Skip to content
MySummaries Log in Start free
Platform Pricing Docs Articles Contact Log in Start free

Privacy

Privacy Policy.

Effective 15 November 2026 · Last updated 18 November 2026 · Version 2026-11-15

1. Scope

This Privacy Policy explains how MySummaries Pty Ltd (ABN 75 545 287 502), a company registered in Victoria, Australia ("MySummaries", "we", "us"), collects, uses, discloses and protects personal information when you use mysummaries.app, portal.mysummaries.app, the MySummaries mobile apps and the services reachable through them (the "Service"). It is written to meet the Australian Privacy Act 1988 and the Australian Privacy Principles, the EU General Data Protection Regulation and UK GDPR, and the California Consumer Privacy Act as amended by the CPRA. Where those laws give you particular rights, the sections below say so. It forms part of our Terms of Service.

For the personal information described here, MySummaries Pty Ltd is the controller (or, in California terms, the business). Our contact details are in section 13. We have not appointed a representative in the European Union or the United Kingdom; contact us directly at the address in section 13.

2. What we collect

  • Account information. Email address, the name you give us, your sign-in provider identifier (for Google sign-in), a hashed password (for email sign-in, held by our authentication provider — we never see it), and the study profile you set up: what you are studying, which examiner persona you chose, exam dates, the name you want the examiner to use, and the language you choose for the app and for what the AI writes. Your account also keeps your pomodoro timings, so that the timer starts from the same ones wherever you sign in, and which of the app's tips you have already been shown, so that a tip shown on one device is not offered again on another. When you sign up on the web we also record which language the site was in at that moment, and use it only to count sign-ups by language, so that we know which languages to support. It is kept with your account and deleted with it.
  • Your Content. Everything you put into the Service: notes, scratchpad text, uploaded documents (PDF and Word files are converted in your browser to text and page images, and those are what we store), images, flashcards, typed exam answers, your questions to the assistant, audio recordings of spoken answers and the transcripts made from them, and the outputs the Service generates from all of that — cards, papers, marks, lectures, the assistant's answers (including the short summary it keeps of a long conversation), examiner transcripts and feedback.
  • Your study record. Each time you answer something in the Service — a question in an Ask AI chat, a flashcard, an exam question, a point in an oral examination — we keep a short record of it: which item and board it was, the marks it earned, which points of the marking guide it missed, how sure you said you were if you said, how long you took, and which model marked it. The record never holds your answer itself, which stays with the chat, paper or attempt it belongs to. It is what lets the Service show you what you have learned and what is slipping, and lets us check that its questions and marking work. Every night a copy of each record also goes into an analysis table in Google BigQuery, in the same Google Cloud project as the rest of the Service. The copy has no name, email address or account identifier: your account is replaced by a code computed from it with a secret key that never leaves our servers, the ids that would lead to your boards, subjects and chats are replaced the same way, and the ids of your papers, attempts and cards are left out. It holds nothing you wrote. We use it to find questions that work for nobody and to compare ways the Service teaches (which order of explaining and asking helps people remember), always across groups, never about one person. We also keep statistics for each question across everyone who answered it in the last 90 days (how often, how well, how quickly), only once at least five accounts have answered it, and with no account identifier in them.
  • Acceptance records. When you accept the Terms and this Policy we record the versions accepted, the time, your IP address and browser user-agent string, so we can show what you agreed to.
  • Usage and billing. Which features you use, when, with which model, and what each call cost (to meter your plan); your plan, subscription and credit balance; and the customer and subscription identifiers our payment provider assigns you. We never receive or store your full card number.
  • Technical and security information. IP address, device and browser type, app version, request logs, error reports, and the signals our bot-protection service (reCAPTCHA Enterprise / App Check) returns. If you file a bug report from inside the Service, it includes the description you write and a short trail of the screens and calls that preceded it.
  • Messages. Anything you send us through the contact form or by email.
  • Referral information. If you arrive through an affiliate link, a cookie holding that affiliate's code is set for 60 days so that a signup or purchase can be attributed to them. The affiliate sees a masked form of your email address, never the full address or any of Your Content.
  • Analytics. We use Google Analytics 4 on the marketing site, the web app and the affiliate portal. It records the pages you view, an approximate location worked out from your IP address (Google derives the location and does not store the address itself), your device and browser type, and the actions you take in the Service as event names and counts. It never receives the content of your notes, cards, exam answers or recordings, and never your name or email address. In the EEA, the UK and Brazil it runs with analytics storage denied by default: no analytics cookie is set, and Google receives cookieless pings instead. Everywhere else it sets the two cookies described in section 11.
  • Advertising measurement (Meta Pixel). We advertise on Facebook and Instagram, and run Meta's pixel on mysummaries.app and portal.mysummaries.app to measure whether those ads lead to visits and sign-ups, and to show our ads to people who have visited. It sends Meta the pages you view and one "registration completed" event when you create an account, together with what any web request carries: your IP address, your browser type and the address of the page. It sends no name, email address or account id, and nothing you type into the Service; Meta's automatic advanced matching, which would look for those on the page, is turned off. It does not run at all if your device's time zone is set to one in the EEA, the UK or Brazil, and it is not in the iPhone or Android app. The check is your device's time zone, not where you are. Meta sets the cookie described in section 11, and if you are logged in to Facebook or Instagram in the same browser it may also use its own cookies to link the visit to that account.

