Privacy Policy

Recallio is run by Henry Joel Majer and Vikram Goel, a partnership trading as Recallio (ABN 65 319 410 673), PO Box 494, Fortitude Valley QLD 4006, Australia (“we”, “us”). This policy explains what personal information we collect, why, who we share it with, how long we keep it and what you can do about it. Questions or requests: privacy@recallio.com.au. Our privacy contact is Henry Joel Majer.

• Your account. The email address you sign in with, whether you used Google or an emailed code or link, and (for Google) Google's ID for your account. When you signed up, confirmed your email and last signed in. We never see a password. Why: to sign you in and keep your decks, styles and credits with your account.
• What you agreed to. Each version of the Terms and this policy you agree to, when, how (signing up, Google, signing in or the update prompt) and your confirmation that you are 18 or older. Why: a record of what you agreed to.
• Sign-in records. When you ask to sign in by email we store the address with a scrambled (hashed) copy of the link and code we send you. Why: to check the link or code and to limit repeated attempts.
• Lectures you upload. Files (PDF, PowerPoint, Word, text, Markdown) or notes you paste, the file name and a fingerprint (hash) of the file. Why: to make your cards. The fingerprint also lets us stop a file that was removed after a copyright notice from being uploaded again.
• What we make from them. Your decks and cards, images of each slide or page, the text we extracted, the intermediate results we use to regenerate a deck, and any focus notes you type for a deck. When you edit or regenerate a card we record that, with the card's text before and after an edit. Why: to show, export and regenerate your decks, to limit regenerations and to see how often cards need fixing.
• Your settings and feedback. Your card styles, ratings and comments. Why: to write cards your way and to improve Recallio.
• Credits and usage. Your credit balance and history, how many pages and cards each deck used, what each deck cost us to make, the days you used Recallio and, if a tagged link brought you here, which channel. Why: to run credits and plans, keep the service within its budget and count active users.
• Payments. If you subscribe to a plan, Stripe handles the payment. We store Stripe's IDs for you and your subscription, your plan, its status and renewal date, and for each payment the invoice ID, amount and any refund. You enter your card details on Stripe's page: we never see or store your card number. Why: to give you your plan's credits and handle cancellations and refunds.
• One free trial and one first-week discount per person. A keyed one-way hash of your email (a scrambled fingerprint that can't be turned back into the address), a keyed hash of its domain (the part after the @) and whether you were given the free trial. If you have ever paid for a plan, a hash of your email marking that you had a paid subscription. Why: so the free trial and the first-week discount can each be used only once per person, and to limit free trials per email domain. These are kept for 2 years after you delete your account (see “How long we keep it”).
• Copyright notices. If a rights holder complains about something uploaded to Recallio, we record the deck, the notice reference, when the notice arrived, what we did and when, the file's fingerprint and whether your account was suspended as a result. Why: to act on notices on time, stop the same file coming back and apply our repeat-infringer rule (see our Copyright policy).
• Page-view counts. The start, sign-in and upload pages are counted with our own counter: the page, a random number for the browser tab (forgotten when you close it) and, if you came from a tagged link, the channel (for example Reddit or a friend). No IP address or device details are stored with it.
• Logs and error records. Our server logs record each request (the page or action, the time and the network address it came from), account and deck ID numbers, and at sign-in a shortened form of your email (its first letter and domain). When something goes wrong we keep an error record with only the type of error, where in our code it happened, the step involved, the file type and the app version: no email, account, file name or lecture content. Your IP address is also used briefly in memory to limit repeated sign-in and other attempts; it is not stored in our database. Why: security, preventing abuse and fixing faults.

We don't sell your personal information, share it for advertising, or use your lectures to train AI models.

Your lectures, decks and cards are private to your account. Other users never see them. The people running Recallio can see an admin summary (your email, credits, page and card counts, costs, deck names and your feedback). We only open your lectures or cards when you ask us to, to fix a fault, or to deal with a copyright complaint or a legal requirement.

We use these service providers, each only for its part of the service:

• Anthropic, PBC (a United States company): the Claude AI model writes your cards. It receives the text and images of the pages you choose, the file name, your card style settings and any notes you type for a deck or a regenerated card. We don't send it your email or account details. In economy mode (the default) requests go through Anthropic's batch service. Your upload is sent to Anthropic, our AI provider, to make your cards. It is not used to train AI models by default. Anthropic keeps it for a limited period, currently up to 30 days, and longer if content breaks Anthropic's usage policy. Where it is processed: the United States. Content that Anthropic's safety systems flag as breaking its usage policy can be kept for up to 2 years. See Anthropic's privacy policy.
• Stripe: only if you subscribe to a plan. It receives your email, our ID for your account, the plan you chose and the card details you enter on Stripe's checkout page. Stripe keeps its own payment records under its own privacy policy. If you delete your account we cancel your plan, but Stripe keeps its customer record. Our contract is with Stripe Payments Australia Pty Ltd. Stripe processes payment data in Australia, the United States and Ireland, and may use other locations.
• Google: only if you choose “Continue with Google”. After you tick the terms box your browser loads Google's sign-in script. We send the sign-in token Google gives you back to Google to check it, and keep only your email address and Google's ID for your account. Google processes this in Australia, the United States and other countries where it operates.
• Our email provider (Resend, United States): sends sign-in codes and links and, if we turn it on, a short message when a deck is removed after a copyright notice.
• Hosting provider (DigitalOcean, Sydney, Australia): runs our servers and stores our database, your decks and files, and our server logs in Sydney, Australia.
• Amazon Web Services (AWS S3, Sydney, Australia): stores encrypted backups of our database and of the slide images and files kept with your decks.
• Google Workspace: our email inboxes (support and our other addresses) are hosted with Google, so emails you send us are stored there.

We use no analytics, advertising or third-party error-tracking services. Our fonts are served from our own site.

Some of your data goes to providers outside Australia: Anthropic (United States), Stripe (Australia, the United States and Ireland, and other locations), Google (Australia, the United States and other countries where it operates) and our email sender Resend (United States). Those providers may use other countries too. Our hosting (DigitalOcean) and our backups (AWS) are in Sydney, Australia. We choose providers with appropriate security and privacy commitments, as required by Australian Privacy Principle 8.

• Sign-in records. An emailed link works for 15 minutes and a code for 10 minutes. The record is deleted 24 hours after both have expired.
• Staying signed in. A sign-in lasts 30 days and is extended while you keep using Recallio. Records of ended sign-ins are deleted 7 days after they end.
• Uploads you never turn into a deck are deleted after 24 hours.
• Original lecture files are deleted as soon as your cards are made, unless you tick “keep my original file”. If making a deck fails, the file is kept with the deck so you can retry, until you delete the deck. For a PowerPoint file we also make a PDF copy to draw the slide images, which stays in our cache (below) for up to 30 days.
• Decks, cards, slide images, extracted text, file names and fingerprints, edits and feedback are kept until you delete the deck or your account. A deck removed after a copyright notice is hidden straight away and can't be deleted by you; unless it is restored, we delete it 28 days after the notice.
• Cached AI results. To avoid paying twice for identical work, we keep some intermediate results (lecture summaries, extracted concepts, slide descriptions and diagram labels) keyed by a fingerprint of the exact request. They aren't linked to your account. If someone submits exactly the same material with the same settings, a cached result may be reused for their deck; they never see your cards, styles or anything about you. Each result is deleted 30 days after it was made.
• Your account, styles, credits, usage and the record of what you agreed to are kept until you delete your account.
• Error records are deleted 30 days after that error last happened.
• Page-view counts have no set end date. They are not linked to you.
• Server logs are deleted after 30 days.
• Backups. We back up our database, and the slide images and files kept with your decks, every day and keep the 30 most recent backup copies (about 30 days). An encrypted copy of each backup is also stored on AWS in Sydney, Australia, where it can be kept for up to about 30 more days. Deleted data can therefore remain in backups for up to about 60 days after you delete it.
• After you delete your account we keep:
  • the keyed hashes of your email and its domain, and whether you were given the free trial, for 2 years after you delete your account. After that, the same email can get a free trial again;
  • if you ever paid for a plan, the hash of your email marking a past paid subscription, for 2 years after you delete your account. After that, the same email can get the first-week discount again;
  • credit, cost and payment records (amounts, dates, plan, invoice and refund details) with your account removed from them, and a keyed hash of your Stripe customer ID, for 7 years from the date of each record;
  • copyright notice records, with your account removed, for about 6 years after the deck was deleted or restored;
  • blocked file fingerprints, with no end date. They contain no personal information and stop the same file being uploaded again;
  • records of actions our admins took (for example suspending an account, lifting a suspension or closing an account), which no longer link to an account, for 2 years (about 6 years for actions on copyright notices).

Stripe and Anthropic keep data under their own terms (see “Who sees it”).

• See your data: Account → Export my data downloads your account details, the record of what you agreed to, your styles, decks with their cards, credit history and feedback as a JSON file. For anything else we hold about you (for example sign-in, payment or file records), email us.
• Correct it: you can edit your cards and styles in the app. To correct anything else, email us.
• Delete it: Account → Delete my account (or the button below) permanently deletes your account, decks, cards, slide images, files, styles and feedback straight away. You can't delete your account while a deck is being made. Deleting cancels any plan straight away (see the Refunds section of the Terms). We keep only what is listed under “After you delete your account”, and deleted data can remain in backups for up to about 60 days after you delete it.
• If your account is suspended you can still export your data and delete your account.
• How to ask: email privacy@recallio.com.au. We reply within 30 days, usually much sooner.

We handle personal information under the Privacy Act 1988 (Cth) and the Australian Privacy Principles. If you're in the EU or UK (GDPR) or California (CCPA/CPRA), you also have the rights those laws give you, including access, correction, deletion, portability and objection; use the tools above or email us. We rely on performing our contract with you to provide the service, and on our legitimate interests for security and improving the service. We don't sell or “share” personal information as those laws define it.

If you're unhappy with how we handled a privacy request, tell us first. You can also complain to the Office of the Australian Information Commissioner (oaic.gov.au) or your local data protection authority.

• You must be 18 or older to use Recallio. When you sign up, you confirm that you are 18 or older.
• If we learn that an account belongs to someone under 18, we will close the account, delete their data and refund their most recent payment, if they made one.
• If you are a parent or guardian and think your child under 18 has an account, email support@recallio.com.au with the account's email address and we will deal with it as above.

We use one essential cookie, cf_session, to keep you signed in. Your browser also stores your theme (light or dark), the link channel you arrived from, whether you dismissed the cookie notice, which cards you have reviewed in each deck, and a note that stops the same “deck ready” message showing in two tabs. For the current tab only, it keeps the page-count number, a note when you change a deck's style, and during checkout a note used to confirm your payment went through. Page views are counted without cookies. We use no advertising or third-party tracking cookies. Stripe's checkout page and Google's sign-in may set their own cookies under their policies.

Sign-in tokens and codes are stored only as hashes, connections are encrypted, and access to the server is restricted. No system is perfectly secure. If a data breach is likely to cause you serious harm, we will tell you and the OAIC as the Notifiable Data Breaches scheme requires. Report security issues to the contact in security.txt.

If we change this policy we will update the date above and, for significant changes, tell you by email or in the app before they take effect. See also our Terms of Use and Copyright policy. Contact: privacy@recallio.com.au.