Privacy notice
Version 0.1 (draft), dated 2026-10-31.
This page is a placeholder. Each section below says what the final text will cover. This is a notice you read: information Weva gives you about your data.
What this notice is
Will say what Weva holds about you, why, and who receives it.
Personal data Weva holds (list for the lawyer, not finished text)
The build holds the following today.
- Email address, and when it was verified (members who sign in by email).
- Google account ID (Google's own identifier) and nothing else from Google (members who sign in with Google).
- GitHub id, handle and avatar address (members who sign in with GitHub).
- Profile: display name, what you do, and a photo if you add one.
- Where you live, as you told Weva: in the EU, EEA, UK or Switzerland, or somewhere else. It decides which model hosts receive your requests.
- Two-factor sign-in: the authenticator secret (encrypted), hashes of recovery codes, and a count of wrong codes.
- Circles you belong to, your role in them, who invited you, and circle charters you write.
- Skills you upload, every version, their pictures, and where they are shared.
- Access requests and proposals, with the notes you wrote.
- Reports you file about a skill: reason, note, and the name and contact recorded from your account. Only admins read reports.
- Admin views of a reported version, and takedown records, kept as audit events.
- Feedback and the interest list: an email address and a short note, if you send them.
- Skill notes: the private notes you write on a skill, and one note for all skills (up to 4,000 characters each), with when you saved and last confirmed each one and whether you typed or pasted it. A note is added only when you yourself use the skill. It is not sent to any other member, to the skill's owner or to admins, and admins have no view of its text. In Weva's chat the note goes with your question to the AI provider that answers it (OpenRouter and a model host, as below); in an AI assistant you connect to Weva, that assistant receives it with the skill. Proposed, not yet decided: a note not confirmed for 180 days is paused, and removed 180 days after that.
- Learning pair: the learning pair you choose in Settings (French - English or French - German), and when you last changed it. It sets the second language shown next to French words in vocabulary skills. Until you choose, French - English applies and nothing is stored. It is not sent to any other member, to the skill's owner or to admins, and admins have no view of it; it is in your own account export. When you play a vocabulary game in an AI assistant you connect to Weva, the game's answer to that assistant names the pair.
- Invite addresses: the address an invite was sent to, cleared when the invite is accepted or revoked, or 30 days after it expires.
- Sign-in links: kept until a day after they expire.
- API tokens and connected apps: names and dates only; Weva keeps a hash of a token, never its value.
- Audit events that name you, and your gateway spend per period. The audit log keeps no network address.
- Which version of each legal document you accepted or read, and when.
Who receives it (processors)
Amazon Web Services hosts Weva in Singapore and holds its backups; Amazon SES sends the mail.
GitHub and Google receive a sign-in request when you use them. OpenRouter receives the text of the requests you send through Weva's gateway, not your account details, and passes it to a model host. Which hosts depends on where you told Weva you live:
If you live in the EU, the EEA, the UK or Switzerland: Weva sends your requests only to the model hosts on its allowlist, and asks OpenRouter on every request to use only hosts that keep no copy of the text and do not train on it.
If you have not told Weva where you live: Weva sends none of your text to a model. Tell Weva in Settings.
If you live somewhere else: Weva sends your requests to its standard model providers, the models its model list picks by test score and price. They may log or keep requests under their own terms. The models the list picks for each price tier today:
- inclusionAI: Ling 3.0 Flash (inclusionai/ling-3.0-flash)
- MiniMax: MiniMax M3 (minimax/minimax-m3)
- Xiaomi: MiMo-V2.6-Pro-UltraSpeed (xiaomi/mimo-v2.6-pro-ultraspeed)
How long it is kept, and backups
Will say how long each item is kept. Backups of the registry expire about 37 days after they were taken, so a deleted account can remain in a backup for about that long.
Seeing, exporting and deleting your data
Will explain how to download your data (Settings, once an hour) and how to delete your account (Settings, Delete my account), and how to write to Weva with any other request.
Cookies and similar storage (list for the lawyer, not finished text)
Weva sets functional cookies only, no analytics and no advertising. Cookies, each set for a sign-in step or to keep you signed in:
- __Host-weva_session: keeps you signed in. Up to 30 days.
- __Host-weva_oauth_state: protects the GitHub sign-in round trip. 10 minutes.
- __Host-weva_google_flow: protects the Google sign-in round trip. 10 minutes.
- __Host-weva_signin_nonce: ties an emailed sign-in link to the browser that asked for it. 10 minutes.
- __Host-weva_pending_invite: remembers your invite across a sign-in. 10 minutes.
- __Host-weva_pending_legal: remembers the box you ticked on the sign-in page across a sign-in. 10 minutes.
- __Host-weva_pending_authorize: remembers an app connection you started while signed out. 10 minutes.
- weva_2fa_pending: remembers that your second sign-in step is waiting. 5 minutes.
- weva_email_pending: remembers an email address being added to an admin account until two-factor is set up. 15 minutes.
- weva_profile_skip: remembers that you skipped profile setup. One year.
- Browser storage, not cookies: your colour theme and display settings, and the browser token the portal keeps in your browser. 7 days, and it ends when you sign out.
Your rights and how to complain
Will cover your rights under the laws that apply, and where to complain. Left for legal review.