We do not collect information from data brokers. The Meta Pixel above is the only advertising tracker in the Service, and the mobile apps carry none.

3. Sensitive information, and information about other people

We do not ask for sensitive information (health, racial or ethnic origin, political or religious views, sexual orientation, genetic or biometric data, criminal history). Your own study notes may nonetheless contain some — a medical student's notes about their own condition, for example. If you choose to enter sensitive information about yourself, we process it only to provide the Service to you, on the basis of your explicit choice to include it, and you can remove it at any time by editing or deleting the content.

The Terms prohibit uploading personal information about anyone else that you are not authorised to disclose, and in particular any information about a patient, client or other identifiable individual. We do not want it, do not knowingly process it, and have no agreement with you to act as your processor or service provider for it. If you upload it anyway, you are the party responsible for it under privacy law. If we become aware of it we may delete it and suspend the account, and we will cooperate with any affected person or regulator. If you believe information about you has been uploaded by someone else, contact us and we will investigate.

4. Why we use it, and our legal bases

Under the GDPR and UK GDPR we need a legal basis for each use. They are:

  • To provide the Service you asked for (performance of our contract with you) — storing and displaying Your Content, sending it to our AI providers to generate cards, papers, marks, lectures and oral examinations, transcribing your recordings, syncing between the web and mobile apps, sharing with people you choose, metering your plan, and billing. AI processing is inseparable from the Service, which is why it is a term of the contract rather than a separate consent you can withdraw while keeping the Service.
  • To run the Service safely and improve it (our legitimate interests, balanced against yours) — security, fraud and abuse prevention, debugging, capacity planning, aggregate usage statistics, reviewing model performance, and paying affiliates for signups they referred (the 60-day first-party referral cookie records only the affiliate's code and is used for nothing else). Where we look at Your Content for these purposes it is to investigate a specific problem or report, not routinely.
  • To measure and show our own advertising (our legitimate interests) — the Meta Pixel described in section 2, on the marketing site and the web app only. It never receives Your Content. You can object to it at any time with the controls in section 11.
  • To meet legal obligations — tax and accounting records, responding to lawful requests, and data-breach notification.
  • With your consent — optional study reminders or product updates by email. You can withdraw consent at any time; every optional email carries an unsubscribe link that takes effect immediately.

We do not use Your Content to train AI models, do not sell personal information, and do not make decisions about you that have legal or similarly significant effects by automated means. AI marking is feedback for your own use; it is not reported to any examining body.

5. Who we share it with

We share personal information only with the service providers that run the Service on our behalf, each bound by contract to use it only for that purpose:

  • Google Cloud / Firebase (United States) — authentication, database, file storage, hosting, serverless compute and bot protection. All of Your Content is stored here.
  • Google Analytics (Google LLC, United States) — the analytics described in section 2, processed on our behalf under the Google Ads Data Processing Terms and Google's privacy policy. We do not use it for advertising.
  • OpenAI, Anthropic, Groq and xAI (United States) — the AI models. The parts of Your Content needed for a request are sent to the one that answers it and the output comes back; we attach no name, email address or account id. As a safety check, OpenAI's moderation service also receives the start of the text in a request, and the words of a picture search, whichever provider answers. To choose a picture Ask AI offers in a chat, OpenAI also receives up to six of the previews the picture search found, downloaded by our servers. Groq turns recorded speech into text and runs the fast text tools — explaining a highlight, the section toolbar's complete, lengthen, shorten and format, translating a selection, and suggesting additions to a subject's index. It receives the audio being transcribed (sometimes by fetching it from our storage through a link that expires after 15 minutes) and, for a recording dropped onto a board, that board's title and headings to help spelling; the passage or section text a single request needs; or, for index suggestions, the subject's name, its index and board titles, what you said you are studying it for and any guidance you typed. xAI turns text into speech: it receives the script of a lecture being narrated, or the feedback on a recorded oral answer, both written by our models from your notes and answers, and sends back the audio. OpenAI also builds the search index over your notes, so it receives their text for that. Under their API terms none of the four may use your data to train their models. OpenAI: up to 30 days — it may keep API inputs and outputs that long for abuse monitoring, and it stores a long generation that runs in the background so that we can collect the result. xAI: up to 30 days — it may keep API inputs and outputs that long for abuse monitoring. Anthropic and Groq may each keep API inputs and outputs for a limited period under its API terms. Which provider serves a feature is an operational setting and may change.
  • SerpApi (SerpApi, LLC, United States) — the picture search on a board, and for a picture Ask AI offers in a chat. It receives the words you search for (in a chat, a short description of the picture our AI model wrote from the chat) and the board's language, sent from our servers with no name, email address or account id attached, and runs the search on Google. SerpApi keeps each search for 31 days, then deletes it. The previews in the results load straight from Google's image servers, so Google receives your IP address and browser details for them, under its own privacy policy; in a chat our servers download the previews instead, so Google sees our servers rather than you. A picture you choose is downloaded by our servers, so the site hosting it sees our servers rather than you, and it is stored with Your Content like any other picture, along with the address of the page it came from.
  • Stripe (United States and local entities) — payments and billing.
  • Amazon Web Services (United States) — sending transactional email.
  • Apple and Google — distribution of the mobile apps and their crash and install statistics, under their own policies.

One company receives information for its own purposes as well as ours: Meta (Meta Platforms, Inc., United States), through the Meta Pixel described in section 2. It receives the page views and the "registration completed" event described there, never Your Content, and processes them under its own terms and its privacy policy, including to show our ads and to improve its own advertising products.

We may also disclose personal information where the law requires it, to protect the rights, safety or property of any person, to enforce the Terms, or to a successor if the Service is acquired or merged (we would tell you first). We do not sell personal information. Under California law, the Meta Pixel counts as sharing it for cross-context behavioural advertising; section 10 says what that covers and section 11 how to stop it.

6. International transfers

MySummaries is operated from Australia, and the providers above store and process data in the United States. If you are in the EEA, the United Kingdom or Switzerland, your personal information is therefore transferred outside your region. We rely on the EU–US Data Privacy Framework, its UK Extension and the Swiss–US Data Privacy Framework where the recipient is certified under them, and otherwise on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum), incorporated into our agreements with those providers. You can ask us for a copy of the relevant safeguards.

7. Security

Data is encrypted in transit and at rest. Access to each account's content is restricted by per-user security rules at the database and storage layer; staff access to production data is limited to what is needed to operate the Service and investigate problems. Our AI providers receive only what a request needs, and the API keys for them never leave our servers. No system is perfectly secure, so we also ask you to use a strong, unique password — we check new passwords against known breach lists — and to tell us at once if you think your account has been compromised. If a data breach is likely to result in serious harm to you we will notify you and the relevant authority as the law requires (within 72 hours to a European supervisory authority where the GDPR applies).

8. How long we keep it

  • Your Content stays until you delete it or delete your account, with the exceptions below, which a nightly job enforces.
  • Recordings. The audio of a recorded spoken answer, and the spoken feedback on it, is deleted 90 days after the attempt. The transcript, the marks and the written feedback stay.
  • Boards and subjects. A board you archive is removed 90 days later, and so is a subject you schedule for deletion. Restore points — the earlier versions of a board kept so that you can go back — are deleted after 30 days. Scratchpad items that have already been merged into a board are deleted 30 days after they were captured. An invitation to share a subject with an address that never signs up is deleted after 90 days. A conversation with the assistant is deleted 90 days after its last message, and with the board or subject it was about; a picture you put into it goes with it, unless you added that picture to a board.
  • Your study record is kept for as long as your account is, including after the board an answer came from is deleted, and is deleted with your account. Its pseudonymous copy in the analysis table (section 2) is deleted with your account too: when the account is deleted we compute its code again from the account and delete every row carrying it — within a day, where a record was copied in the hours just before. The per-question statistics stay: they are totals over at least five accounts, recalculated every night, and are nobody's.
  • Notifications, job records and exports. In-app notifications and background generation job records are deleted after 30 days; data-export files after seven days.
  • Unconfirmed sign-ups. An account whose email address is never confirmed is deleted seven days after sign-up, so that a mistyped address is not held — unless it already holds a plan or an affiliate application.
  • Account deletion runs after a seven-day recovery window, then removes Your Content, your stored files, your profile, subscription projections and your authentication account. It also cancels any subscription and deletes your customer record and saved card at Stripe, which keeps the invoices as a financial record. The database is backed up nightly and each backup is kept for 30 days, so a copy of what was deleted rolls off within a further 30 days. One thing is kept: a one-way, salted hash of the email address you signed up with, together with the count of free-plan items that address has used. It identifies nobody, cannot be turned back into an address, and is not included in a data export — it exists only so that deleting an account and signing up again does not hand out a second free allowance.
  • Billing, usage and acceptance records are kept for as long as tax, accounting and consumer law require — generally up to seven years — and then deleted or anonymised.
  • Emails and contact messages — the queue of emails we send on your behalf or about your account, and messages you send us through the contact form, are deleted 30 days after they are written.
  • Security logs are kept for up to 12 months unless needed for an ongoing investigation.

