Privacy Policy

Last updated: October 1, 2026

1. Who we are

Oafer ("we," "us") operates the Oafer study companion application at oafer.ai and app.oafer.ai.

2. Information we collect

Account information: your email address, display name, and (if you sign in with Google) the profile information Google provides during authentication.

Content you provide: messages you send to Oafer, textbooks and course materials you upload, and any other content you enter into the app.

Usage information: which subjects and expeditions (study sessions) you create, how often you use Oafer, and general activity patterns used to power features like your streak and progression stats.

Memory: Oafer maintains a long-term memory of things you've shared, in order to provide continuity across study sessions. This memory is private to your account.

Notes you write: Oafer can generate a set of notes, and you can edit them yourself. We store the document, and three things alongside it. The first is a short undo history — the last three versions of the document, so you can put back a paragraph you deleted. The second is a record of which parts you typed and when: the notes view marks text you have just written so it stands out and fades that mark over about ten minutes, which means storing a timestamp for each stretch of text you typed. The third is what Oafer said about the notes, below. All of it is stored with the notes and goes when they go.

Oafer reading along: while you write, Oafer reads what changed after each pause and sometimes leaves a short remark in the margin. To do that, the notes you have open are sent to our AI provider each time you pause — the whole document, the lines that just changed, passages from your textbook, and the concepts you have missed on past quizzes. The remarks are kept with the notes, up to sixty per document, so they are still there when you reopen it. You can switch this off for a set of notes with the solo mode button in the notes view; while it is off, nothing is sent and no remarks are made.

Telling us whether a remark was useful: each remark carries three controls — a tick for "worth saying", a cross for "this shouldn't have been said," and a question mark for more detail. Pressing one saves a record we use to make Oafer better, and it is worth being plain about what that record holds: the remark, which control you pressed, and a copy of your notes as they stood at the moment the remark was made, along with the lines that had just changed. This is the one place we keep your own writing for a purpose other than showing it back to you. If you would rather not contribute that, don't press the controls — nothing else about your notes or the remarks changes. These records are deleted when you delete the notes, and when you delete your account.

Graphs you edit: when Oafer draws a graph, you can open its expression panel and change the equations or add your own. We store what you have built as a single block of the calculator's own saved data, kept on that graph. What Oafer originally drew is never overwritten, which is why Reset always works: pressing it deletes what you saved and puts Oafer's graph back.

Visitor analytics: when you visit oafer.ai or use app.oafer.ai, we count the visit ourselves. We don't use Google Analytics or any other outside analytics service. Each page view is saved as a short record containing: a random visitor ID your browser makes up for itself, the page you viewed (with any ID numbers in the address swapped for a placeholder, and nothing after a "?"), the website you came from (just the site, such as "https://www.google.com," not the full link), whether you were on the website or the app, and the time. If you click one of our "Try Oafer" buttons, we record that click the same way. We do not save your IP address, your browser or device details, or your name or email in these records, and we do not connect them to your account, even if you're signed in. (Like any website, our servers see your IP address when you load a page, and we use it briefly to limit abuse, but it is not kept with the record.) We use these records only to understand how many people visit and whether the site is working.

Browser storage: we don't use cookies. Instead, Oafer keeps a few small items in your browser's local storage. One is the visitor ID above, which lets us tell a returning visitor from a new one; it is the only item used for analytics. The rest exist so the app works: a sign-in token that keeps you logged in, your display name, your light or dark theme choice, a notes-view preference, and a timer for break reminders. You can clear all of this any time in your browser settings. If you do, you'll be signed out and will look like a new visitor next time. If your browser blocks local storage, the site still works; your visits just won't be matched up with each other.

3. How we use your information

To operate and improve Oafer's core features; to personalize responses using your uploaded materials and memory, scoped strictly to your own account; to maintain account security and prevent abuse; to communicate with you about your account or the service.

We use the feedback you give Oafer's margin remarks — including the copy of your notes stored with it, described in section 2 — to improve the quality of those remarks, which may include training a model on them. That is the only purpose for which we keep anything you have written beyond showing it back to you, and it only ever applies to a remark you pressed a control on.

We do not sell your personal information. We do not use your data for advertising or ad targeting. We do not share your uploaded materials or conversations with other users.

4. Third-party service providers

We use AI inference providers to process your messages and generate responses. Your messages and relevant context are sent to these providers to generate a reply. We also use Google for authentication if you choose to sign in with Google, and cloud hosting infrastructure to run the application and store data securely. These providers process data on our behalf and are not permitted to use your data for their own independent purposes beyond providing the service to us.

Desmos: graphs are drawn by the Desmos calculator, which runs inside your browser. The first time a graph appears, your browser downloads that calculator from desmos.com. That request tells Desmos what any request for a file tells a website: your IP address, your browser and device, and that the request came from Oafer. After it has loaded, the calculator runs entirely on your own device — we tested this, and it makes no further requests — so the equations you type into a graph are not sent to Desmos. What you save is sent to us and stored with your graph, not with them.

5. Google Calendar and signing in with Google

Two parts of Oafer talk to Google, and only if you ask them to. Nothing in this section happens unless you sign in with Google or connect your calendar yourself, and nothing in Oafer stops working if you never do.

