Privacy Policy

1. What We Collect

When you use Actually, we collect the following data:

• Account information: email address and display name (provided during sign-up or via Google Sign-In or Sign in with Apple)
• Audio recordings: voice recordings you make, or audio files you upload, in the app for fact-checking. Audio is sent to our server and to a speech-to-text provider (see Section 3) to be turned into text. Our server holds audio only while it is being processed and then deletes it; we do NOT keep your recordings.
• Transcripts and content you submit: the text transcript of each session, the claims found in it with their verdicts and sources, the claims found in screenshots you submit (the screenshot itself is not stored), and questions you ask. Transcripts, fact-check results, saved questions and research reports are stored in your account.
• Usage data: session history, fact-check results, credit balance, and purchase history
• Onboarding preferences: language choice and content interests selected during setup
• Games (Hunch, Your Move, the daily line, and the party games Hot Seat and Sooner or Later): We collect the True or False calls you make in Hunch and whether you marked a card Sure. We collect the place you choose for each event on the daily line and whether it was right. We keep the dates you played and your days-played streaks. We keep the challenge links you send and what is stored with them (see Section 5). When you start a party game, we keep a record of the cards dealt to you (see Section 5). We also keep the yes or no result of the age question that decides whether sharing is on. Your birth year is not saved. The nicknames, colours, scores and calls at a party game table stay on your phone and are not collected, with two exceptions. A challenge you send stores the calls and counts described in Section 5. We also collect pseudonymous analytics counts, such as how many players called a card right, with no names (see Section 3).
• Feedback you send: the subject and message you send through the app's feedback form, together with your email address so we can reply
• Creator program (only if you apply): your name, platform, channel link, audience size, bio and requested code; if you are accepted, your country and payout account ID, and the sign-ups and commissions linked to your code. If you use a creator's code, we record which creator referred you.
• Diagnostic and analytics data: crash reports, error logs, and pseudonymous product analytics events (see Section 3)

2. How We Use Your Data

• To provide real-time AI fact-checking services
• To manage your account and credit balance
• To process in-app purchases
• To send transactional emails (sign-up confirmations, password resets, trial reminders) and service and account notices (e.g. outages, changes to your account, credits or these terms)
• To diagnose crashes and improve app stability
• To improve our service and app experience through aggregated, pseudonymous analytics

3. Third-Party Services

We use the following third-party services:

• Supabase: authentication and database (your account data, sessions, transcripts and fact-check results)
• Render: hosting for our server. Your audio, transcripts and the other content you submit pass through it while they are processed.
• Groq: our main speech-to-text provider (Whisper). Groq receives the audio of your recordings and uploads and returns the text. Groq is also a backup AI provider for fact-checking (see Anthropic below).
• xAI, OpenAI and AssemblyAI: backup speech-to-text providers. If Groq is unavailable, your audio is sent to one of them instead (each only while we have it switched on).
• Anthropic (Claude AI): AI-powered fact-checking analysis. Anthropic receives the text of your transcripts, the claims found in them, screenshots you submit, questions you ask, and web search results, in order to find and check claims. If Claude is unavailable, OpenAI or Groq may process the same content as a backup (Groq does not receive screenshots).
• Serper: web search (Google search results) used to check claims. Serper receives the text of each claim or question being checked as a search query, not your name or email address.
• RevenueCat: in-app purchase management. RevenueCat receives your purchase records and your internal account ID.
• Apple App Store and Google Play Billing: subscription and payment processing
• Google Sign-In and Sign in with Apple: optional authentication methods. If you use one, Google or Apple shares your email address (Apple may share a private relay address) and your name with us (with Apple, only if you choose to share it). For Sign in with Apple we also keep a token from Apple so we can revoke the app's access when you delete your account.
• Sentry: crash reporting and error monitoring. Sentry receives technical data such as error stack traces, device model, OS version and, on Android and on our server, your internal account ID, to help us diagnose bugs. When a request to our server fails, the error report can include the first part of that request (up to about 10 KB), for example the text of a claim or question being checked.
• Mixpanel: product analytics. We send pseudonymous events (e.g. "onboarding completed", "fact-check started") to help us understand how the app is used and improve it. On iOS, events are tied to an identifier Mixpanel creates on your device; on Android, to your internal account ID. Events do not include your email, your name, your audio or the content of your fact-checks. We send these events to Mixpanel's EU servers.
• Resend: transactional email delivery. We use Resend to send sign-up confirmations, password resets, trial reminders, and service and account notices. Resend processes your email address (and, in trial reminders, your name) to deliver these messages. When you send feedback or apply to the creator program, Resend also delivers what you wrote, with your email address, to our team's inbox.
• Expo (EAS Update): delivers app updates. When the app checks for an update, Expo receives technical data such as your IP address, device platform and app version.
• Stripe: payouts for our creator program only. If you join the program, we share your email address and country with Stripe to set up your payout account, and Stripe collects the payout details it needs directly. Stripe is not used for in-app purchases.