9. Your rights and controls

Wherever you live, the Account page lets you export a structured copy of your data, edit your profile, manage your subscription and schedule deletion of your account, and every board lets you edit or delete its content directly.

Depending on where you live you also have rights under law to:

  • access the personal information we hold about you and be told how we use it;
  • have inaccurate information corrected;
  • have your information deleted;
  • receive it in a portable, machine-readable form;
  • object to, or ask us to restrict, particular processing;
  • withdraw consent where consent is the basis (this does not affect processing already done);
  • not be discriminated against for exercising any of these rights; and
  • complain to a supervisory authority.

To exercise a right that the Account page does not cover, email [email protected] from the address on your account, or use the contact form while signed in, so that we can verify the request. We respond within one month (45 days for California requests), or tell you if we need longer and why. We will not charge for a request unless it is manifestly unfounded or excessive. If you are unhappy with our response you can complain to the Office of the Australian Information Commissioner (oaic.gov.au), the UK Information Commissioner's Office (ico.org.uk), your local EU data protection authority, or the California Attorney General.

10. California residents

This section supplements the rest of the Policy for California residents under the CCPA/CPRA. In the preceding 12 months we have collected the following categories of personal information, from you directly and from your device, for the purposes in section 4, and disclosed them for a business purpose to the service providers in section 5: identifiers (name, email, account and customer IDs, IP address); customer records and commercial information (plan, purchases, credits); internet and electronic activity (feature use, logs, bug-report trails); audio information (recordings you make); the content you upload and the outputs generated from it; inferences limited to study scheduling (which cards are due); and sensitive personal information limited to account credentials and any health or other sensitive information you choose to include about yourself in your notes. We use sensitive personal information only to provide the Service you requested and for security, which are permitted purposes, so no "Limit the Use of My Sensitive Personal Information" control is required. We do not sell personal information. We share two categories with Meta for cross-context behavioural advertising, through the Meta Pixel on the marketing site and the web app (section 2): identifiers (IP address and the browser identifier in the "_fbp" cookie) and internet activity (the pages you view, and that you created an account). You can opt out of that sharing with the controls in section 11, or by asking us at the address in section 13. We have no actual knowledge of selling or sharing the personal information of anyone under 16. You have the rights to know, access, correct, delete and port your information and not to be discriminated against, exercisable as described in section 9, including through an authorised agent with written permission from you. Retention periods are in section 8.

