What we collect, why, who sees it, and how to get rid of it.
This summary is here to orient you. The detail below is what actually governs, so please read it.
OTAKULT is operated by Jacob Sarradet, an individual doing business as OTAKULT, based in Arizona, United States. For the purposes of the UK and EU General Data Protection Regulation, we are the data controller for the information described here.
Contact: support@otakult.app, or our contact page.
This policy covers the OTAKULT website at otakult.app and the OTAKULT mobile app. It is part of our Terms of Service.
It does not cover third party sites we link to, such as streaming platforms or anime databases. Those have their own policies.
You do not need an account to use the app. Tapping START opens a guest file: Firebase Authentication creates a random account identifier for your phone, with no email address, name, or photo attached, and everything you do in the app is stored under it exactly as it would be under an account. The rows below apply to a guest file in the same way; the difference is that the identifier is the whole of what identifies you. Saving your file adds a sign in to that same identifier, an email address or an Apple or Google account, so nothing is copied or moved when you save. A guest file you do not save is removed after a period of inactivity (see How long we keep it), and you can erase it yourself at any time (see Deleting your account).
| What | When | Stored as |
|---|---|---|
| Email address | Creating an account, saving a guest file to an email address, or joining the app waitlist. A guest file holds no email address. | users/{uid}, waitlist. So the waitlist confirmation is sent only once, waitlist_welcomes keeps a one-way fingerprint of the address, never the address itself. |
| Display name and profile photo URL | Only if you sign in with Google or Apple. Blank for email signups. Apple sends your name only the first time you sign in, and only if you allow it. When you sign in with Google, Google may also collect information such as your phone number and IP address as part of its own sign in, under the Google Privacy Policy. | Your sign in record in Firebase Authentication. If you signed in on our website before August 2026, a copy may also be in users/{uid}. |
| Password | Handled entirely by Google Firebase Authentication. We never see it, store it, or have any way to retrieve it. | not stored by us |
| Your reactions to anime titles: seen, loved, liked, not for me, saved, watching, dropped, plus timestamps. For each reaction you make in the app, that includes the time on your phone and its time zone (its offset from UTC), so your profile can tell what time of day you pick anime. | As you use the app | users/{uid}/anime/{id} |
| A push token for your phone, and which alerts you want | The token only if you allow notifications in the app; your alert choices when you change them in Settings. The token is the address Apple and Expo use to deliver alerts to this install of the app, and on its own it says nothing about you. | users/{uid}: push (the token, the platform, and when it was last updated) and notificationPrefs. Each alert we send is logged in push_log (your user ID, the kind of alert, the title and episode it was about or, for a lineup alert, how many people had saved the lineup, when it was sent, and the delivery receipt), so the same alert is never sent twice. |
| Bug reports: your message, plus app version, platform, OS version, device model, screen size, theme, and a log of roughly your last 50 in app actions. From a guest file, a reply email address as well, only if you choose to type one into the report. | Only when you submit a bug report | bug_reports |
| Lineups you build: a name, an optional description, and the ordered titles in them | As you create and edit them in the app | users/{uid}/lineups/{id}, plus an anonymous public copy if you publish one (see below) |
| A record of what you agreed to when you signed up: the date, which version of these terms and this policy were current, and whether you ticked the box, used a Continue with Apple or Google button, or tapped START to open a guest file. Your email marketing choice is recorded the same way. | Once, when your account or guest file is created (saving a guest file to an account does not write a new one), and again only if you change your email preference. We never rewrite it afterwards. | users/{uid} |
| Titles you ask us to add, or on the website to watch and write up, and helpful or not helpful votes on pages | When you tap those controls. The request or vote itself carries no account or identifier; like other taps, it is also recorded in analytics (see below). | anime_requests, why_requests, page_feedback. Title requests also reach our email inbox via a relay service (see below), carrying the title you searched for and whether it came from the website or the app, with the app's version. A request to watch a title, sent from its page on the website, reaches the same inbox the same way, carrying that title, its catalog IDs and the page link. |
| Anything you write to us through the contact form | When you send it | contact_messages, and our email inbox via a relay service (see below) |
When you create a lineup the app asks whether it is public or private, and starts you on public. If it is public, we create a separate anonymous copy of its name, description, and titles that anyone can see, in the app and on otakult.app. That copy carries no name, account identifier, or anything else that links it to you; the link between a public lineup and its owner is stored where only we can read it, so we can let you edit and unpublish your own. If you allow notifications, we also use it to tell you when people save one of your public lineups: the alert names the lineup and how many people saved it, never who did, and Expo and Apple deliver it like any other alert (see Who we share it with). Taking a lineup private again, or deleting it, removes the public copy. Guest files can publish lineups too, under the same rules; a public lineup from a guest file comes down when that file is erased or expires. The Terms of Service describe the content rules and moderation that apply to public lineups.
Your taste profile is calculated from your reactions: the tones, themes, character archetypes, and studios you gravitate toward, grouped into a handful of distinct taste clusters. We store a summary of it so your recommendations follow you across devices. It is derived from your own activity and nothing else.
We also keep simple counters, such as how many titles you have reacted to and how many you have saved.
On the website, Google Analytics collects standard web analytics: pages viewed, approximate location derived from IP address, device and browser type, referring site, and interactions such as which buttons you press. It sets cookies to recognise returning browsers.
In the mobile app, we collect analytics about how you use it: screens you open, features you use, and actions such as swiping, saving, and finishing a title, along with your app version, device model, and operating system version. These are tied to your account so we can understand how real usage flows through the product.
App analytics never include the contents of private messages, and we do not use any advertising SDK or sell what we collect.
The mobile app also checks for updates to its own code, when you open it and from time to time when you come back to it, so that fixes can reach you between App Store releases. Each check goes to Expo, the service that delivers those updates, and carries your IP address, the version of the app's code you are running, and a random identifier created when the app was installed. If the app crashed while starting up the last time it ran, the next check also carries the error message from that crash, so a broken update can be found and withdrawn. That identifier is not linked to your account, and a check says nothing about what you do in the app.
Our hosting provider processes standard server request data, including IP addresses, as part of delivering the site and protecting it from abuse.
A lot of OTAKULT runs locally, which means some information never leaves your phone or browser at all.
Clearing your app data or browser storage removes all of this. It does not delete your account.
We do not sell your personal information, we do not share it for cross context behavioural advertising, and we do not use it to build advertising profiles.
If you are in the UK or the European Economic Area, we rely on these legal bases under the GDPR:
| Purpose | Legal basis |
|---|---|
| Creating and running your account, syncing your list, generating recommendations | Performance of a contract with you |
| Answering support requests and handling bug reports | Performance of a contract, and our legitimate interest in fixing our software |
| Security, abuse prevention, and service integrity | Legitimate interests |
| Website analytics | In regions that require opt-in consent, your consent, given through the cookie banner. Until you choose, and whenever you decline, the restricted cookieless mode runs on our legitimate interest in knowing our traffic volume. Elsewhere, our legitimate interest in understanding how the site gets used, with an opt-out available at any time through the COOKIES link in the footer. |
| App analytics | Our legitimate interest in understanding and improving how the app is used, and your consent where the law that applies to you requires it. |
| Waitlist signups and any future product email | Consent, which you can withdraw at any time |
| Complying with legal obligations | Legal obligation |
You can import your list from AniList or MyAnimeList by giving us your public username on that service.
Once imported, those titles become your OTAKULT viewing history and are treated exactly like anything else you told us directly.
Two-way sync is optional and needs a saved OTAKULT account. You turn it on by signing in to AniList or MyAnimeList on that service's own site, which then gives the app an access token.
OTAKULT is operated from the United States, and our providers store and process data on servers in the United States. If you use OTAKULT from outside the US, your information will be transferred there.
For transfers of personal data out of the UK or the European Economic Area, our providers rely on the European Commission's Standard Contractual Clauses, or an equivalent approved safeguard. You can ask us for more detail using the contact address below.
| What | Kept for |
|---|---|
| Account, profile, taste profile, viewing history, lineups | As long as your account exists. Deleted when you delete your account, including the anonymous public copies of your lineups. |
| Guest files | A guest file that never finished the opening picks is removed after 30 days. Any other guest file is removed after 12 months without a visit. Removal is final and takes the file's public lineups with it; saving your file to an account stops the clock. |
| Push token and alert log | The token: until you sign out on that phone, delete the app (Apple then reports the token as no longer valid and we remove it), or delete your account. A sign out made with no connection leaves the token in place until one of the others happens. The alert log: as long as your account exists, and deleted with it. |
| Bug reports | Up to 24 months, then deleted. Sooner if the issue is resolved and the report is no longer useful. |
| Contact form messages | As long as needed to deal with your enquiry, and a reasonable period after, in our database and our email. |
| Waitlist signups | Until launch, or until you ask to be removed. |
| Title requests, page votes, visitor counts | Indefinitely. The records themselves carry no personal identifier. Page votes and visitor counts are counts only; a title request is a count plus the title, whether searched for or asked about from its page, kept in our database and our email. |
| Website analytics | Per Google Analytics retention settings, currently up to 14 months. Our own copy of the same events is kept for up to 26 months, then deleted automatically. |
| App analytics | Google Analytics keeps user level data per its retention settings, currently up to 14 months, and deleting your account does not change that. We also keep our own copy of the app's analytics events, which include your ratings, passes and saves, to improve the app and its recommendations. That copy is kept for up to 26 months, then deleted automatically. When you delete your account, we delete the events in our copy that are tied to it within 30 days. Before we do, the titles you loved may be added to the totals in the next row. |
| Totals of titles loved together | Indefinitely. Each total is two titles and the number of deleted accounts whose loves were added to that pair. It holds no account ID, device identifier or date. See Deleting your account. |
We also keep periodic backups of user data so an accident or outage does not destroy your account. Deleted data can persist in a backup for up to 30 days before it ages out.
You have the right to access your data, correct it, delete it, restrict or object to how we use it, receive it in a portable format, and withdraw consent where we relied on consent. Withdrawing consent does not affect anything we did before you withdrew it.
You also have the right to complain to your local data protection authority. We would appreciate the chance to sort the problem out first.
You have the right to know what personal information we collect and how we use it, to request deletion, to request correction, and not to be discriminated against for exercising those rights.
We do not sell personal information, and we do not share it for cross context behavioural advertising, as those terms are defined by the CCPA and CPRA. We have not done so in the preceding twelve months, including for anyone under 16.
Wherever you are, you can ask us for a copy of your data or ask us to delete it, and we will honour it. Email support@otakult.app. We will respond within 30 days, and we may need to verify that the request is really coming from you.
Deleting your account removes your profile, your taste profile, and your viewing history. Erasing a guest file does the same.
You can delete your account from inside the app. Open Settings, scroll to Account, and tap Delete my account. We ask you to confirm and to sign in again, because it cannot be undone. If you are using the app as a guest, the same row reads Erase my guest file, and there is no sign in to repeat. You do not have to ask us, and you do not have to explain.
Most of it goes immediately: your profile, your taste profile, your viewing history, your lineups and the anonymous public copies of them, and your sign in. The rest is finished off by a clean up job that runs daily, so a few remaining records that are keyed to your account, such as delivery records for notifications we sent you and the likes behind our marquee, can take up to a day longer. In every case it is gone well inside the 30 days the law allows us.
If you would rather we did it for you, or you have lost access to the account, email support@otakult.app and we will handle it, within 30 days and usually much sooner. We will not make you jump through hoops.
Our own copy of the app's analytics events goes too: within 30 days we delete the events in it that are tied to your account. Before we do, the titles you loved may be added to running totals of which titles get loved together, which we may use to help improve recommendations for everyone. We add to a pair of titles only when at least 10 other accounts have also loved both; a pair with fewer is left out, not saved. The totals hold just the two titles and a count, with no account ID, device identifier or date. Google Analytics' own copy is not changed when you delete your account; it ages out on its own schedule, currently up to 14 months.
Apart from those totals and Google Analytics' own copy, some information may remain afterwards: anonymous counters that were never linked to you, reports you filed about someone else's public lineup (we keep the report so the complaint survives, but we remove your name from it), and records we are legally required to keep. The counters and reports cannot identify you. A few copies do still hold your account ID for a while: copies inside our backups, until each backup is deleted (our routine backups are deleted after 30 days); the records our database provider keeps of the jobs that carried out your deletion, for about six months; and the deleted analytics events themselves, which can still be restored for up to about two weeks.
Public copies of your lineups stop being served straight away. The one exception is a lineup popular enough to have earned its own page on this website: that page is built in advance rather than looked up each time, so it can take a few days to come down. Cached copies elsewhere, such as a search engine's index or a page someone already has open, are outside our control and clear on their own schedule.
OTAKULT is not intended for children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has given us personal information, email us and we will delete it.
Where local law sets a higher age for consenting to data processing, that higher age applies.
No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects your personal data, we will notify you and the relevant authority where the law requires it.
OTAKULT ranks anime for you automatically, based on the taste profile derived from your reactions. That is the entire point of the product.
It has no legal or similarly significant effect on you. It decides what order anime appear in, nothing more. You can reset it by re running onboarding, or remove it entirely by deleting your account.
We will update this policy as the product changes. The effective date at the top always reflects the current version.
If a change materially affects how we handle your personal information, we will give you notice by email or in the app before it takes effect.
Privacy questions, data requests, and deletion requests: