Effective date: 27 October 2026
This Privacy Policy explains what information Stealth Launch, LLC (“we”, “us”) collects when you use AYearAgo.Today (the “Service”): the website at ayearago.today and the AYearAgo.Today apps for iPhone and Android. It says why we collect it, who we share it with, how long we keep it, and the choices and rights you have.
The Service is run by Stealth Launch, LLC, a company in Puerto Rico (United States). Stealth Launch, LLC is the data controller for the information described in this policy.
Email: ayearagotoday@outlook.com. If you're signed in, you can also message Support from your Inbox on the website or in the app. More ways to reach us are on our Support page.
In this policy, “legal basis” refers to the EU and UK General Data Protection Regulation (GDPR). If you live elsewhere, the same practices apply to you.
When you create an account, on the website or in an app, we collect your username, email address, password and time zone, and whether you want our newsletter. Your password is stored only as a secure hash; we can't read it. We record that you accepted our Terms of Service, acknowledged this policy and confirmed you are 13 or older, with the date and time.
As you use the Service we also keep your settings (for example default visibility for to-dos, whether your planner activity shows on your entries, the Premium badge, email notifications and 18+ entries), the people you block, your experience points, level and achievements, and when you joined and last signed in.
If you change your email address, we keep the new address and a one-time confirmation link until you confirm it or the link expires. If you create personal access tokens (a Premium feature for connecting other apps), we keep each token's name, permissions, a secure hash of the token, when it was last used and the IP address that last used it.
In the apps, your sign-in is kept with tokens that expire. We keep a record of each app sign-in session so we can sign you out, including on other devices when you delete your account.
Legal basis: performance of our contract with you, the Terms (Article 6(1)(b) GDPR). Security records are kept for our legitimate interest in protecting accounts (Article 6(1)(f)).
You can sign up or sign in with another account instead of a password. We never receive your password for that account.
Google, Apple and Meta handle your sign-in with them under their own privacy policies.
Legal basis: performance of our contract with you (Article 6(1)(b)).
We store what you create so we can show it to you and, when you choose, to others: journal entries, photos with their titles and descriptions, logs and log entries with their images, to-dos and habits with their progress, journal prompts and answers, personal achievements, comments, likes and favorites, and your profile biography and profile photo.
When you upload an image we resize it and save a new copy, which removes embedded information such as the location where a photo was taken. In the apps, you choose which photos to upload with your phone's photo picker; the app doesn't read the rest of your photo library.
New journal entries are private unless you publish them. You decide, item by item, what to publish, and you can make published items private again or delete them.
When you ask for an account backup, we build a zip file of your content (including the private messages you sent and received) and keep it for 7 days so you can download it. Then it is deleted.
Legal basis: performance of our contract with you (Article 6(1)(b)).
Your profile page is public: your username, profile photo, biography, the date you joined, your level and experience points, your achievements, statistics such as how many entries you've published, your to-do counts and writing streak, and your latest published entries, photos and logs.
Anything you publish (journal entries, photos, logs, and to-dos or habits you make public), and comments you write on published items, can be seen by anyone, including people without an account. Public profiles and published items are listed for search engines such as Google, so they can appear in search results. 18+ entries aren't listed for search engines. If you make something private or delete it, it disappears from the Service right away, but search engines and people who copied it may keep their copies for a while.
Members can also see your username next to your comments and on messages you send them.
Private messages are visible to you and the person you're writing to. They are sent over an encrypted connection and stored on our servers, but they are not end-to-end encrypted, so they are technically readable on our servers.
Legal basis: performance of our contract with you (Article 6(1)(b)); reviewing reported messages is in our legitimate interest in keeping members safe (Article 6(1)(f)).
Your journals, logs and messages may contain sensitive information, such as about your health, weight or fitness, beliefs, relationships or sex life. We treat everything you write as private by default:
You decide what to write, and you can delete it at any time. Please think before publishing sensitive information about yourself, and don't post sensitive information about other people.
Legal basis: we store and show your content because you ask us to as part of the Service (Article 6(1)(b)). For sensitive information that you choose to publish, we also rely on your having made it public (Article 9(2)(e)).
At signup you confirm that you are 13 or older. We record that confirmation with the date and time.
App-store age signals. On iPhone and Android, the app may ask the App Store or Google Play for your age range (not your birthdate) and, where the law requires, whether a parent has approved. We store the age range, how it was confirmed (for example, declared by you or by a parent), and any parental-control or approval status with your account (one record, updated each time; if you later decline to share, we keep the last age range) to apply our age rules: people under 13 can't sign up, people under 18 can't see 18+ entries, and if an app store says an existing member is under 13, our team is alerted to review the account.
18+ entries. Authors can mark journal entries 18+ when they deal with adult themes. These entries are hidden by default, on the website and in the apps. You can turn them on only on the website, at Settings → 18+ entries, by giving your birthdate and confirming you are 18 or older. We store your birthdate and that confirmation with the date and time. The apps can't turn 18+ entries on; they follow the website's setting and can turn it off. On the website, we also ask you to confirm you're 18 or older before each 18+ entry opens; that confirmation is kept in your sign-in session only for that visit.
If you give a birthdate showing you are under 18, we don't keep the birthdate. We record only the time of that answer, so 18+ entries stay hidden on your account and the check can't be retried. If you made a mistake, contact us.
Age answers are based on what you or your app store tell us; we don't check identity documents.
Legal basis: our legal obligations where the law requires age checks (Article 6(1)(c)) and our legitimate interest in keeping adult themes away from minors (Article 6(1)(f)).
On the website, Premium is billed by Stripe. We send Stripe your email address, username and account number. Stripe collects your card details and billing address (used for tax) directly; we never see or store your full card number. We store your Stripe customer and subscription IDs, your plan, the subscription's status and when the current period ends.
In the apps, Premium is bought through the App Store or Google Play, which handle the payment under their own terms and privacy policies. We use RevenueCat to confirm purchases and renewals. When you open the Premium screen, even before you sign in, the app connects to RevenueCat with an anonymous RevenueCat ID and basic store and device information, such as your platform, app version and store country, so it can show the store's prices. After you sign in, your purchases are linked to your AYearAgo.Today account number. RevenueCat receives the store's purchase and renewal records for your subscription and tells us whether your Premium is active. We store the product, the store, whether it renews, and when it ends.
Legal basis: performance of our contract with you (Article 6(1)(b)), and our legal obligation to keep accounting records (Article 6(1)(c)), which Stripe, Apple and Google meet with their own records.
Anyone can report content or people: signed-in members with the Report links on the website and in the apps, and anyone with our public report form or our form for removing intimate images shared without consent.
Legal basis: our legal obligations, including under the EU Digital Services Act and US law on intimate images and child safety (Article 6(1)(c)), and our legitimate interest in keeping the Service safe and enforcing our Terms (Article 6(1)(f)).
We send emails through Mailgun. They include: welcome and account emails, password and username recovery, email-change confirmation, account-deletion links, notices that a backup is ready, report receipts and outcomes, and moderation decisions.
If someone comments on your content, or mentions you in a comment, journal entry or photo, we email you a notification. It includes the comment's text, or the title of the entry or photo you were mentioned in. You can turn these emails off in your profile settings.
If you sign up for our newsletter, we send it to your email address until you unsubscribe in your settings (the link in each newsletter takes you there).
Legal basis: performance of our contract with you for account and notification emails (Article 6(1)(b)); your consent for the newsletter (Article 6(1)(a)), which you can withdraw at any time.
When you email us or message our Support account, we receive your email address or username and whatever you tell us. We use it to answer you and keep a record of what was asked. Our support mailbox is hosted by Microsoft (Outlook.com).
Legal basis: our legitimate interest in answering questions (Article 6(1)(f)), or performance of our contract with you when your message is about your account (Article 6(1)(b)).
How long each record is kept is in How long we keep information.
Legal basis: our legitimate interests in securing the Service and in showing view counts (Article 6(1)(f)), and our legal obligation to keep personal data secure (Article 6(1)(c)).
The website uses cookies to keep you signed in, protect forms, remember your language, count unique views and remember that you closed the cookie notice. We don't use advertising cookies. See our Cookie Policy.
The website loads its fonts from Google Fonts, so your browser sends your IP address and browser information to Google when it fetches them.
Links such as “Share on Facebook” and “Share on Twitter” open those sites; they receive the page's address only if you click.
The apps use your phone's time zone to set up your account. They contain no advertising, analytics or crash-reporting software, don't use advertising identifiers, and don't track you across other apps or websites. Pages from ayearago.today, such as this one, open in a browser, where our Cookie Policy applies.
We don't sell your personal information, and we don't share it for advertising. We share it only with the companies that help us run the Service, each for the purpose listed:
Every third party we share your information with provides the same or equal protection of your information as described in this policy. Each may use it only to provide its service to us, or as its own privacy policy describes for the parts it controls (such as App Store, Google Play and Stripe payments).
We also share information when we must:
We and our main providers are in the United States, so your information is stored and processed there, wherever you use the Service from. When information from the European Economic Area, the United Kingdom or Switzerland goes to a provider in another country, we rely on the provider's certification under the EU-U.S. Data Privacy Framework (and its UK and Swiss extensions) where it has one, and otherwise on the European Commission's Standard Contractual Clauses (with the UK Addendum). You can ask us for a copy of these safeguards.
We keep information only as long as we need it. Deleted information also stays in our server backups until they are overwritten.
| Information | How long |
|---|---|
| Your account, content, photos, messages, settings and age confirmations | Until you delete them or your account |
| Server backups (copies of the database and uploaded files) | Overwritten within 30 days |
| Account backup files you ask for | 7 days |
| View-count records with IP addresses | 90 days (the totals stay) |
| Server logs | Up to 90 days |
| Failed sign-in records | 30 days |
| Password and username recovery requests | 7 days |
| The last IP address that used a personal access token | Cleared 90 days after the token was last used |
| App sign-in session records | Deleted once the session expires (at most 30 days without use) |
| Our subscription records | Until you delete your account. Stripe keeps records of web payments as tax law requires; Apple and Google keep their own purchase records. |
| Reports and moderation records | As long as needed for safety and legal reasons. If you delete your account, reports you made stay without the link to your account, and reports about your content or account keep your username and the copy of what was reported. |
| Evidence copies of reported files | Until the report is closed; child-safety evidence 365 days after our action, or longer if the authorities ask |
| Support emails and messages to Support | As long as needed to help you and keep a record of the request |
| Newsletter subscription | Until you unsubscribe or delete your account |
You can delete your account at any time:
Deletion is immediate and permanent, and you'll see a confirmation on screen when it's done. We delete your profile and sign-in details, everything you created and uploaded (including the files), your comments, other members' comments on your posts and the replies in your comment threads, the private messages you sent and received (for the other person too), your likes, favorites, achievements, notifications, tokens and backup files, and our billing records. Other devices are signed out, and we delete your customer record at Stripe and your subscriber record at RevenueCat.
Subscriptions: deleting your account cancels a web (Stripe) subscription at once; unused time isn't refunded. If we can't reach Stripe to cancel it, your account isn't deleted and we ask you to try again, so you're never left paying for an account you can't sign in to. Deleting your account does not cancel a subscription bought through the App Store or Google Play. Cancel it in your store account settings, or the store will keep charging you.
What stays: copies in server backups until they are overwritten, the security records, payment records and reports described in How long we keep information, and notifications and emails other members already received (for example about a comment you wrote), which may still show your username and what you wrote. Likes and favorites other members gave your posts may still show your username and the post's title in their lists. If the law requires us to preserve an account's data, for example during a child-safety investigation, we can't delete that account until the obligation ends.
Wherever you live, you can ask us to:
Email ayearagotoday@outlook.com from your account's email address, or message Support while signed in. We answer within one month. If a request is complex, we may need up to two more months, and we'll tell you why within the first month. To protect your account, we may need to confirm that the request comes from you.
If you live in the EU or UK, you can also complain to your data protection authority. We'd appreciate the chance to help first.
We don't sell or share personal information for targeted advertising, and we don't make decisions about you based solely on automated processing that have legal or similarly significant effects. The blocked-words check only stops text from being saved; a person reviews every report.
The Service is for people 13 and older. At signup you must confirm you are 13 or older, and where the App Store or Google Play tells the app that you are under 13, you can't sign up. We don't knowingly collect information from children under 13. If we learn that we have, we delete the account and its information. Parents who think their child under 13 has an account can contact us.
Members under 18 may not view 18+ entries, and they stay hidden whenever we know a member is under 18. If you're under 18, you can delete anything you posted at any time, or ask us to remove it; copies other people made may remain.
No system is perfectly secure. If a breach puts your information at risk, we'll tell you and the authorities as the law requires.
Our point of contact for authorities and for people who use the Service, under the EU Digital Services Act, is ayearagotoday@outlook.com, in English. See Contact points on our Support page.
When we change this policy, we post the new version here with a new effective date. If a change is significant, for example a new use of your information, we'll tell you before it takes effect by email or with a notice on the Service, and we'll ask for your consent where the law requires it.
Questions about this policy or your information: ayearagotoday@outlook.com.