Privacy Notice

1. Information we handle

• Account information: Your email address, account identifier, sign-in and verification records, and the account-to-household connection. We also keep access status, including complimentary access when granted.
• Planning information: Household members’ names or labels, ages or birth dates, retirement choices, income, spending, account balances, savings, assumptions, scenario names, and other entries you choose to provide. Basic unsaved projections are calculated on your device. When you save, reopen, update, or request a report, the necessary planning records are processed by the server; saved records include inputs, results, and previous versions. The Plus insurance worksheets send their entered values to the server for calculation.
• Payment information: When you use checkout, the payment providers collect the checkout details, including your email and payment method information. Money Rehearsal uses your account identifier, product, subscription status, and purchase, renewal, expiration, or refund information to determine access. The app does not store full card numbers or card security codes in its account database.
• Service requests: Your contact email, selected issue, optional purchase date, message, submission time, reference number, app version, any error reference you supply, and delivery status. The form also keeps hashed email and connection-address identifiers for abuse controls. Please do not submit financial plans or sensitive documents in the issue form.
• Technical information: The app keeps daily totals of account operations and server failures for 30 days, plus operational check and backup status. These counters do not contain financial entries, email addresses, or sign-in tokens. Our hosting, sign-in, email, and payment providers may process connection and usage information such as IP address, browser information, timestamps, delivery events, and errors to operate and protect their services.

2. How information is used and shared

Information is used to provide calculations and saved reviews, authenticate access, deliver sign-in emails, administer subscriptions and refunds, handle service requests, prevent misuse, and meet applicable obligations. We do not sell personal information, share email addresses for other companies’ marketing, or use the app to serve targeted advertising. RevenueCat uses purchase history and account identifiers for subscription functionality and subscription analytics, including customer history and subscription reporting.

Authorized personnel of Cornerstone Keep, LLC may access records for operation and support. Information is shared with service providers as needed for their functions:

• Render: website and server hosting, including the database containing saved household records and service requests.
• Supabase or Clerk: email-based account authentication and associated account and security records. The Clerk test app service uses Clerk; the earlier Supabase-backed app service continues to use Supabase until a migration is completed. Clerk processes technical information for authentication and abuse prevention. Development SDK telemetry may apply on the website; it is disabled in our native Clerk integration.
• Resend: delivery of sign-in emails, service-request notifications, and account-deletion completion emails.
• Google Gmail: receipt and handling of service-request notifications in the operator’s private support inbox.
• Apple App Store and Google Play: native store purchase, subscription, receipt, and refund processing when store purchases become available. RevenueCat verifies store entitlements using the app account identifier; household projection amounts are not sent for that verification.
• RevenueCat and Stripe: hosted web checkout, payment processing, subscription management, receipts, and subscription access verification when those features are used. Sandbox checkout also creates test customer and transaction records; use test payment details only.

Saved household projections are not sent to payment providers as part of the subscription-access check. Providers may process information in the United States and other countries in which they operate. Their own notices describe their independent processing. We may also disclose information when required by law or reasonably necessary to address fraud, security threats, or protect legal rights.

3. Browser storage, security, and retention

The Supabase version keeps its sign-in session in browser memory rather than persistently saving it in local storage. The Clerk test version uses Clerk session cookies and related browser storage so a sign-in can continue after a reload. Sign out when using a shared device. If you choose “Keep my household entries in this browser tab,” household setup inputs are kept in session storage on that device for restoration after a reload. You can clear the tab draft at any time; sign-out also clears it. Browser session restoration may retain this storage. This option does not store What-Ifs, results or sign-in credentials. Other unsaved inputs and results can be lost when the page closes or reloads. Your browser may retain form entries, downloaded reports, or cached information according to its settings. External checkout and account-provider pages may use their own cookies or similar technologies for authentication, payments, and fraud prevention.

Mobile apps keep the sign-in credential in iOS Keychain or encrypted Android Keystore-backed storage. The app writes reports to temporary app storage for native opening and sharing, and attempts to clear that report cache at launch and sign-out. Copies you save or send to another app are not removed by signing out or deleting your account.

We use HTTPS and account-access checks, but no system is completely secure. Protect your email account and sign-in codes. Downloaded reports are under your control; use care when saving or sharing them, especially on a shared device.

We make daily database backups. Saved information and backups may become unavailable or be lost; recovery, uninterrupted availability, and permanent retention are not guaranteed. To keep a copy you control, open Saved Scenarios, find your rehearsal, and use Open PDF, Share PDF or the available report download options. The saved input reference can help you manually re-enter information if needed; it is not an automatic restore file. Keep downloaded copies private and update them after changes.

Saved planning records remain associated with your account until removed following a verified request or an operational need to remove them. Canceling a subscription, receiving a refund, or losing paid access does not automatically delete saved information. The current app has no automatic inactivity-deletion schedule.

Account and service-request records are retained to operate the service, resolve issues, prevent abuse, and address legal, accounting, or dispute requirements. Retention depends on the purpose, whether an issue is still open, and applicable obligations. Signed-in account deletion requests include a verified account identifier, household identifier, and submission time. Deletion requests are processed manually within 30 days, with completion confirmation; information no longer needed for these purposes is removed. We retain a minimal deletion record containing the request, account and household identifiers and a timestamp to prevent a deleted account from being recreated by an old session or restored backup. This record does not contain saved financial plans. Other limited records may be retained where required or justified for the purposes above, and backup or provider-held copies may remain until their normal retention cycles end.

4. Your choices and requests

Delete your account: choose Delete my account and saved data in Account settings, or use the dedicated account deletion page. Sign in, review what will be removed, and confirm the request. No paid plan, explanation, or support conversation is required. We process deletion within 30 days and confirm completion by email. Cancel any active subscription separately through the store or web subscription manager.

You can explore basic projections without creating an account. You choose what planning information to enter and whether to save or export it. Enter another household member’s information only with their permission.

To request access to or correction of account or saved information, or report a privacy concern, select Privacy or security concern in the service issue form. These requests do not require a paid plan. Provide your account email and a brief description, not passwords, sign-in codes, card numbers, or financial documents.

We may need to verify that you control the account before disclosing or changing information. Requests concerning a household’s records must account for other people’s rights. We handle requests according to applicable law and explain any reason information cannot be deleted. Depending on where you live, additional rights or complaint options with a privacy regulator may apply.

Deleting an account and canceling a subscription are separate actions. Use the subscription-management link in your purchase email to cancel renewal, or select cancellation difficulty in the issue form. A privacy request will not be treated as permission to make a new purchase.

5. Adults and external links

Money Rehearsal is intended for adults age 18 or older and is not directed to children. If you believe a child has provided personal information, use the privacy issue option so it can be reviewed and removed as appropriate.

Links to other websites, including the Social Security Administration and payment services, lead to services with their own privacy practices. We do not receive your Social Security account credentials or retrieve your official benefit record.

6. Contact and changes

Operator: Cornerstone Keep, LLC. Submit privacy or security questions through the service issue form. This channel is for service issues and privacy requests, not personal financial advice.

We will update the effective date when this notice changes and provide notice of material changes before they take effect, obtaining consent where required.