Each of these services handles the data it receives under its own terms and privacy policy.

Our website, actuallyai.app (including the creator dashboard), is hosted on Cloudflare and loads fonts from Google Fonts; the creator dashboard also loads code from the esm.sh CDN. These services receive your IP address and browser details when you visit.

We do NOT sell your data to any third party.

4. Data Storage & Security

All data is encrypted in transit using TLS/SSL. Your data is stored securely on Supabase servers. Audio recordings are held on our server only while they are being transcribed and are then deleted; transcripts and fact-check results are stored with your sessions.

To answer repeated checks faster, we also keep a shared cache of claims and questions that have been checked, with their results. Cache entries do not include your name, email address or account ID, so they are not removed when you delete your account. We stop reusing an entry 60 days after it was last updated.

5. Challenge and game pages (link.actuallyai.app)

The games use public pages on link.actuallyai.app: /c is a challenge link that a friend plays in a browser, /d is the page for a day's Hunch set and /line is the page for a day's daily line, both of which anyone with the link can play. Two short links send you on to another place: /get to the App Store or Google Play (on a computer or other device, to actuallyai.app), and /class to actuallyai.app. None of these pages asks for a name, an email address or an account.

What we store for a challenge

• The animal avatar chosen by the sender and by the friend who takes the seat (a preset picture, not a photo or a name)
• The cards in the set and the calls on them (True or False and whether a card was marked Sure; Let it stand or Call cap in a Hot Seat challenge; the place each event was put in a Sooner or Later challenge), with the scores that follow
• A hashed seat code. When a friend takes the seat, their browser receives a random game code, and we keep a one-way hash of it, not the code. That lets us recognise the same browser if the page is reloaded, and tells any other browser that the seat is taken.
• Timestamps: when the challenge was created, when the seat was taken, when it was finished, when it expires, when the sender saw the result and, if the link was cancelled, when it was cancelled
• If the sender removed a card from the score after the game, which card was removed
• The account that sent it, so the challenge appears in the sender's list in the app

The other player sees your avatar and your calls on that challenge, not your name or email address.

What the browser keeps

• On /c, one game code in local storage, so that reloading the page returns you to your game
• On /d, your calls for that day's set in local storage, so that reloading does not lose them. Each call is also sent to our server to get its verdict. We keep anonymous totals (for example how many times the page was opened or a set was finished), not your individual calls.
• On /line, your placements for that day's line in local storage, so that reloading does not lose them. Each placement is also sent to our server to get its reveal. We keep anonymous totals, not your individual placements.
• No cookies and no analytics scripts

You can remove what the browser keeps by clearing site data for link.actuallyai.app.

Party games (Hot Seat and Sooner or Later)