11. Cookies and local storage

The Service uses only what it needs to work: a sign-in token kept by our authentication provider, your display preferences (theme, fonts, pomodoro timings, country filter) stored in your browser, a language cookie, bot-protection tokens, and — on the marketing site only, if you arrived through an affiliate link — the 60-day referral cookie described in section 2. The pomodoro timings are also saved on your account, as section 2 describes. The language cookie, "ms_lang", holds only the language you chose, so that the marketing site and the web app both open in it. It is set only when you pick a language, or when the web app applies the language saved on your account, and lasts a year. Google Analytics adds two analytics cookies, "_ga" and "_ga_" followed by our measurement id; they hold a randomly generated identifier for your browser and last up to two years — except in the EEA, the UK and Brazil, where analytics storage is denied by default and neither is set. The Meta Pixel (section 2) adds one advertising cookie, "_fbp", set on our own domain by Meta's script: it holds a randomly generated identifier for your browser and lasts 90 days from your last visit. It is never set where the pixel does not run (a device time zone in the EEA, the UK or Brazil, and the mobile apps). If you are logged in to Facebook or Instagram in the same browser, Meta may also read its own cookies, set by Meta under its own policy. You can clear all of these from your browser settings, and refuse the analytics ones there or with Google's opt-out browser add-on, which turns off Google Analytics on every site you visit. Clearing the sign-in token signs you out.

To stop the Meta Pixel, turn on Global Privacy Control in your browser (the pixel does not load when it is on), or block "connect.facebook.net" in your browser's settings or with a content or ad blocker, and the pixel never loads. You can also change how Meta uses this activity in your Facebook and Instagram ad preferences, or object to it by emailing [email protected].

12. Children

The Service is not directed at children under 16 and we do not knowingly collect personal information from them. If you are under 18 a parent or guardian must agree to the Terms for you. If you believe a child under 16 has created an account, contact us and we will delete it.

13. Changes and contact

When this Policy changes we publish it with a new "Last updated" date. For changes that matter we also give it a new version, ask you to accept it in the Service before you continue, and tell you by email where we can. Questions, requests and complaints about privacy go to [email protected] or the contact form. Please include enough detail for us to identify your account and understand the request.

14. Discord

The MySummaries Discord app answers slash commands in a Discord server. Nobody signs in to use it. It has no bot user in the server and no permissions, so it cannot read messages, and it sends every reply with mentions turned off.

  • What we keep. The server's id; a hashed form of the id of the person who used a command (a keyed HMAC, so the id itself is never stored), which we use only to apply the per-person limits and delete after 30 days; and the command, the topic and the board it made, kept as long as the board is. For a /osce station, the answers typed into it are kept for the station's hour, then deleted.
  • What we never collect. Message content, usernames, and member lists.
  • Who receives it. The topic and any station answers go to the moderation check and to the AI providers named in section 5, to make the board. The reply is posted in Discord, which handles it under its own privacy policy.
  • Boards are public by link. A board made in Discord can be opened by anyone who has its link, without an account, and copied into an account. Do not put personal information in a topic or an answer.
  • If you then sign up. A board's link carries the server's id, so an account created from it records that it came from Discord and from which server.

We use this to answer the command and to apply the limits, on the basis of our legitimate interest in providing the app and preventing its abuse. A server's moderators can restrict or remove the app in Server Settings → Integrations.

MySummaries Learn, practise, retain
Product
Web portal Pricing Mobile app Affiliates
Resources
Docs FAQ Articles Compare Example boards Revision planner About Contact
Legal
Terms Privacy Trust Accessibility Academic integrity

© 2026 MySummaries. A study companion, not a substitute for professional judgement.