Privacy Policy
Effective date: October 9, 2026 (version 1.1.0 adds “Where to eat”)
The short version
- No account. No sign-up, no email, no password.
- Local-first. Your ideas, jar, plans, standing-date cadence and memories live in a database on your phone. Unlinked, nothing about them ever leaves it.
- No analytics SDK, no ad network, no tracking across apps or websites.
- Location only if you use “Where to eat”, only approximately, only while you are searching, and never stored.
- Linking a partner (optional) shares only what the table below lists, with exactly one person, once you choose to set it up. Unlinking deletes the shared record for both of you.
- Surprise-date clues never sync. They stay private to the phone that wrote them, by design.
What stays on your phone
Your idea jar, your plans, your standing-date cadence and key dates, your memories (including any photo you attach), your challenge progress, your Surprise-date clues, and your settings are stored in a database on the device. You can export the whole thing to a JSON file and restore it on another phone. Deleting the app deletes all of it.
Location and “Where to eat”
The idea library names a kind of place, never a specific business, and most of Standing Date never asks where you are. One feature does: Where to eat, which finds a real restaurant that is open near you.
- It asks first. Nothing is sent until you tap “Use my location” (or type a city or neighbourhood instead, in which case your device’s location is never read at all).
- It is approximate. The app requests approximate location only. Before the request leaves our server the position is rounded to three decimal places, roughly a city block.
- Where it goes. The rounded position, your search radius, the cuisines you picked and your app language go to our server and from there to Google Places (Google LLC), which returns the list of restaurants. Google’s privacy policy applies to its handling of that request.
- What we keep. Our server stores no location, no restaurant and no history. It keeps one counter per app install per day — how many searches that install has made — to enforce the daily limit, and deletes it after seven days.
- What stays on your phone. What the feature learns about your taste, the places you thumbed up or down, your never-again list, and the place you kept for a plan (Google’s place id and its name) are stored on your device only, and are included in your backup file.
When a plan includes “find places nearby” or “Directions,” that link opens your device’s own maps app, and your position there is handled entirely by that app, not by us.
Linking a partner’s phone (optional)
If you never create or join a pairing code, nothing in this section applies to you.
If you link another phone, an anonymous identity is created at that moment — not at install — with no email, name or password, using a six-character code you type by hand. From then on, and only between the two of you:
| What syncs | Why |
|---|---|
| Your standing-date cadence and its history — interval, day, time, and days since your last date | so either phone shows the same standing date and the same streak |
| Your current plan — the kept idea, its steps, bring list and status | so either phone shows what tonight’s plan actually is |
| Your date jar — the ideas you both added | so either phone can draw from the same jar |
| Your memories — the rating, note and photo saved after each date | so you share one scrapbook, not two |
| The restaurant kept for the current plan — Google’s place id and its name | so either phone shows where you are going |
| Your “Where to eat” taste, as totals only — a score per cuisine, price band and distance band, and per-restaurant thumbs up, thumbs down and never-again marks | so either phone can pick a place you will both say yes to |
| A Two thumbs round while it is open — the four restaurants dealt (place id, name, cuisine, price band, distance band) and each person’s yes or no on them | so you can both vote; the round is replaced by the next one and deleted within 24 hours |
What never syncs, by design: Surprise-date clue text stays private to the phone that created it, so a surprise can stay a surprise; your location, the list of restaurants a search returned, your search filters, your device settings, your challenge progress and your raw local database never leave the phone for your partner either way. A row is readable only by the two members of that pair, enforced by the database itself.
Either person can unlink at any time, which deletes the shared pair record for both of you — see Delete synced data.
Purchases
Purchases are handled by the App Store or Google Play and processed through RevenueCat, which receives an anonymous install id (a random UUID generated on your phone) and your purchase status so your Plus access survives a reinstall. We never see or store payment-card details.
Invite a Friend (Optional)
If you use Invite a friend, the entire payload is: your app install id, your RevenueCat customer id and the invite code. That is all that is ever sent. No email address, no contacts, no name, no device fingerprint, no location. The code exists so both sides can be granted 30 days of Standing Date Plus; the install id exists so a code cannot be redeemed twice on the same phone. Nothing about your ideas, your plans or your memories is involved.
Children
Standing Date is not directed to children under 13 and we do not knowingly collect personal information from them.
Your rights
Because there is no account, most of your data is already entirely in your hands: export it, delete it, or delete the app. For anything synced to a pair unlink in the App or write to us. Where the GDPR or the CCPA applies, you have rights of access, correction, deletion and portability; we do not sell personal information and never have.
Changes & contact
We may update this policy; material changes will be reflected by a new effective date here. Questions or requests: dev@adelyons.com.