Here is the path it takes, where it sits and how it is protected. No marketing fog: everything on this page is in the code that way.
You type something. Up to here nobody has seen it.
The connection is encrypted (TLS), like online banking. The session cookie is httpOnly and only set over HTTPS.
Sensitive fields are encrypted BEFORE they are stored: birth data, names, notes, chats, messages to friends, medication, cycle. 198 fields across 63 tables.
What you upload, meaning IDs, documents inside a plan and attachments in a conversation, is encrypted before it leaves the server and sits in the media store as ciphertext too. Images and songs sit there unencrypted, because your device has to show and play them directly. They only come out through your login, which issues a short-lived link for them. The exception is whatever you published or shared as a card yourself.
On the website: no tracking, no advertising cookies, no analytics services. The cookie notice names exactly one purpose: your login.
We don't build tracking pixels into our emails. Whether the sending service adds one is a setting on their side. We keep it off and check it. If you want to be sure: don't let your mail app load images automatically.
And loading this page, your browser only asks smplyou.com. The font is hosted by us instead of Google, and Stripe's script only loads when you actually pay. Open your browser's network tab and check. In front of smplyou.com sits Cloudflare as protection and cache, see below.
Never sold. SMPLYOU is self-funded; there is nobody we owe data to.
Error reports go out without personal data (send_default_pii=false). We see THAT something broke, not who it happened to.
Passwords exist only if you want one. The normal way in is a link by email. A password you set is stored as a hash (PBKDF2-SHA256, salted), never in plain text.
Your name, your age, your birthday (day and month, without the year) and the blueprint our server calculated from them. Your year, time and place of birth are NOT sent along: they are needed here to calculate the blueprint, not there to interpret it. If you've saved a current location, its name goes along, so the date and time are right for you. Depending on the feature, your daily mood, your journal, your cycle, your medications, what Alfred has remembered about you and whatever you've noted about yourself go along. If you ask about another person or a plan, their blueprint or the plan's content goes along. Every text is written there: the chat, but also your daily reading, your month and your year.
Only if you refine your writing profile with your own texts: those texts, once. We only store the rules drawn from them and two made-up examples, not your texts themselves. When Alfred drafts something for you, the rules go along.
Only if you connect SMPLTAX in your account: the lines of your work week, that is deadlines, how many receipts are open, logged hours and the titles of your own tasks. No amounts, no customer names, no email texts. They go along when you ask Alfred about your work and when your weekly look-back is written.
When you generate an image: your description, and for a hero avatar your photo. When something is read aloud: the text being read. For a song: title, lyrics, style and the name and short portrait of the person it is about, for a content check.
Only when you create a song: the text, the style and the description it is made from.
Only when a song or a read-aloud voice is made with ElevenLabs: the text or the song description it is made from.
Only when you pay: your payment details. We never get to see your card number. It is also the only case where an outside script runs in your browser.
Your email address and the content of the mails we send you.
Every request to smplyou.com passes through Cloudflare: it delivers the site quickly and protects it from attacks. Cloudflare sees your IP address and which address you request. Your images and songs are stored there too, and your uploaded documents, those encrypted.
Place names you type in, for your birthplace and for places in a plan, so we can find the coordinates. When a plan shows a map, your browser loads the map images directly from OpenStreetMap. OpenStreetMap sees your IP address when it does.
When a plan needs places or routes: the name of a place, the start and end of a route. That's where photos, opening hours and travel times come from.
When you ask about flights or one is in a plan: airports, date and flight number.
For train and bus connections: start, destination and time.
When you ask about the weather: the coordinates of the place.
For charging stops with good food: points along your route.
Error reports when something breaks. Personal content is switched off; an identifier such as your account ID can still appear in one.
Only in the app and only if you allow notifications: your device's push token and the text of the notification. Your device fetches the token and the app's updates from Expo itself.
This is where our server and our database run, in Frankfurt.
Whoever gets hold of the database gets ciphertext. But the server itself has to be able to read your data in order to show it to you. So “encrypted” here means: protected against theft and against copies of the database. It does not mean that nobody with server access could technically read it.
Not only when you talk to Alfred. Your daily reading, your month, your year and every other text about you are written by an AI model. Your name, your age, your birthday (day and month) and your finished blueprint go there for that, every time. Your year, time and place of birth stay here: our own server calculates the blueprint, the model only interprets the result. That's not a side effect, that IS the feature: without this path there would be no reading. If you've saved a current location, its name goes along too. What Alfred doesn't need for an answer, he still doesn't get. A plan you don't mean isn't included.
What you write to a friend sits encrypted in the database, like your chats and blueprints. But not end to end: the server has to be able to read the lines in order to show them to the other person. No AI reads along there on its own. In conversations between people, Alfred is only the messenger: if you ask him, he puts your message or a plan in. Two exceptions: if you have a conversation summarized, its history goes to the model for that. And what you write to us yourself is sorted by a small model as a bug, a wish or a question.
Invite someone into a plan and they see what is in that plan. That is exactly the point. You decide per building block who sees what, and single files can be locked. Your cycle, your medication and your private notes are never part of it.