A party game is played on one phone. Other than the calls and counts a challenge you send stores (below) and pseudonymous analytics counts such as how many players called a card right, with no names (see Section 3), the nicknames you type, the colours, the scores and the calls at the table stay on that phone and are not sent to us. When you start a game, the phone asks our server for cards. We record which cards were dealt to your account, so that the next game does not repeat them, and we keep your latest 20 deals for each game; older ones are deleted as you deal new ones. A record holds the game, the deck, the cards, how many were shown and when they were dealt. It holds no players, names, scores or calls.

If you send a challenge from a Hot Seat game, we store the calls of the player you chose on the challenge cards, with no nickname. If you send one from a Sooner or Later game, we store the table size and, for each challenge card, how many people placed it and how many placed it in a wrong spot, with no names.

The daily line

The daily line is stored per account, as Hunch is: for each line you play, the place you chose for each event, whether it was right, the date you played and your days-played streak, which is counted separately from Hunch. The page for a day's line (/line) asks for nothing about you; what it keeps in your browser and what we count are described above.

Class and the store link

A Class link (/class) counts the visit in a daily total and sends you on to actuallyai.app. We collect no student data: no names, no emails and no accounts. The store link (/get) works the same way: it counts the visit in a daily total and sends you to the App Store or Google Play (on a computer or other device, to actuallyai.app).

IP address

We use your IP address to limit how many requests one device can make, so the pages cannot be overloaded or abused. We use it for nothing else and do not store it with the challenge or with any other Play data. As with any website, your IP address is also processed by our hosting provider (Render, see Section 3) to serve the request, on /c, /d, /line, /get and /class alike. The pages load the Actually mascot picture from actuallyai.app, and apps that show a preview of the link load its preview picture from there too. actuallyai.app is hosted on Cloudflare (see Section 3), so Cloudflare also receives the IP address and browser details of the device that loads these pictures.

How long it is kept

A challenge link stops working 7 days after it is created. The challenge record (avatars, calls, scores, table counts and timestamps, including the friend's side) stays with the sender's account, so the sender can see past results, and it is deleted when the sender deletes their account (see "Delete Your Account" below). The record of cards dealt to you for party games keeps your latest 20 deals for each game and is also deleted when you delete your account.

The age question

Before you share a result or send a challenge, the app asks for your birth year. It is sent to our server to work out a yes or no answer, and it is not saved in our database. Your profile keeps the yes or no result and nothing else about your age. If the answer is no, sharing stays off.

Disputes

If you dispute a verdict, we store the card, which game it was in, the reason you picked from a fixed list, whether you sent it from the app or from a challenge page, the date and, for a dispute sent from a challenge page, which challenge it came from, so that a person can review it. A dispute sent from the app is linked to your account; if you delete your account, the dispute stays without that link. If your phone is offline when you dispute a card in a party game or on the daily line in the app, the dispute waits on your phone and is sent the next time the app can reach us. On the page for a day's Hunch set (/d) and the page for a day's daily line (/line), the dispute link opens an email to moderation@actuallyai.app in your own mail app, and so does the Report link in the footer of /c, /d and /line. We receive your email address and what you write, and keep it in our team's inbox. These emails are not linked to an account, so deleting your account does not remove them.

6. Your Rights

You have the right to:

• Access your personal data
• Request correction of your data
• Request deletion of your account and associated data (see "What we keep" below)
• Export your data
• Opt out of analytics (contact us via email)

7. Data Retention

We retain your data for as long as your account is active. When you request account deletion, your data is permanently deleted within 30 days, except the limited records listed under "What we keep" below, including copies of emails in our team's inbox, such as one sent from the Report link on a challenge page (/c) or the dispute link on a daily or line page (/d or /line).

8. Children's Privacy

Actually is not directed at children under 13. We do not knowingly collect data from children under 13. If you believe we have collected data from a child under 13, please contact us immediately.

9. Changes to This Policy

We may update this policy from time to time. We will notify users of significant changes through the app.

10. Contact Us

For any privacy-related questions or requests, contact us at:

Email: support@actuallyai.app