Legal
License, privacy and refunds
Beta builds show the short agreement below before use. Product licenses and third-party notices are available inside each app.
The beta terms below apply to approved beta builds. The license terms apply to paid releases; a 30-day demo needs no purchase.
Beta access
Niche-Knack reviews beta requests for the apps in beta, currently Choirboy, and sends invitations as places become available. A request is not an approval or a guarantee that a particular platform is ready.
An approved tester receives a private download invitation by email. Keep the link and activation code private. If beta access ends, you can request more access or get the full version when it is available. Reinstallation and additional devices do not extend access. Access may be revoked to address a security or testing problem. Expiry or withdrawal of diagnostic consent pauses beta access without deleting your saved work.
Beta software can contain bugs. Keep separate copies of important work. There is no charge for the beta and no automatic conversion to a purchase or subscription.
The first-open beta agreement
This is beta software. Some features may be rough or may not work as expected. While you use it, the app sends diagnostic reports to help fix problems. Reports use a random ID instead of your name or email and exclude personal content, file names, and media titles.
The app asks you to choose: “I accept the beta agreement and diagnostic sharing.” Acceptance is never preselected.
License
- Pocket Nerd, LedgerKeep, Rabbit Trail, Clip Dr., Euphonics and RiffWright are licensed to you, not sold. A purchase is a license to use that major version for as long as you like, on up to 5 of your own devices. Desktop and Android are separate purchases.
- Point releases within a major version are included. A new major version is a separate purchase.
- The 30-day demo is the full app. After it ends the app is read-only until you buy. Saved work stays yours either way.
- The license shipped with your build states its permitted use and restrictions. Third-party components have their own notices.
- Your data is yours. Nothing in the license gives me any right to your entries or your books. They are files you control and can move or delete whenever you like.
Privacy
App privacy notices: Pocket Nerd · LedgerKeep · Clip Dr. · Rabbit Trail · Euphonics.
- Your financial records stay on your devices unless you set up sync. Pocket Nerd can sync over Wi-Fi, Bluetooth, or an encrypted Dropbox folder. LedgerKeep can sync over Wi-Fi or a Git remote you choose. These financial records are not sent to me by normal app use. If you send a support request or diagnostic report, that material is received for support.
- This site uses self-hosted analytics (Umami) to count visits and interest in each app, including beta form starts, successful requests, demo downloads and helpful votes on guides. A thumbs-up records the guide and whether you rated the page or video. It honors Do Not Track and uses no tracking cookies or account identifiers. Query strings, invitation codes, support details and form contents are excluded. Private download and account pages are not tracked. Product screenshots and fonts are served from this site.
- Purchases go through Lemon Squeezy (direct) or Google Play. I receive the contact and order details provided by the store and use them to honor your license and any refund.
- Support requests are handled through the support system and email. An account is optional. Requests are saved with your name, reply address, message, order reference and diagnostic information you choose to send. Questions and suggestions from help pages also include a link to the guide. These messages are not sent to analytics. A confirmation lets you continue by email. If you create an account, verify your email before viewing matching requests online. Do not include passwords or private files that are unnecessary for the request.
Beta requests and automatic reports
Sending the beta form saves your name, reply address, platform and note in Niche-Knack’s support system. It sends a confirmation to your email and a notification to support@nk.tools. I use these details to respond and arrange beta access. An account is optional: if you choose to create one, the account service stores a protected password hash and sends an email verification link. Your password is never included in a ticket or notification. After verification and sign-in, requests made with the same email address appear in your support dashboard. A request does not subscribe you to marketing mail or start a purchase. You can ask me to delete your request or account through support.
Beta builds require your explicit agreement before collecting or sending diagnostic reports. The first-open screen explains this. Reports help diagnose bugs, slow operations and memory problems. While the app is active, it normally sends a small batch about once an hour and retries after a connection is restored. Reports are kept in a bounded local queue while offline. An app that is closed or killed by the operating system cannot promise to send a report at that moment; it can report an incomplete previous session on its next opening.
Reports contain the app and build version, operating system version, broad device class, processor architecture and core count, approximate memory capacity and use, graphics backend, operation timings, fixed error codes and fixed code locations. They do not contain raw log text, document contents, financial entries, media or media titles, transcripts, research sources, filenames, source addresses, names, email addresses, device serial numbers, passwords or access tokens.
A random installation identifier links reports from one installation to an approved beta enrollment. These reports are deidentified, not completely anonymous: the service can associate the installation with your approved request. Only authorized support staff can view them. They appear separately from messages you send to support, and may be reviewed with support tools, including an optional configured assistant. Raw diagnostic batches are retained for up to 30 days and then removed; aggregate testing counts and your enrollment, consent history, support correspondence and reward eligibility have separate purposes.
You can withdraw diagnostic agreement in the app. Collection and sending stop immediately, unsent reports are cleared and beta access pauses. Reinstating agreement does not extend your access period. To ask for deletion of received reports or enrollment details, contact support. Routine server access logs may include connection metadata such as IP addresses for security and traffic control; invitation codes are carried in a private exchange, not public download addresses.
Rabbit Trail stores research in a local archive and Clip Dr. processes audio locally. Chosen web sources, model downloads and device sync may use a network connection. Choirboy’s optional online services and connected media libraries have their own data flows; its product terms are at choirboy.app.
RiffWright privacy
RiffWright and RiffWright Beta are provided by Niche-Knack Apps LLC. Songs, recordings, Quick riff takes and your own sounds stay on your device, and Quick riff listens on your device. Beta access and reports follow the agreement and privacy terms above. The full RiffWright privacy notice covers microphone use, the 30-day demo, license keys, store purchases and updates.
Euphonics privacy
Euphonics and Euphonics Beta are provided by Niche-Knack Apps LLC. Writing, dictionary tools, scansion, saved poems and recordings work on your device. Your writing and recordings are not included in automatic diagnostic reports. Beta access and reports follow the agreement and privacy terms above.
The optional writing assistant has separate settings. Local assistance processes writing on your device. If you choose a connected server or Niche-Knack hosted suggestions, the app asks permission before sending selected writing context when you request a suggestion. This can include poem text, a selected line, writing directions and rhyme or meter constraints. Choosing a server or saving a poem does not send writing by itself.
Connected requests go to the server you choose, using the API credential you supply. That provider's privacy and retention terms apply. Hosted requests go to Niche-Knack's service and its processing providers to produce the requested suggestions. Access credentials accompany requests to verify service access; they are not diagnostic data. Network requests to remote services use encrypted connections. You can turn off the assistant or withdraw its permission in Settings without losing your saved writing.
Exporting or sharing a poem or recording sends the content you select to the destination you choose. Local recordings, imported files and dictionary searches are not otherwise uploaded. Beta diagnostic reports contain the limited operational information described above, even when the writing assistant is off. Support messages contain only the information and attachments you choose to send.
Lamplighter privacy
Lamplighter is free and does not use the beta invitation or automatic-reporting program above. Its privacy policy covers local reading, optional online sources, shared studies and listening connections.
Breach privacy and connections
Breach is not an anonymity tool. Shared prayers travel over the internet and independent relays. If using Breach could put you at risk, do not assume your activity is unmonitored. Networks, relay operators, or people with access to your device may observe app use or connection information, such as network addresses and connection times. Protecting prayer content does not guarantee anonymity or protection from state monitoring.
Public posts are public. Words shared with selected friends or private groups are encrypted, but recipients can keep or copy them. A prayer’s selected Visibility includes its saved journal and edited speech transcript. Choose On phone only to keep those words on this device. Keeping words or prayer activity on your phone does not itself turn off the app’s other network traffic. A fresh or unnamed identity does not hide network connections. See the current Android privacy guide before sharing.
Public news and source websites
After you allow network access, Breach can download a public news snapshot from Niche-Knack at nk.tools. That download does not attach your prayer words, journals, contacts, or Breach identity. Niche-Knack and its infrastructure providers can still receive ordinary connection information, including your network address, request time, and the app identification sent with the request. This news service is separate from the Nostr connections used for shared prayer activity.
With network access allowed, Breach can also contact source websites to read missing headline titles. Adding or refreshing a feed contacts its provider; choosing Read source opens the publisher’s website. Those providers receive the request and ordinary connection information, and their privacy terms apply. Saved news reports and headline titles can be cached on your phone. Keeping a prayer On phone only does not turn off these separate news connections. Read the refresh and report-date guidance.
Prayer audiences
These controls are available in the Android app. iPhone is coming soon. The prayer Visibility choices are Public, Groups only, Friends only, Groups and friends only, Specific contacts only, and On phone only. A saved audience for an individual prayer takes precedence over the general default. Review the selected audience before finishing or saving a prayer. Each prayer in a list retains its own audience and recipients, including for its saved journal words.
Public prayers and their saved journal words can be read by anyone. Restricted activity and words are encrypted for the selected saved Breach contacts or current members of selected private groups. Explicitly selected invited contacts can have authorized prayers held for delivery after acceptance and verification. Public groups are not private recipient lists. Group and friend audiences combine those recipients; specific contacts means the people you select. Separately enabled anonymous live dots carry no prayer title or journal words.
Saving a prayer with a shared audience makes its journal words eligible for delivery to that audience; there is no separate Share words step. On phone only keeps the prayer’s words on this device. Updating Breach does not publish older unshared journals in bulk: their author must edit the saved prayer, review its words and intended audience, and save it. Changing visibility withdraws pending activity and words for that prayer, but cannot recall copies already received or a send already handed to the network.
Editing an existing shared prayer or request lets its author change the words and audience. With the same audience, the edit keeps the post's original identity and date. An audience change creates the new permitted copy before requesting removal of the old one. Making words phone-only preserves a local journal copy before recall; if that copy cannot be saved, the change can fail. Existing journals are not discarded to make space. Read the result before assuming a change completed. Earlier recipients may retain copies, and editing words does not erase separate prayer-activity signals.
New friends can receive retained history explicitly shared with friends. Members of selected private groups can receive retained history shared with that group. This ordinary feed history is bounded by the original 30-day signed-post lifetime, withdrawals, blocks, and delivery limits. Specific contacts never expands to all friends, and an empty group selection does not automatically include future groups. Phone-only and older unshared journals are not automatically included in this history sharing.
A live audio room is a separate choice: participants can see that you joined and hear an explicitly enabled microphone, regardless of your prayer audience. Listeners may record audio. Neither an audience choice nor encryption makes participation unobservable.
Invited recipients and retained prayers
You may explicitly select an invited person as a future recipient. Authorized prayer activity and shared words remain on the sending phone until the intended person accepts and completes verification, after which eligible items can be delivered encrypted. Naming or tagging someone does not override Visibility. The selected audience includes the prayer’s saved journal. Older unshared journals require their author to edit and save with the intended audience before becoming eligible for delivery. Pending authorized items are distinct from the relay cache and ordinary feed history; edits, audience changes, blocks, withdrawal, and deletion limit later delivery. Verification does not guarantee delivery or erase copies already received. A receiving-app acknowledgment does not mean the person read the prayer.
Your own Activity entries can display titles matched from saved prayer history on this phone. Displaying that local label does not add a title to the transmitted prayer-activity message. A saved shared prayer’s title and journal follow its selected audience. Optional anonymous live dots contain neither.
Prayer lists, appearance, and playback on your phone
Prayer lists, their reminders, appearance preferences, and imported font files are saved on this phone. Adding a prayer to a list does not combine its audience with the other prayers. Deleting a list removes its list reminder but keeps the individual prayers and earlier history.
Past 24 hours builds a bounded local cache of derived playback frames from available dated news, requests, victories, and prayer observations. Reconnecting can retrieve available shared history through the existing news and Nostr connections. This is not a complete worldwide record; gaps remain unknown. Current deletion, hiding, blocking, and audience rules still limit what is shown. Clear playback cache removes the derived frames, not original prayers, private journals, identity keys, or settings.
Encrypted identity backup
An identity backup is a password-encrypted file saved to the destination you choose. It includes the identity and supported native social records, including contacts, email associations, pending contacts, and authorized shared prayers. Private journals, prayer lists, appearance choices, imported fonts, and other phone settings are not included. Older files may contain only the identity key. Saving to a cloud-backed folder or sharing the file also puts that encrypted copy with the service or recipient you choose. Keep the password separately; restoring a file does not change the selected verification service or phone, or recover information absent from the file.
Optional profile photos
In the Android app, You → Profile lets you add, change, or remove a photo. Saving keeps your name, About text, and photo on the phone unless you explicitly select Share profile publicly. Choosing a photo alone does not publish it. Guided setup also offers an optional name, email verification, usual prayer region, and identity backup. Share my name publicly starts unchecked. A name can label earlier prayers locally without republishing them or changing their audience; email verification and public profile sharing remain separate actions. The phone crops and re-encodes the image as a small PNG thumbnail without the original photo metadata. A shared profile carries the image directly; viewers do not fetch a remote avatar URL. Without a readable photo, the app uses initials or a neutral symbol. Separate anonymous identities do not inherit the phone owner's profile.
A public profile and its photo can be read and copied by others. Removing a photo locally does not retrieve previously shared copies. Publishing an updated profile asks other clients to use that version; it does not guarantee erasure from recipients, relays, or backups.
Optional nk.tools relay
The optional relay at nk.tools/relay is a temporary, best-effort cache. Each admitted event is kept in memory for at most 24 hours from its first server receipt, or until an earlier signed expiration. Duplicates still cached keep their original deadline; a purged event can be newly received later. Restarts and capacity limits may remove events sooner. The cache has no payload disk storage, swap, core dumps, payload logs, or payload backups. This retention does not erase prayers or journals saved on phones, or copies held by recipients or other independent relays. The relay does not federate with other relays and does not guarantee delivery.
Nearby forwarding
Nearby discovery and relay hosting are separate settings. Opted-in phones can forward signed public posts and encrypted deliveries within Bluetooth range and available connections. Forwarding does not authorize reading private words or verifying another person’s email identity. Phone permissions and background limits still apply. Shared copies may remain after an edit or deletion, and encrypted content does not make network activity anonymous. See nearby and backup settings.
Optional email invitations
Breach does not upload your address book. In versions that offer Email under Together → Invite, choosing Send invitation sends the one recipient address you entered or selected, your chosen display name, your optional message, and a signed partner invitation to Niche-Knack’s service at nk.tools. Niche-Knack and its mail provider, MXroute, use this information to deliver that email. No email-account sign-in or SMTP setup is required. The sender is shown as your name via Breach, using support@nk.tools or no-reply@inthebreach.app as shown in the message; this does not verify your personal identity or send from your own email address.
The active delivery queue keeps the address, name, message, and invitation until the mail server accepts the email, delivery fails or becomes uncertain, or 24 hours pass, whichever comes first. A delivery receipt and hashed address/network values are kept for up to 31 days to handle retries and limit abuse. These records are pseudonymous, not anonymous. Company backups and mail-provider records have separate retention; the recipient’s email provider and device can also keep the delivered message. To stop further Breach invitation emails to an address, reply with “Stop invitations” or contact support@nk.tools. A hashed address remains on the suppression list to honor that request.
The Android app keeps invitation status and link controls under Together → Partners → Invitations. A signed request can refresh the sender's own delivery receipts or cancel a pending email before it is handed off for delivery. Refreshing status does not send mail. An email accepted by the provider cannot be edited or recalled; acceptance does not prove inbox placement or reading. Recall link can separately stop a new partnership from that link, without erasing delivered email or removing existing partners. Editing prepares a draft and never sends a replacement automatically.
Invitations and automatic verification-code requests use this email service. The independent two-phone verification method instead sends its code through the verifying phone’s configured email app. Prayer posts, private groups, local journals, and the sharing choices described in Breach keep their existing paths. Invitation pages exclude analytics. Older links keep the complete invitation in the link fragment and can still be opened manually. New short inthebreach.app links keep a random token in the fragment; the page sends that token privately to the invitation service to retrieve the original signed invitation. Opening the page does not accept it. Email providers and anyone you forward the message to can still read the invitation. See partner invitation help for delivery states and confirmation steps.
Short invitations use a separate service record containing the original signed invitation, sender public identity, request and invitation identifiers, hashed link token, hashed recipient address, and expiration. The link expires after at most 30 days or the invitation’s earlier signed expiration. Expired links stop resolving immediately; the existing scheduled worker removes expired active records while the service is running. This separate record can remain after the delivery queue erases its message. A confirmed link recall or address suppression removes it sooner. Explicit service recovery from a company backup clears these short-link records so a revoked link is not restored; retained backups and recipients may still hold earlier copies.
Supported Breach versions can request incoming invitations using the current identity’s signed authorization. The service matches only that identity’s current, service-verified email associations and returns matching invitations privately; it offers no public email lookup. Finding a match does not accept a partnership, upgrade an older invitation’s verification rules, or share prayer history. Breach still requires the invitation’s validation and confirmation steps. Removing a verified email association stops incoming matching for that association; it does not erase the email already delivered or independently recall its invitation.
Optional email verification
Email is optional. The Android app offers Email me a code, sent by nk.tools, as the default optional method, and Another Breach phone as an independent choice. You request and enter the code inside Breach; no inbox password is requested there. Verification does not establish legal identity, add a friend, or make a reassigned address the owner of someone else’s saved prayers. Accepting the exact signed invitation and matching verification evidence is required to bind the intended contact and make previously authorized history eligible for delivery.
Automatic verification sends the selected email address, Breach public identity key, and code to Niche-Knack at nk.tools. The service checks the code and retains private signed association evidence containing the email address itself, not just a hash. It also handles verification requests, challenges, results, and operational records for delivery and abuse controls. It receives no prayer words, journals, or address book, and provides no public email directory.
Niche-Knack and MXroute handle automatic verification email. The active mail queue keeps message content until provider acceptance, terminal failure or uncertainty, or at most 24 hours. Delivery receipts and hashed address/network values remain for up to 31 days for retries and abuse controls. Those mail limits do not apply to the separate signed evidence retained for associations that do not automatically expire. These are private service records, not anonymous data. Company backups, mail providers, and recipients can retain separate copies. A mail-delivery receipt is not proof of verification.
With Another Breach phone, both phones need a version supporting the method and the verifying phone needs a configured email app. That phone creates, checks, and signs the verification inside Breach; its email app and provider deliver the code. This method uses neither the nk.tools verifier nor its mail courier. The participating phones exchange private verification messages and evidence, and they and their email providers can retain copies. Opening or sending from an email app does not prove inbox delivery. Other app connections and network metadata remain subject to Breach’s existing privacy and connection limits.
Codes expire after three calendar months. A replacement invalidates the old code when the selected verifier processes it; an offline request cannot change the verifier immediately. Accepted associations have no automatic expiration. Existing invitations and accepted proofs keep their original verifier. New invitations can offer both methods; the first accepted method stays selected. Canceling an unused method does not silently replace an accepted proof. An inviter’s recall cancels the invitation as a whole.
When nk.tools processes a valid removal, it clears the active challenge, verification assertion, and code hash. It retains signed removal, public identity, mailbox-hash, and operation metadata. Backups and other phones may retain earlier evidence. Removal does not erase existing partners, received prayers, or journals, or recall copies already delivered. Other devices need synchronization or Check status to learn about removal; this action is also available for verified automatic associations.
To stop invitation or verification emails sent through Niche-Knack’s service, contact support@nk.tools. A hashed address remains to honor that request. This suppression does not control mail sent through another person’s independent email app. Existing invitees need an explicit verification invitation; an app update does not send one for you. Read the verification questions and steps.
Optional closed-app alerts
The Android app offers optional closed-app alerts. Both sender and recipient must opt in. Generic alerts travel through nk.tools and Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). Local prayer reminders are separate. The app remains usable without this optional service, and notification permission, connection, or phone settings can delay or prevent delivery.
The service uses the enrolled public identity, phone delivery address or token, random registration identifier, allowed sender public keys, and category choices. Sending a hint supplies sender and recipient public keys, an event identifier, creation time, and a generic category: prayer, room, or thanks. Apple or Google receives the delivery identifier and a generic alert or enrollment challenge. Prayer words, journals, room audio, private keys, and identity backups do not enter this service. These identity and delivery records are private service data, not anonymous data. Opening an alert makes the app check the actual Nostr activity; a hint alone is not proof that an event exists.
Active registrations have a 30-day lease unless renewed. A pending enrollment challenge and a queued delivery hint each expire after 10 minutes; duplicate-suppression records last up to 24 hours. Revoked registration identifiers are retained for up to 30 days to reject delayed re-enrollment requests. These limits concern the service’s active records, not prayers saved on a phone or Apple’s and Google’s own records. Operational backup copies may remain for up to 28 days after removal from the active service. Recovery from a backup requires fresh enrollment; historical push registrations are not reactivated. This does not delete prayers or other data saved on your phone.
Turning alerts off requests removal of the registration and pending jobs; an offline request must wait for a connection. After the service confirms removal, no older queued send can begin. An alert already accepted by Apple or Google may still arrive. Allowed senders and categories are checked again before each send. No email-account sign-in or personal SMTP setup is part of push enrollment.
Breach community and child-safety rules
Version 2026-10-31 · Adults 18 and older. These rules apply to profiles, prayer requests, victories, shared words, groups, and live rooms. Use Breach respectfully. Do not threaten, harass, promote hatred, impersonate others, run scams, or send spam. Do not publish another person’s private information without permission.
Sexual or exploitative content is prohibited. Child sexual abuse or exploitation, grooming, sexualization of minors, and content that facilitates those harms are strictly prohibited. Do not use Breach to solicit or arrange abusive or illegal activity.
Report a safety concern privately to Breach, or contact support@nk.tools. Niche-Knack support is the responsible safety contact and reviews these reports through the private support queue. Share only the details you choose; no prayer words are attached automatically. For suspected child exploitation, provide a description and event or identity ID when available, not illegal media. For immediate danger, contact local emergency services.
Niche-Knack support reviews reports, prioritizes threats and child-safety concerns, and can request necessary clarification, use available controls on services Niche-Knack operates, and report apparent child sexual exploitation to the appropriate authorities as required by law. Company-relay responses currently include clearing its temporary cache or suspending its route; these actions do not prevent every later resubmission. A receipt confirms the report was saved; it does not mean a review or removal is complete. This is not a continuously monitored emergency service.
In the Android app, More → Remove from this phone hides another person’s request or shared post on this phone and keeps it hidden after syncing. Other people can still see it. Delete request or Delete post on your own content asks relays or recipients to remove their copies; copies elsewhere may remain. These actions keep your private prayer history, journal, and reminders.
Use Block in Breach to hide a person’s activity on your device. Private-group owners can also manage their groups. A public Nostr report is a separate public action and does not by itself notify Niche-Knack staff. Niche-Knack cannot erase copies from independent relays or recipients’ phones, guarantee removal everywhere, or make shared activity anonymous. Reports and any evidence you choose to send are handled under the support privacy policy.
Request account or data deletion
To delete your optional Niche-Knack support account, use the dedicated account deletion form. Sign in with that account and confirm; no explanation or support conversation is required. Niche-Knack support completes verified requests within 7 days and confirms by email, or explains a specific legal or transaction-related retention requirement. The account is shared with other Niche-Knack and Choirboy services.
For particular beta requests, received diagnostic reports, or support information, contact support or email support@nk.tools. Name the app and the data you want removed. You do not need to create another account for these requests; we verify ownership before acting.
Raw beta diagnostic batches are removed within 30 days. Account and enrollment records, consent history and support correspondence are kept to provide access and support until no longer needed or deletion is requested. Records needed to meet legal obligations, prevent abuse or resolve a dispute may be retained for those purposes. Deleting cloud records does not erase files saved on your devices or copies you sent to another service; you control those separately.
Refunds
- Bought here: 30 days, money back, no reason needed. Request a refund through support with your order number. An account is optional. You can also email support@nk.tools.
- Bought on Google Play: Google handles the refund under its policy.
Who
Niche-Knack Apps LLC, Ohio, United States. Questions: Contact support.