Signing in with Google. If you choose to sign in with Google, Google tells us your email address and an ID number that identifies your Google account to us. We store both, so we can recognize you the next time you sign in. That is all we receive — no contacts, no files, no calendar.

Putting your study plan in your calendar. In Settings you can connect Google Calendar. When you do, Oafer asks Google for exactly one permission, the one Google names calendar.app.created and describes as "make secondary Google calendars, and see, create, change, and delete events on them." It lets Oafer make one calendar of its own in your account, called "Oafer Study Plan," and manage the events inside that one calendar. It gives Oafer no access whatsoever to the calendars you already keep. That is not a promise about how we behave; it is the limit of what Google will let us do. Oafer cannot see, read, download or change anything in your own calendars, and cannot even see a list of them. We ask for nothing else, and there is no narrower permission that would still let Oafer write your study plan down for you.

What Oafer writes there. Only what you can already see on Oafer's own calendar page: the title of a study session or a test date, the description if you wrote one, the date and time, and whether it repeats. Each event also carries one line Oafer adds itself, "Added by Oafer." Nothing else goes to Google — not your conversations, not your quizzes, not your uploaded textbooks, not your notes, and not what Oafer remembers about you. Oafer stays the original and the Google calendar is a copy of it, which is why changing a study session in Oafer updates the event, and changing the event in Google changes nothing in Oafer.

What we receive and store. Oafer never asks Google for calendar information, so none of your events, invitations or availability exist anywhere in Oafer. What we do store, for as long as the connection lasts, is:

Two keys from Google that let Oafer write to that calendar: a long-lived one, and a short-lived one that expires after about an hour. Both are encrypted before they are written to our database, with an encryption key kept outside it, so a copy of the database on its own yields nothing that works. Neither key is ever sent to your browser, written to our logs, or put in an error message.
The ID of the calendar Oafer created, so that it gets created once rather than over and over.
One small row per study session or test date, recording which Oafer item it is, which Google event stands for it, whether the last attempt to send it worked, and a short reason if it didn't — with anything that looks like a key stripped out before it is saved.
The permission Google granted, and the times you connected, we last synced, and access ended.

Connecting your calendar does not tell us your Google email address — the permission we ask for doesn't include it, so Settings simply says "Connected." None of this is kept on a timer: the keys last as long as the connection does, and the row about a study session lasts as long as the study session does.

What we don't do with it. Oafer's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms: we do not sell any of it, we do not use it for advertising or ad targeting, we do not use it to train or improve any AI model, and we do not share it with anyone beyond the cloud hosting provider that stores our database for us (section 4). The keys and IDs above never leave our own servers — they are not sent to our AI providers, and no one at Oafer reads them. Your study sessions and test dates are Oafer's own rather than Google's, and they are used the way the rest of your Oafer content is: Oafer may include the next few of them in what it sends an AI provider, so it can greet you with what's coming up. Connecting Google Calendar doesn't change that, and disconnecting doesn't stop it.

How to disconnect. In Oafer, open Settings → Google Calendar and press Disconnect. Three things then happen, in this order: we tell Google to withdraw Oafer's access, we delete the "Oafer Study Plan" calendar from your Google account, and we delete everything in the list above from our database — both keys, the calendar ID, and every row. Deleted, not marked as deleted. Your reminders and test dates stay in Oafer.

You can also remove Oafer's access from your Google account yourself, at myaccount.google.com/connections. Oafer finds out the next time it tries to send something, deletes both keys at that moment, and offers you a Reconnect button; we keep the fact that you were connected, and when it ended, until you reconnect or press Disconnect. Removing access this way leaves the "Oafer Study Plan" calendar sitting in your Google Calendar, for you to keep or delete as you like — Oafer no longer has permission to touch it.

If you ask us to delete your account, all of the above goes with it. We disconnect you from Google as part of that, so the access is withdrawn and the calendar removed rather than left behind.

6. Data retention and deletion

We retain your account data for as long as your account is active. Nothing described above is deleted on a timer, and nothing outlives the thing it belongs to.

What deleting each thing actually removes:

A set of notes (from the menu beside Print, in the notes view): the document, its undo history, Oafer's remarks about it, and the feedback records described in section 2.
A territory: everything in it — its chats, notes, graphs, quizzes, uploaded textbooks and the memory Oafer built from them.
A chat: the conversation itself. Notes, graphs and quizzes made during that chat are kept, because they are work you made rather than part of the conversation. You can delete a set of notes on its own as above; a graph or a quiz can currently only be removed by deleting the territory it belongs to, or your account.
Your account: all of it, including the feedback records in section 2 and the memory Oafer built.

You may request deletion of your account and associated data at any time by contacting [email protected].

7. Children's privacy

Oafer is intended for users 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has created an account, contact us at [email protected] and we will take appropriate action.

8. Data security

We take reasonable measures to protect your information, including access controls that ensure your uploaded materials, conversations, and memory are private to your account and not accessible by other users.

9. Your rights

Depending on your location, you may have rights to access, correct, or delete your personal information. To exercise these rights, contact [email protected].

10. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be noted with an updated "Last updated" date.

11. Contact

Questions about this Privacy Policy: [email protected]