The short version
Solo Era needs an account, and the account holds your data. Your journal entries, your photos, your progress and your answers to the setup questions are stored on our backend so they come back whole on a new phone. Your phone keeps a copy so the app works offline.
We also keep a short record of how you move through setup and the paywall, so we can see where the app is confusing and which offers work. It is described under "Setup and paywall events" below and never contains your journal.
We do not sell anything about you, we do not track you across other apps or websites, and there is no advertising SDK in the app. RevenueCat provides subscription and paywall measurement, and we keep our own small record of setup and paywall events; both are described below. We do not use a separate general-purpose analytics service.
What we store
| What | Why |
|---|---|
| Your email address | To sign you in, together with your internal account identifier. |
| Your name | The display name you enter or edit, or a name provided by Sign in with Apple, to personalise your pass, screens and reminders. |
| Your journal entries — mission and date, before-and-after nervousity ratings, notes, and titles you give to your own entries | So they come back on a new phone, and so the app can draw how your ratings change over months. |
| Your photos — the picture on a journal entry, downscaled before it leaves your phone | So an entry comes back with its picture. Each account can read and write only its own photos; nobody else's account can see yours. |
| Your progress — XP, level, streak, which missions you have completed, and your weekly reminder day and time | So a new phone shows the level, the streak and the history you built, instead of starting you over. |
| Your setup answers — where you heard about Solo Era, which solo activities you have already done, how you feel about doing things alone, what the hard part is, what you want to be able to do in six months, and your starting mission. Earlier versions also asked about gender and available time; if you answered those, they stay with your account. | To personalise your starting point and understand how people find and use Solo Era. |
| Your unique Solo Pass code (SE- followed by six digits) | To keep a stable pass identifier when your display name changes. It is not a password or permission to read your account. |
| Your own custom missions | So the missions you wrote are yours on any device, not only on the one you wrote them on. |
| Setup and paywall events — a few timestamped events about setup and the paywall, listed below | So we can see where people stop in setup, whether the paywall appears when it should, and which offer leads to a subscription. |
Signing in
You sign in with Sign in with Apple or with a six-digit code we email you. Sign in with Apple may give us your name and an email address, or a private relay address if you choose Hide My Email. We treat a relay address like any other and send your code to it. Supabase's sign-in service creates and checks the code, and Resend delivers the email.
What we never store
- A password for the app. There is none: not at sign-up and not as a fallback. The creator dashboard on our website is a separate system, and administrators there do use a password together with an emailed code. It is described under "Optional creator codes".
- Your location, your contacts, data from Apple Health, or anything from other apps. The app never asks for any of it. The photo you attach to an entry is the one you choose; the app reads nothing else from your library.
- Advertising identifiers. There are none in the app, and the app does not ask to track you.
Setup and paywall events
From version 1.0.7, Solo Era records a few events about how you move through setup and the paywall. We use them to see where people get stuck, whether the paywall appears when it should, and which of our offers leads to a subscription. This is our own record, kept in our own database. It is not sent to an analytics service.
The events are: you started setup; you finished the setup questions; setup was skipped because you came back to the app later; a paywall was shown to you; and your access started after a purchase or a restore. Each event carries when it happened, a random identifier for that app session, the app version and build, whether the app is a store release or a test build, and, where it applies, which offer you were shown, where in the app the paywall opened, and which product you bought. An event never contains your name, email address, answers, notes, ratings or photos.
Events are written on your phone first and uploaded only while you are signed in. Events recorded before you signed in on this phone are uploaded under the account you sign in with next. If you never sign in, nothing is uploaded. When you sign out, events of that account that could not be uploaded are removed from the phone. Once uploaded, events are linked to your account and deleted when you delete your account. Other people's accounts cannot read them. The developer can.
RevenueCat keeps its own record of paywall views and purchases, described under "Purchases". Our events are a separate record, so we can check the two against each other.
A pass number before you sign in
During setup, before you have an account, the app asks our server to reserve a Solo Pass number for you, so the pass you see is the one you keep. The request carries a random token that the app creates on your phone and nothing else about you: no name, no email address and no device identifier. The token is kept in your phone's Keychain, and the app uses it for six days at most. The server holds the reserved number and the token for up to seven days. If you sign in within that time, the number becomes yours and the token is deleted. If you do not, the reservation expires, and expired reservations are deleted whenever the server next assigns a pass number.
Where it is stored, and who can see it
On Supabase, on servers in Zurich, Switzerland. Supabase is our data processor and stores this on our behalf — the rows in a database and the photos in a private storage bucket.
Every row and every photo that belongs to your account is locked to it at the database level, so one account cannot read another's. A few tables hold records that belong to no single account, such as feedback, purchase events and creator accounting; no customer account can read them directly. They are read through the developer's administrator access and, for creator accounting, through the creator dashboard described below. The developer can technically access the database and the storage as its administrator, and uses that access to run the service, to answer support requests, to look at how setup, the paywall and purchases are doing, and for creator commission accounting.
Like any online service, Supabase keeps standard server logs, such as IP address and request time, for a limited period, for security and operation. Several services we use are based in the United States: RevenueCat, Resend and, for the website, Vercel and TypeSafe. What they process for us may therefore be handled there.
Purchases
Subscriptions are handled by Apple and by RevenueCat, which tells the app whether your subscription is active. RevenueCat starts working when the app opens, under a random identifier it creates; when you sign in, that identifier is linked to your internal account identifier, not to your email address or name. RevenueCat receives that identifier, subscription and transaction information, which offer you were shown, and technical information such as device and operating-system details. We never see your payment details — those stay with Apple. RevenueCat also records paywall views and subscription purchase and restoration events so we can evaluate paywall conversion and compare offers. This does not include your journal notes or photos. The paywall uses your display name, your pass code and your starting mission to personalise what you see. Prices, trial availability and renewal terms are shown for your selected offer before purchase.
RevenueCat also sends us a copy of its events for the whole app — such as a purchase, a trial, a renewal, a cancellation, a refund, or being placed in one of our paywall experiments — for every customer, not only for those who use a creator code. We store that copy on Supabase: the event type and time, the product, price, currency, store, whether it was a real or a test purchase, transaction identifiers, and your internal account identifier or, before you sign in, RevenueCat's random identifier. It contains no email address, name, journal entry or photo. We use it to check our own records of paywall results against what was actually bought, to reconcile refunds, and to calculate commission when a creator code applies. Test purchases made in TestFlight or the sandbox are kept apart from real ones.
Creator program applications
If you apply through our website, we collect the name, email address, country or region, content languages, social profile links, optional follower and reach figures, audience description, and collaboration ideas you choose to submit. We use these details to assess the application and contact you about a potential partnership. Applications do not automatically create a creator account or subscribe you to marketing emails.
Applications are stored privately on Supabase and sent to our team at marketing@soloera.app using Resend. We retain application records for review and follow-up; you can ask us to delete them by emailing marketing@soloera.app. To prevent submission abuse, we keep a daily salted network digest rather than a raw IP address; these digests are cleared after 24 hours during subsequent submissions. Your application is not published.
The website and its free tools
The website soloera.app is hosted by Vercel. Like any web host, Vercel processes your IP address and basic request details to deliver pages and to block abuse. We use this to limit how often the optional text box described below can be used from one network. The website has no analytics, advertising or tracking scripts.
The free tools at soloera.app/tools need no account. Your answers are worked out in your browser and are not sent to us. When you share a result, the answer is written into the page address or into an image created on your device, and you choose where it goes. The habit tracker, the routine builder, the solo travel checklist and the comfort zone ladder keep your ticks, choices and nerves ratings in your browser's local storage on your device; we cannot see them, and clearing your browser data removes them. Anything you type into the travel check-in message stays on your device and is not stored. Links to Google Maps or the App Store open those services, which handle your visit under their own privacy policies.
Some tools (the comfort zone quiz and ladder, "What should I do today?", "What to say" and "How to say no") offer an optional text box, marked with a note next to it. If you use it, the sentence you type is sent through our server to TypeSafe (United States), which matches it to a level, a category, an activity or a situation. We do not store the sentence and do not link it to you. If you prefer, use the multiple-choice answers instead; they never leave your browser.
Optional creator codes
If you choose to apply a creator code before your first subscription, we link that code to your internal account identifier. We store the attribution date and the applicable creator agreement so eligible purchases can support that creator. Applying a code does not change your price, plan or trial. The code is also sent to RevenueCat as an account attribute for subscription reporting.
For commission accounting, we process attributed transaction identifiers, products, purchase dates, currency, amounts, trials, refunds, estimated store fees and taxes, and recorded creator payouts. These records are stored on Supabase. Creators can sign in to a private dashboard to see only their attributed sales and earnings. They do not receive customer names, email addresses, account identifiers, journal entries or photos. For creator partners, we store their display name, login email, code, commission rate, agreement dates and details, and contracts or attachments uploaded by the administrator. These attachments are private and available only to authorised administrators and the relevant creator. Payment records include the USD amount, payment date, covered transaction period, reference and payment details, visible to that creator.
Dashboard login codes are sent only to registered partner or administrator emails. Administrators additionally enter a password before verifying an emailed code. Supabase processes the password and stores its protected hash, not a readable password in creator reports. Short-lived login challenges and session approvals enforce this extra check. Dashboard access expires after 12 hours and can be revoked by an administrator. The dashboard keeps your signed-in session in your browser's session storage until you close the tab or sign out. To limit login abuse, we temporarily store attempted login email addresses, hashed network identifiers and timestamps; records older than 24 hours are removed during subsequent login checks. Removing dashboard access preserves financial and agreement records where needed for accounting and resolving disputes.
Feedback you send us
The feedback form in the app lets you pick reasons and write a note, with an optional email address if you would like a reply. It is sent to our server, stored, and forwarded to support@soloera.app by Resend. It is not tied to your account: the app does not attach your account identifier to it. Please do not put anything in it that you would not want us to read. To limit abuse, each submission keeps a daily salted digest of your network address instead of the address itself; digests are cleared after 24 hours when later submissions arrive. We keep feedback until you ask us to delete it or we no longer need it. To have yours deleted, write to support@soloera.app and tell us roughly when you sent it or which reply address you used.
Email is sent by Resend on our behalf: the code that signs you in, your feedback to our inbox, and, for the website, creator applications and dashboard login codes. Resend processes the email addresses and message contents to deliver them.
Notifications
The app schedules local reminders on your device — the weekly mission, and a timer when a mission has one. They are generated entirely on-device and are not sent through any push-notification server. If you allow notifications, a reminder can show your display name and mission title on your lock screen. The app asks for permission once, after you have started using it, and never during setup. You can change reminder preferences in the app and notification previews in iOS Settings.
Widgets
The Home Screen widget shows your current mission, your streak and your latest completed mission from a small file that the app keeps on your phone. The widget does not contact our servers.
Sharing
Sharing a pass, completed mission or journal note opens the iOS share sheet. You choose the recipient or app. The shared content may include your name, pass code, mission, ratings, notes or an attached photo, depending on the item you choose. Sharing is optional; we do not automatically publish your journal or create a public profile. The destination you choose handles its copy under its own privacy practices.
How long we keep it
We keep your account content, including your setup and paywall events, while you have an account. Account deletion removes it from our active account database and storage. Payment providers maintain their own transaction records; deleting Solo Era does not erase Apple purchase records or automatically cancel an App Store subscription.
Some records stay after your account is deleted:
- Purchase and creator-accounting records — the copy of RevenueCat's events, the attribution of a creator code and the commission calculations. They are kept to reconcile purchases, refunds, commissions and our accounting obligations. They may still contain your former internal account identifier, but once your account is deleted we no longer hold your email address or name next to it. They never contain journal entries or photos. Write to support@soloera.app about access or deletion requests for these records.
- Feedback you sent, because it is not tied to your account. See "Feedback you send us".
- Reserved pass numbers you never claimed expire after seven days.
- Backups. If our database provider holds a backup taken before your deletion, your data stays in it until that backup expires under the provider's schedule.
Deleting your account
Your account (top right) → Delete account, inside the app.
That deletes your app account content: your journal, your photos, your progress, your setup answers, your setup and paywall events and your email address. It cannot be undone. The copy on your phone is cleared at the same time. The records described under "How long we keep it" are the exception. To request help with purchase-related data held by our subscription provider, contact support@soloera.app. Manage or cancel your subscription separately in your Apple account subscription settings.
Signing out
Signing out clears the copy on your phone. Nothing is lost — your account still holds it, and signing back in brings it back.
Your rights
You can ask for a copy of what we hold, ask us to correct it, or ask us to delete it, at support@soloera.app. Deleting is faster from inside the app. If you live in Switzerland or the European Union, you can also complain to your data protection authority.
Children
Solo Era is not intended for children under 13, and we do not knowingly collect anything from them.
Changes
When this policy changes, we publish the new version at this address with a new date at the top. If a change affects what the app collects, we also say so in the release notes of the version that makes the change. The current version is always available at this address.
Contact
Questions about privacy: support@soloera.app