Your home data is private by design.
This policy explains what Tidy 20 collects, why it is needed, which service providers process it, and how to export or delete it.
Updated November 8, 2026 · Version 2026-11-08
1. Who controls the data
Krausenhouse LLC operates Tidy 20 and is responsible for the personal information covered by this policy. Questions and privacy requests can be sent to friends@tidy20.com.
Emailing Support
Support-mail processing clarified November 13, 2026: messages you send to friends@tidy20.com are received through Resend and forwarded to the operator’s support inbox hosted by Google Gmail. This includes the message and attachments you choose to email us. This service does not query your private app photos, rooms or coaching history, and sending a support message does not subscribe you to marketing.
The application keeps limited forwarding-state records for up to 30 days to prevent duplicate sends and identify failures; scheduled cleanup can be delayed by an outage. It does not copy email bodies, subjects, attachment content or download links into its database. Account deletion removes associated local forwarding records and retains a minimal sender hash and erasure time so an old webhook cannot recreate them. New support messages after deletion are still allowed. A signed-in account can export its associated forwarding-state records through the early-access export controls even when marketing is paused.
Copies in the email provider and support mailbox follow their retention controls and any support, security or legal obligations. Deleting an app account does not recall an already forwarded email or rewrite those providers’ records. Contact Support for a correspondence-removal request. Oversized or unusually structured messages may require manual review in Resend rather than automatic forwarding.
2. Information you provide
- Account information: email address, display name, household name, a securely derived password hash, household membership, and legal acceptance records.
- Home content: room names, reset tasks, timing, completion history, friction notes, calibration findings, and preferences.
- Optional photos and AI content: room images, prompts, generated goal images, and friction-coach conversation content when you actively use those features.
- Billing information: subscription status, price or product identifier, customer, transaction, and subscription identifiers, store platform, expiration, and a one-way hash of the Google purchase token where applicable. Native purchases use a random Tidy 20 account identifier—not your email—to bind the store transaction to your account. Payment-card details are handled by Stripe, Apple, or Google and are not stored by Tidy 20.
- Beta and support information: invitation status, feedback, rating, product context, platform, and messages you send us.
3. Information collected automatically
We collect limited operational information needed to authenticate sessions, prevent abuse, diagnose failures, meter feature allowances, and secure the service. This can include session identifiers, request time, IP-derived security signals, browser or app platform, model and token usage, and provider logs. Tidy 20 does not use third-party advertising trackers and does not sell personal information.
4. How information is used
We use information to provide and synchronize household features, authenticate accounts, process subscriptions, deliver password and invitation emails, analyze optional photos, generate requested images, provide friction coaching, enforce allowances, respond to feedback, prevent fraud, improve reliability, comply with law, and protect users and the service.
5. Room photos and AI processing
Original and generated room images are stored in private object storage and are not public. When you choose an AI feature, the necessary image and text are sent to OpenAI’s API for that request. OpenAI states that API inputs and outputs are not used to train its models by default unless the API customer opts in. OpenAI may retain API abuse-monitoring data for up to 30 days under its standard controls, subject to its policies and legal obligations.
Do not photograph people, sensitive documents, medications, financial information, access codes, or anything you do not want processed. You can use the Free plan without photos or AI.
Coaching voice and optional online room announcements
Pre-recorded generic encouragement can play without sending your room details. Standard device speech also works without voice-provider permission. If matching online room announcements are available and you separately enable them, Tidy 20 sends the necessary room and task wording to ElevenLabs to generate speech. This does not send your room photos, coaching conversations, or observation history to ElevenLabs. We keep online room announcements disabled until our provider account’s model-improvement sharing is turned off.
Named recordings are private to your account and household. You can remove online voice permission in timer companion settings; revocation removes the active server audio cache and leaves the pre-recorded voice available. Recordings become unavailable after seven days and their stored audio is removed at the next scheduled or request-time cleanup. Limited generation-job records are scheduled for deletion after 35 days and generation-budget records after 65 days to prevent duplicate charges and enforce limits. An outage can delay cleanup. Permission records remain while needed to remember your choice. You can export available voice records and recordings through the voice controls. Account and household deletion remove their active voice records.
Protected database backups may contain earlier recordings or permission records. Before a restored backup can serve voice requests, restored recordings and voice permissions are cleared; online voice requires fresh permission. ElevenLabs may retain request and response data under its own policies; zero-retention processing is not promised. Removing Tidy 20’s cache does not itself erase provider records or rewrite earlier backups.
6. Service providers and disclosures
We disclose only what is necessary to service providers acting for product operations: Railway for application hosting, database, and private object storage; OpenAI for requested AI analysis and image generation; ElevenLabs for separately enabled enhanced spoken timer cues; Stripe for web billing; Resend for transactional account email; and Apple or Google for native distribution and in-app billing when those versions are offered. We may also disclose information when required by law, to protect rights and safety, during a business transaction with appropriate safeguards, or with your direction.
Group sprint participation
When you host or join a group sprint, we store the display name you enter, the sprint’s room labels, room selections, progress, timer state, and an access-token hash so participants can reconnect. The host’s account is linked to the sprint. Guests do not need an account or subscription. Anyone with the invitation code can join and see the sprint’s names, room labels, and progress. Sprint participation does not share private household photos, saved tasks, AI content, or subscription access.
Sprint access expires 24 hours after creation. Expired sprint records are removed when accessed or during cleanup when a new sprint is created; deletion may therefore occur after the access window. Leaving removes a guest from the active participant list. Deleting a host’s account removes the sprints they hosted. Database backups and operational records follow the retention controls described below.
Optional Observe & learn features
Additional disclosures for optional observations, contextual AI, and study check-ins are in the Observe & learn privacy supplement, version 2026-09-28. These features require separate opt-in and do not change the version of this core policy or the Terms.
Early access and optional Tidy 20 updates
If you request early access, we store your email, request and confirmation times, invitation/reservation status, and a limited campaign source such as the social channel or campaign name. We use these records to verify your request, manage the small tester cohort, deliver requested access messages, and prevent duplicate or abusive requests. Verification links expire; opening a link alone does not confirm your request. Private beta codes are restricted to the invited account and do not create a paid subscription.
You can save a timezone and delivery window for optional email updates. We use the timezone you choose, not an inferred location from your email or IP address. Optional updates wait if no valid timezone/window is saved. You can change or clear this timing on the email preference page or signed-in tester check-in; saving timing does not turn marketing consent on. Retained timing preferences are included in your early-access export and removed with contact/account erasure. Verification and access messages are separate.
Optional tips and product announcements require a separate choice. This permission is for Tidy 20 only and does not subscribe you to another Krausenhouse LLC product. You can unsubscribe from optional updates without changing account/security messages or canceling your pending access request. The same preference page separately lets you withdraw an unfulfilled early-access request. Withdrawing does not delete an existing Tidy 20 account or cancel a store subscription.
Requested access messages and separately opted-in Tidy 20 updates use Resend. Queued message bodies are encrypted and cleared after provider acceptance, cancellation or the applicable expiry/retry window; provider acceptance does not prove recipient delivery or reading. Unconfirmed requests are removed by maintenance after seven days. Confirmed requests and invitation records remain while needed for the beta or your chosen updates; you can request removal through Support. Account deletion also removes associated early-access contact and queued-message records. A minimal email hash may remain to honor suppression and prevent messages from being recreated accidentally. A signed-in account can export its own early-access records from the early-access controls. We do not send room photos, household content, or coaching conversations to marketing tools.
Early-access mail and tester-report details clarified November 13, 2026: signed email-provider events record delivery, bounce, complaint or suppression status so we can stop inappropriate retries and messages. We do not use email-open or click events to decide these follow-up messages. Minimal message-state and event records support deduplication and troubleshooting; active records associated with your contact are removed with account/contact erasure. An erased contact is not recreated from a later delivery event.
You can optionally tell us that you tried a first reset or returned for another visit. These records show when you reported progress, not when a room was tidied, how tidy it was, or whether an iPhone app was installed. They include no room names, photos or task details. You can clear these reports in the tester check-in and include retained reports and mail-state records in your early-access export. Clearing a report does not restart previously sent messages or erase a separate feedback note you submitted. Existing backup and deletion-replay controls also apply to these records.
First-party marketing measurement
Payment measurement clarified November 14, 2026: when enabled, a private read-only process checks existing billing-provider records for verified early-access claimants and homes they own. It records minimal dated evidence of a production purchase begun after the access claim, its source category, a hashed source reference and any known reversal. Trials, Sandbox purchases and missing evidence do not establish a paid conversion. These reporting records contain no card details, amounts, raw transaction responses, room content or conversation data and do not change purchases or access. Retained records are included in your signed-in early-access export; withdrawing the request or deleting the associated account or home removes the applicable payment evidence and clears derived weekly snapshots. Provider billing records remain subject to their separate retention controls.
Anonymous marketing page counts use no advertising identifier or account cookie. Only a public page path and allowlisted campaign words are counted after an interaction. They do not record what you type, private app pages or room content. Browser Do Not Track and Global Privacy Control are respected.
When collection is enabled, a short-lived random page nonce is sent without account cookies to prevent duplicate counts. Only its day-specific hash and a temporary claim marker are retained for up to48hours; no IP address, email or persistent visitor identifier is copied into these records. Aggregate counts for allowlisted public paths and campaign words are kept for up to56days. Counts describe browser-reported engaged pageviews, not unique people or proof that a person installed or used the app.
Allowlisted campaign words can be remembered in this tab’s session storage for up to30minutes to preserve the source when you follow a guide or request access. A browser opt-out clears that memory. No private invitation query or room content is retained. Anonymous aggregate counts cannot be linked back to your account.
Private operational reports can show explicitly reported tester progress, delivery state, synthetic-test exclusions and shared provider quotas. Weekly snapshots expire after56days. Relevant contact/account erasure, cleared progress and changed test exclusions clear stored snapshots; a later run can create a fresh current-period report from remaining records. Heartbeat records retain only operational status for14days. Scheduled maintenance enforces these retention windows; an outage can delay cleanup. These controls do not initiate optional email or change your subscription.
7. Retention
Account and home content are kept while the account is active. Optional photos and generated images remain until you replace/remove them or delete the owning account or household. Confirmed removals are hidden from the app immediately. Private backup copies are removed on the next successful hourly deletion-sync run; a storage or service outage can delay that cleanup. Minimal opaque deletion records are retained to prevent removed content from being restored. Beta feedback remains while needed to evaluate and document the beta unless you delete your account or request earlier deletion. Subscription, security, and operational records may be retained as needed for fraud prevention, dispute resolution, accounting, or legal obligations. Service-provider logs follow the provider’s retention controls.
8. Your choices and rights
You can use manual Free features without submitting photos, export household data from account settings, correct profile information, revoke household members, cancel renewal, and delete your account. Depending on your location, you may also request access, correction, deletion, restriction, portability, or appeal a privacy decision. We do not discriminate for exercising privacy rights.
Use the in-product deletion control or follow the external instructions at tidy20.com/support#delete-account. We may verify that a request comes from the account owner.
9. Security
We use authenticated household separation, hashed passwords, revocable sessions, restricted private storage, signed billing webhooks, and server-side API credentials. No system is perfectly secure, so please use a unique password and report suspected access promptly.
10. Children and international processing
Tidy 20 is for adults and is not directed to children under 13. We do not knowingly create accounts for children. Information is primarily processed in the United States and may be processed where our providers operate, subject to applicable safeguards.
11. Changes
We will update the effective date and notify account holders when a material privacy change requires notice or consent. Contact friends@tidy20.com with a privacy question or request.