Understand your choices
Privacy, sharing and data retention
Let's Arrange This helps two adults compare arrangement expectations, intimacy preferences or both. Here you can check what the app stores, what can be shared and when information expires. The app does not promise end-to-end encryption, complete anonymity or a scientific assessment of compatibility.
Local implementation information · 27 October 2026
What Let's Arrange This stores
An alignment stores aliases, age and processing choices with their policy versions, question scope, drafts, submitted answers, a limited report and access records. The person starting an alignment chooses a gender response and can add an optional country or city to their private details. If the alignment includes Intimacy, they also choose a gender response for their partner. These choices determine which gender-specific questions each person can answer. The shared report does not display gender responses. This build does not produce regional statistics. Using these details for that purpose would require a separate choice. The app uses authenticated encryption to store answers, demographic details, reports, aliases, alignment names and private account labels. The server can decrypt records when access is authorized; this is not end-to-end encryption. Optional sign-in uses your email and verified account identity. Application access records hold hashes of random guest, invitation, return and report credentials. The sign-in provider also processes authentication and network information.
What your partner can see
A limited report becomes available after both of you submit. Shared results can still reveal preferences, especially to someone who selects broadly. A shared interest or a Maybe answer never counts as consent. Anyone with a valid report link may see the limited report, so keep that link private too. Never put addresses, contact details or other identifying information in notes.
When answers and reports expire
Your answers, demographic details and drafts expire 30 days after the alignment is created, even if you have an account or save the report. Unfinished alignments and unsaved reports expire on that same original date. Both people must allow longer report retention before submitting. A participant must then choose Save to keep only the limited report for at most 12 months after completion. Permission alone, marking a favourite or creating an account does not extend retention. Check the app for the actual deadlines.
What each removal option does
Removing a history entry removes only your account’s reference to it, its label and its favourite status. Revoking access immediately blocks both people from the alignment. Deleting your participation erases your own answers, identifying participation details and private access, and closes the shared report. The other person keeps their own drafts, submitted answers and private access in the same alignment, subject to the original expiry limits. Deleting an account removes it and the participations it owns, including those hidden from history. Guest participations that were never linked to the account need their own private access. Removal may still be pending after access ends; keep the private receipt to check completion. Screenshots, exports and copies made elsewhere cannot be recalled.
Backups and restoring data
Stopping the app does not erase its database. A completed removal receipt confirms that the affected data has been cleared from current operational storage for the scope of that request. It does not certify removal from historical snapshots or provide an independent backup guarantee. Historical private-data restoration is unsupported for development and initial release. If the database is lost, recovery starts with empty private state rather than importing old accounts, answers or reports. Provider backup retention remains unverified. Expired data stays blocked even if cleanup is delayed.
Optional analytics and limited diagnostics
PostHog receives optional product analytics only when it is configured and you have agreed to analytics. Sentry may receive limited error diagnostics when configured, even if you turn analytics off. These events exclude answers, demographic details, place searches, amounts, intimacy topics, aliases, emails, participant IDs, private codes, credentials, URLs, cookies and arbitrary error text. The app does not enable session replay, page recording or automatic interaction capture. Providers can still see network metadata, including the app server’s address.
Your controls and privacy requests
Export your own retained data and reports you are allowed to access from this page or Privacy options. Exports never include your partner’s raw answers. Alignment controls let you withdraw from intimacy processing, revoke access or delete your participation. Account controls let you remove history entries or delete the account. If you have lost private access, use the privacy request form and keep its private status link. A request alone does not prove ownership, restore access or authorize erasure. Suitable proof is required before removal. The operator’s identity, contact details and process for reviewing requests still need confirmation before public launch.
Privacy requests
Use your existing private access to withdraw processing or request removal. Creating an account is optional. A code or ID locates a record; it does not prove that it belongs to you.
This locates the alignment. Your current participant or private recovery access is still required.
Export your data
Prepare a private copy of your retained information and any report you can currently access. Records are selected when preparation starts; each page checks what is still retained and permitted. Your partner's private answers, notes and credentials are excluded.
The JSONL file is assembled in this page's memory. Account preparation supports up to 10,000 selected records and the browser file limit is 100 MiB. Retrieval credentials are never placed in the file, a link, email or browser storage. Answers that have expired or been erased cannot be restored by an export.
Terms revision sa-terms-2 · processing consent sa-sensitive-2. Earlier alignments retain their original question version.