who we are
oeper.dev is a personal website run by an individual who goes by "oeper.dev". Anywhere this policy says "we", it means that person. You can reach us at [email protected].
what we collect and why
| what | why |
|---|---|
| your google account name, email address and profile photo, received when you sign in with google | to create your account and show who you are to other people on the site. Your email address is also what your account is keyed by in our database. |
| profile details you add: handle, bio, badge and similar | to show on your public profile. |
| things you post: posts, comments, stories, videos, projects, notes, uploaded files, direct and group messages, follows, reactions | to run the features you asked to use. Posts, comments and profiles are public. Direct and group messages are visible to the people in that conversation and to the site owners (see "who can see it"). |
| files you attach to epic AI (PDFs and text files) | to let the AI answer questions about them. The file is read inside your browser and is not uploaded. Only the extracted text is sent to the AI service together with your message, and it is saved in your AI chat history like the rest of the conversation. |
| ai chats | so the AI assistant can show your past chats on all your devices. |
| epic AI's memory file about you (signed-in people only): a short text profile, a list of quick facts, and a switch for whether epic AI may learn about you. It holds things you told epic AI or wrote there yourself, such as the name you go by, what you study or do, your interests, how you like answers written, and your goals. epic AI is told not to store passwords, ID, card or bank numbers, exact addresses, health, religion, sexuality or political views, or private details about other people | so epic AI can remember you between chats and devices and help you better. The file is saved to your account, is not shown to other people, and is sent to the AI service (Cloudflare Workers AI) with each message you send while you are signed in. You can read, change and delete all of it, and turn learning off, in the memory panel on the website and in the app's Settings. |
| epic AI usage: how many tokens you used today and in total, which plan or codes you have redeemed and when, and for people who are not signed in, a count tied to their network address | to apply the daily limits, to apply codes, and to stop abuse. Daily counters are small numbers per person; they are not a copy of what you wrote. |
| screen text and screenshots, when you use phone control or ask epic AI to look at your screen (Android app) | to let the AI see what you see so it can help or do the task. The text and picture of the screen go to Cloudflare Workers AI with your message. Nothing is read in the background, and banking, wallet and password apps are skipped. They are kept in your chat only as a short note, not as the picture. |
| feedback and bug reports you send from the app or the feedback page: your message, the kind of report, the app and version, and, only if you leave them in, your account email, a contact address you typed, the device model and Android version, and the last crash log | to read, answer and fix what you reported. A crash report is only sent after you press Send. Reports are kept in our database (the newest few hundred), can be forwarded to a private owner channel, and can be deleted on request. A thumbs up or down on an answer is sent as a short report; the answer's text is included only if you tick that box. |
| oeper+: whether you have it and until when, whether you chose to show the + badge, and, once buying opens, purchase records | to give you what the plan includes and to show the + if you want it. Whether you have oeper+ and until when is part of your public profile record, so others who look can see it. No payment card details are collected by us. |
| pictures you ask epic AI or the One suite to make: your description, and a count of how many you made today | to make the picture and to apply the daily limit. The description is checked by a safety filter and goes to Cloudflare Workers AI (for the best-quality pictures, to Google through Cloudflare). The finished picture is sent back to you and kept on your own device; we do not store it on our servers. |
| conversations you choose to share (signed-in people only): a copy of the messages (and pictures, up to six) of the conversation or answer you share, a title, the time, how many times the link was opened, and the account that made it | to let anyone you give the link to read it, like sharing a chat from other AI apps. Nothing is shared unless you press share. The copy is public to anyone who has the link (it is not listed anywhere), it shows no name or email, and it does not change when you keep chatting unless you update it. You can stop sharing from the chat's menu, or by deleting the chat in the app, and the copy is then deleted. Do not share anything you would not want strangers to read. |
| signed-in devices: a random device id, a label such as your browser and operating system, and the last time that device was active | to show you a list of where you are signed in, in settings. |
| your IP address, seen by our servers when you connect | for rate limiting and abuse prevention. For uploads without an account, the IP address is stored along with an upload count so we can enforce the anonymous upload limit. |
| your approximate country and time zone, worked out from your connection when you chat with epic AI (not your exact location) | sent to the AI model along with your message so that answers fit where you live (prices in your currency, local services, units). It is not stored, and a message you write about where you are takes priority. |
| reports you send about content | to review and act on them. A report, with the reported content and your account, is sent to a private channel only the owners can read. |
| preferences saved in your browser | for example theme, font, sort order and read markers. These stay on your device. See the cookie policy. |
We do not run advertising, we do not use analytics or tracking scripts, and we do not sell your data.
who can see it
- the public: your handle, name, photo, bio, public posts, comments, files you made public and your public activity.
- other users: only what you send them, such as messages.
- the site owners: because we run the database and the file server, we can technically read stored content. We only look at private content when needed to handle a report, enforce the terms, fix a fault or comply with the law.
services that process data for us
We use these providers. Each receives the data needed for its job and has its own privacy policy.
| provider | used for |
|---|---|
| Google (Firebase Authentication and Cloud Firestore) | sign-in and the database that holds almost everything above. |
| Cloudflare (network and security layer in front of the site, Tunnel, and Workers AI) | delivering the site, connecting to our file server, and running the AI assistant and automated content moderation. Text and images you send to the AI assistant, and uploads that are checked by moderation, are processed by Cloudflare Workers AI. |
| GitHub (GitHub Pages) | hosting the website files. |
| jsDelivr (a public CDN) | delivers the PDF reading library. Your browser only requests it when you attach a PDF to epic AI, which means jsDelivr sees your IP address and browser details. The PDF itself never goes to jsDelivr. |
| Google Fonts | icon and text fonts. Your browser requests them from Google, which means Google sees your IP address and browser details. |
| Discord | receives user reports and feedback in a private owner channel. |
| Picovoice (Android app only) | listens for the "hey epic" wake word on your device if you turn that on. The audio is processed on the device. |
| connectors you add yourself | when you add a connector (MCP server) in the app, epic AI sends it the requests needed to use its tools. That server is run by someone else and has its own policy. |
| our own file server | stores files you upload. It is a small server run by us and reached through a Cloudflare Tunnel. Files you upload to your file storage are private by default: only you can open them (and the site owners, see "who can see it"), and a link you copy for one stops working after a while. You can make a file public, or change the default, in settings. Uploads made without signing in, and copies you share from the one suite, are public links. |
Some of these providers are located outside your country, so your data can be processed in other countries, including the United States.
how long we keep it
- Your account data and content stay until you delete them or delete your account.
- Uploads made without an account expire automatically, and larger files expire sooner.
- Deleted files move to a trash and are removed after a retention period.
- Your memory file and quick facts stay until you edit or delete them, or delete your account. Turning learning off stops new things being added but keeps what is already there until you clear it.
- Daily epic AI usage counters are small and are replaced day by day. Feedback reports are kept until we have dealt with them and, at most, for as long as the newest few hundred reports fit; ask us if you want one deleted.
- Moderation and audit records may be kept for as long as needed to protect the site and other users.
your choices and rights
Depending on where you live, you may have the right to access, correct, export or delete your data, to object to some processing, and to complain to your local data protection authority. In practice:
- You can edit your profile and delete your own posts, comments, files and messages from the site.
- You can ask us to delete your account and the data tied to it, or to send you a copy of your data, by emailing [email protected] from the email address on the account. We aim to reply within 30 days.
- You can remove a signed-in device in settings, and you can revoke this site's access from your google account at any time.
Deleting something from the site does not always remove it from copies other people made, or from backups, straight away.
children
Sign-in uses a google account, and google's own age rules apply to having one. We do not knowingly want personal information from children who do not have permission to use the site. If you are under 13, or under the age of digital consent where you live, use oeper.dev only with the permission and supervision of a parent or guardian. A parent or guardian can email [email protected] to see, correct or delete a child's data, and we will act on a verified request quickly. Do not post personal details about yourself or others in public areas.
security
Connections to the site use HTTPS, and database access is limited by access rules. No online service can promise perfect security, so please do not share passwords or sensitive personal information in messages or posts.
changes
If we change this policy in a way that matters, we will update the date above and, for large changes, post a notice on the site.