Black Widow - Privacy
Updated 2026-11-17 - Minimal data - Open registration - Covers GDPR Articles 6, 13, 15 to 21, 28, 44 to 49 and 77
I try to collect as little as possible. Here is what actually lives on the server, why I keep it, how long I keep it, who else touches it, and how to ask me about it.
Controller and contact
The data controller for this server is its operator, known as Spider. There is no separate data protection officer. This is a one-operator server, so the operator handles requests directly. Contact: [email protected]. If we cannot resolve your concern, you may complain to your local supervisory authority. Contact: [email protected]. There is no separate data protection officer: this is a one-operator server, so the operator handles requests directly. If we cannot resolve your concern, you have the right to complain to your local supervisory authority (GDPR Article 77).
What we store
One SQLite file on our virtual server. It holds:
- Account: username, salted password hash, login token and its expiry.
- Profile: display name, bio, avatar, including uploaded avatar files.
- Your content: characters, personas, chats and turns, votes, lorebooks.
- Who can read your chats: chats are stored as plain text and I can read them for moderation and safety. Treat chats as visible to the operator, not private messages.
- Security and operations: last IP address and user agent (set at login and signup, refreshed at most hourly on later authenticated requests), device fingerprint string sent by your client for ban evasion (stored only when your client sends one), audit log rows for logins, signups, recoveries and admin actions, strikes and moderation records, first-party stats aggregates, a client error reporter that POSTs crashes to /__diag (rate limited at 30 per minute per IP, written to a server log file with token and email redaction, rotated past 5 MB)
- Age stub: no real birthdays collected. Every account carries placeholder date of birth 2000-01-01 and an adult category label as system defaults. There is no age verification.
Passwords, corrected
Earlier versions of this page said no passwords were stored. That was wrong, and I am fixing it here. I store salted password hashes (PBKDF2), never plaintext passwords. You log in with your username plus a password of 8 or more characters. If you forget it, contact me for a temporary password.
Why I process it: lawful basis
- Provide the service you signed up for (contract, Article 6(1)(b)): accounts, content, login.
- Your consent (Article 6(1)(a)): optional profile fields, avatars and bios you choose to upload.
- Legitimate interests (Article 6(1)(f)): security, abuse prevention, ban evasion detection, first-party operational stats. I balance this by collecting as little as possible.
- Legal obligation (Article 6(1)(c)): takedown and safety records I must keep.
I do not use your data for ads, I do not sell it, and I do not build profiles for third parties.
Who else touches your data: processors
Earlier versions said the server never phones home. That is true only when inference runs locally. When external AI inference or other network services are used, the minimum needed leaves this machine:
- Proteus chats use Google Gemini at https://generativelanguage.googleapis.com/v1beta/openai/: prompts and chat text are sent for generation.
- Polyester chats use Google Gemini at https://generativelanguage.googleapis.com/v1beta/openai/.
- Text safety checks for characters, personas, chats, lorebooks, posts, and comments use Inception Labs Decide first when a key is configured (submitted content triaged at https://api.inceptionlabs.ai/v1/decisions), with the moderation lane model path as fallback. A second model pass names exact offending words. Empty or filtered provider replies are held for human review with a NEEDS-REVIEW flag, never auto cleared. Flagged deletes freeze a content snapshot plus an audit row before rows are wiped. Image checks use the moderation lane vision model. Avatar serving is local only with no upstream proxy: every avatar in the database is an uploaded file minted here, served resized with a per-size cache, and misses return 404.
- Hosting: the server runs on a rented virtual server (Contabo, EU region). The hoster has physical access to the machine, as with any VPS; no other hosting vendor touches the data.
- Chat wallpaper: the stock wallpaper set proxies characterai.io default background images on miss, then caches short term.
- Cloudflare tunnel: when the server runs behind a tunnel, Cloudflare carries TLS and sees IP addresses as network operator.
No other third parties. No ad networks, no analytics vendors.
International transfers
External processors may sit outside the EEA. Where that happens, transfers rely on the provider contracts plus sending only what is needed for the request (Articles 44 to 49). Chat and moderation text leaves this machine whenever an external key is configured; with no keys configured the provider raises instead of serving locally.
Retention
- Your content: kept until you delete it. Deleting a character, chat, lorebook, post or comment deletes its active database rows; deleting a lorebook also removes its entries and unlinks it from characters. Lorebook saves replace entries by id diff, so removed entries delete as part of the save. Archiving a persona does not delete it. It only hides it. There is no self-serve hard delete for personas today. Ask me to hard delete it.
- Accounts, hashes and tokens: login cookies carry a 30 day Max-Age and sessions extend their server expiry on active use, with a 90 day absolute cap from creation. Up to 5 sessions per user, oldest kicked. Accounts stay until an erasure request is granted.
- IPs and user agents: last IP and user agent are set at login and signup, then refreshed at most hourly on later authenticated requests. Login audit entries that contain IP addresses are kept for security and are not overwritten.
- Audit log, strikes, moderation records, and token usage records have no automatic deletion today and are kept until a schedule is set or an erasure request is granted where the law allows.
- Usage aggregates in stats_minute are kept with no automatic prune (per-minute counts are anonymous, not personal data). Per-generation token usage rows are kept with no automatic prune today.
- Strikes and moderation records: kept while needed for safety decisions.
- Legacy invites: the invite system was retired in November 2026. Old codes persist with their claims recorded for history. No new codes are minted.
There is no automatic expiry for user content yet: the retention rule is deletion when you delete it or when an erasure request is granted.
Your rights and how to ask
You hold the GDPR rights of access (15), rectification (16), erasure (17), restriction (18), portability (20), objection (21), and withdrawal of consent where consent applies. To use any of them, email [email protected] with your username, what you want, and an optional date range. Tell me in the community Discord if mail is down. I verify you own the account, then answer within one month. Export arrives as JSON of your core account data: profile (username, display name, bio, created), characters (id, name, title, description, greeting, definition, visibility, created), chat headers (chat id, character id, create time, no message text), full persona rows, and strike records (target, reason, created, appeal status). Message text inside chats, lorebooks, posts, votes, settings files, avatar files, and server logs are not included in the download. For a full access request including those categories, email with your username and date range. No passwords or active tokens are included. Erasure deletes your account row, votes, follows, chats with their turns, characters, personas, lorebooks with entries, posts with comments, strikes, token usage, notifications, settings, and sessions, and unlinks your legacy invite codes (used codes unlink, granted unused codes revoke). Avatar files on disk, mod snapshots, audit log rows, and moderation records are kept for safety and legal records. I keep only what the law forces me to keep (for example abuse records under investigation) and I will tell you what that is. There is a self-serve Export button on /account for core data. Full export beyond that and full erasure run through [email protected] until self-serve delete ships. Per-object deletes exist in the app today. Deleting a character, chat, lorebook, post or comment removes its database rows. Archiving a persona hides it but does not delete it. There is no separate backup system in the code; bundle zip uploads replace the served client only. There is no self-serve account delete button yet: full erasure runs through this inbox until it ships.
Cookies
Two first-party cookies keep you logged in: HTTP_AUTHORIZATION and char_token. Both are HttpOnly. SameSite is Lax on direct hosting, and None plus Secure when served through a tunnel. Each lasts 30 days. Logging out revokes the server session and clears both cookies in the browser. No third-party tracking cookies. Full detail on the Cookies page.
Operational stats, no third-party trackers
No analytics vendors, no ads, no third-party trackers. I run first-party operational stats only: a sampler with no automatic prune, a staff stats endpoint, and a client error reporter that POSTs crashes to /__diag at 30 per minute per IP into a redacted server log file. The bundled client telemetry endpoints (statsig, amplitude, braze style sinks) return empty locally and never leave this machine.
Age gating
SFW is 13+. Accounts are self-declared 13+: I do not collect real birthdays and there is no age verification. Every account carries a placeholder date of birth of 2000-01-01 and an adult category label by default. Those values are system defaults, not verified facts. If you believe a user is under 13, contact [email protected] and I will investigate and remove the account and personal data as required by law. If you or someone you know is in distress, see the Safety page. No NSFW anywhere, and no 18+ site is planned.
Changes
2026-11-17: hosting moved to a rented EU virtual server (processor list updated), inference providers corrected to Google Gemini only. If this page changes materially, I will update the date above and note what changed, plus announce it on the login page or in the community Discord.