Wilds.ai Privacy Policy
Effective Date: November 19, 2026
Previous version: November 18, 2026
What We Collect
- Account information: Email address, display name, hashed password for email/password accounts, linked OAuth identities, and account settings.
- WildWeave film studio data: your studio preferences (the editing view, snapping and saved layouts), saved templates, studio asset records for the files a film uses, your storage total, your studio credit meter, the policy version recorded on a subscription, and the binding of your copy of the demo reel. Each is deleted with your account.
- Billing information: your subscription status, purchase history, and the customer and transaction identifiers our card processor assigns. Card numbers are entered on the processor's payment page and are never stored by Wilds. Card payments are paused while we move to a new processor; the processor will be named at /legal/subprocessors before the first charge. We keep the customer identifiers and purchase history from our previous processor, Stripe, Inc. (used until June 10, 2026), for accounting and tax records.
- Content you create: Stories, worlds, character configurations, session messages, character conversations, lore, assets, and other creative content you submit to the service, including information about other people inside a work you create, such as an interview’s words, a quote or a label.
- Operational and analytics data: Session starts and ends, heartbeat playtime, favorites, shares, search and browse behavior, multiplayer joins, compiler runs, model/provider usage, token counts, latency, IP address, and other product-usage telemetry.
- Guest play: If you play without an account, your browser gets a random guest ID in the
wilds_guest_idcookie, and we keep a guest record under that ID: the games, characters and worlds you make as a guest, the WildWeave documents you write as a guest, with their settings, your guest credits, and a hash of the IP address the guest record was registered from, which we use to limit how many free guest credit grants one network receives. - Interaction records: Some first-party interaction events may include player prompt text or AI response text when needed to operate, evaluate, debug, or improve Wilds features.
- Messages you send us: The "Write to us" form on the Contact page takes your name, your email address, the topic you pick and your message, and sends them to the wilds.ai team by email, with your address as the one we reply to. If you are signed in, it takes the topic and your message and opens a support request on your account instead, with the staff notification described under "How We Handle Your Content".
How We Use Data
We use data to:
- operate the product and generate AI responses
- save your worlds, sessions, characters, and account state
- measure usage, reliability, retention, creator reward attribution, and creator analytics
- detect abuse, investigate bugs, respond to support issues, and secure the platform
- generate anonymized or aggregated benchmarks, statistics, and business reporting
Legal Bases for Processing
For users in the EU, UK, and Switzerland, each kind of processing has a legal basis under GDPR Article 6, and, for sensitive data, Article 9:
| Purpose | Legal basis |
|---|---|
| Providing the service: accounts, sessions, saved worlds, characters, and generating AI responses | Contract (Art. 6(1)(b)) |
| Hosting information about other people inside a work you create | Legitimate interests (Art. 6(1)(f)) |
| Authentication, fraud and abuse prevention, and platform security | Legitimate interests (Art. 6(1)(f)) |
| Account-linked first-party product analytics | Legitimate interests (Art. 6(1)(f)), with an opt-out in Settings |
| Browser analytics and guest server-side analytics | Consent (Art. 6(1)(a)) |
| Research and data-licensing program | Consent (Art. 6(1)(a)) |
| Sensitive (special category) data in personas and Mature (18+) / Private (18+) rated content | Explicit consent (Art. 9(2)(a)) |
| Billing, tax, and legally required records | Legal obligation (Art. 6(1)(c)) |
| Content moderation and safety enforcement | Legitimate interests (Art. 6(1)(f)); legal obligation where the law requires it |
| Responding to legal requests and defending legal claims | Legal obligation (Art. 6(1)(c)) and legitimate interests (Art. 6(1)(f)) |
Where we rely on legitimate interests, we have weighed those interests against your rights and freedoms. Where we rely on consent, you can withdraw it at any time, and withdrawal does not affect processing that already took place.
How We Handle Your Content
- Automated processing is required to run Wilds. Your content is processed by our application and the AI models you choose so Wilds can generate responses, memories, summaries, art, and other outputs. Wilds is an AI service: the characters, narration, dialogue, and images you interact with are generated by artificial intelligence.
- We do not use advertising analytics to record your raw writing. We do not send your raw prompts, stories, or character dialogue to Google Analytics, Clarity, or Plausible as analytics payloads.
- First-party operational logs can include text. Some server-side interaction records may store prompt text or AI output text. These records are treated as restricted operational data, not public creator analytics.
- Human access is limited. We do not routinely have employees read private content, but authorized personnel may access limited data when necessary for support, debugging, fraud/security investigations, abuse incidents, or legal compliance.
- Operational audit notifications. Some events post an internal, timestamped notification to a staff-only audit channel on the wilds.ai Discord server. A notification about your account or a report you make names you by your display name (or, if you have none, your username or masked email) and links your public profile if you have claimed a username. Creating an account, linking a Discord identity, verifying your email, or asking for a new verification email also posts your masked email (e.g.
j**e@example.com) and account ID, with the sign-in or verification method where it applies; linking a Discord identity also posts the linked Discord account and whether the link earned its credit reward. Opening a support ticket in wilds.ai, yourself or through Wilo, posts one line that tells staff only that a request is waiting, with its reference (a short code such as S-2K9D), how long it has waited and a link to it on our staff pages. That line holds nothing you wrote, no name, no email address and no ticket or account ID, and no staff thread is opened for it. Until November 19, 2026, opening a support ticket posted its subject and category, the first 1,024 characters of your message, your name, your masked email, the ticket and account IDs, and a link to your public profile if you had claimed a username, and opened a private staff thread on the same Discord server holding the subject, the category, the first 3,500 characters of your message, your username if you had claimed one, and the ticket ID. Reporting content also posts what you reported and its ID, the category, the first 1,024 characters of your description, and the report's ID; reporting a comment also posts the comment's ID and the first 1,024 characters of your reason. An unusual burst of referral rewards on one referral link posts the referrer's username (or masked email), account ID, and the number and times of those referrals. Your full email address never leaves our servers in these notifications; the masked form is enough context for staff while reducing exposure if a staff seat is compromised. Staff use these notifications to answer support requests and to triage abuse and safety reports. Discord stores them on our behalf and is listed at /legal/subprocessors. You can request deletion of an audit-log entry or a staff thread by emailing team@wilds.ai. - AI providers. When you use cloud AI models, relevant context is sent to the selected provider to generate outputs. Local-model mode can keep generation on your own infrastructure when configured.
- Search ranking. When Wilds looks something up on the web, it ranks the results by relevance with a model that runs on our own servers. An AI model from one of the AI providers listed at /legal/subprocessors may then order the best of them, and receives the search query and the first 200 characters of each of those results. For example, this happens while Wilds builds a world, adds lore or writes a character from a source, and when a character or the Research tab searches for you. A query can contain words you typed or words from your conversation. When we rank the memories a character recalls, that ranking also runs on our own servers. Until November 11, 2026, Wilds sent the search query and the text of the results to Cohere, which ranked them. Until November 9, 2026, while a memory-ranking setting on our servers was on, Cohere also received stored memories and your current message, to rank which memories a character recalled.
- Information about other people in your work. A work you create can hold information about other people, such as an interview’s words, a quote or a person’s name. We store and process it to provide the service to you. When you use an AI feature on that work with a cloud model, the context the feature needs is sent to that model’s provider. Saving an ordinary WildWeave note can automatically send its title and the first 4,000 characters of its text to OpenAI for semantic retrieval using text-embedding-3-small, without running Assist or choosing a model. This transfer requires our embedding provider to be configured; source companion notes are excluded. Deleting a document removes its working copy and history. Deleting a storyboard from a book does not remove its text from an already published book snapshot, which remains readable through the public reader. To remove that copy, unpublish the book, republish it without the storyboard, or delete the book. Account deletion removes the published copy through the account-deletion process below, subject to legal holds and backup windows. Documentary scripts and their source material, including information about other people in them, are never part of the research and data-licensing program, even if the author has opted in. You are responsible for having the right to hold it. If you believe a work on wilds.ai holds information about you, write to team@wilds.ai or abuse@wilds.ai.
Staff access to user content
Wilds employs a strict-minimum-disclosure posture on staff-facing dashboards. The internal admin user-activity view shows per-account activity SHAPE only — counts of worlds and characters bucketed by content rating (Safe / Standard / Mature 18+ / Private 18+), counts of messages, and first/last activity timestamps. It does NOT show world names, world IDs, character names, character identifiers, message content, or any creator-set titles. Staff inspect a specific piece of content only case by case, for support, abuse investigation, or legal compliance. Routine activity monitoring never surfaces user content text or titles.
This restriction applies to dashboards, ranked leaderboards, audit notifications, and any aggregate report generated for internal staff use. The exception is what you send to staff yourself: the report notifications described above carry what you wrote and the ID of anything you reported, so staff can act on it. The restriction also does not apply when you, the account holder, view your own content through normal product surfaces.
Analytics and Cookies
Consent-Gated Client Analytics
Wilds uses a consent banner and settings controls for optional browser analytics.
- PostHog, Google Analytics 4 and Microsoft Clarity load only after you grant analytics consent. Until then, and after you decline or withdraw, your browser sends them nothing. We use PostHog for manual pageviews, named product events, funnels, cohorts, and masked session recordings; autocapture stays off.
- Plausible is self-hosted, sets no cookie and records no identity. It counts visits from your first page, before you choose. After you decline or withdraw analytics consent, and while your browser sends Global Privacy Control, it sends nothing, including automatic outbound-link clicks.
- Global Privacy Control. If your browser sends a Global Privacy Control signal, Wilds treats it as a refusal of analytics consent while that signal is active.
Purchase and Gameplay Events Sent From Our Servers
When you buy credits or start, change or cancel a subscription, our servers record it in our own database and add it to a count in Plausible with the plan and amount and nothing that identifies you. Gameplay events are counted in Plausible the same way, unless you have turned off first-party product analytics.
These events also go to PostHog and Google Analytics 4, under your account or guest ID, only if you granted analytics consent. When you are signed in, your choice on the cookie banner is saved to your account so that our servers can honor it. If you declined, have not chosen, turned off first-party product analytics, or your browser sent a Global Privacy Control signal, neither provider receives these events.
Google Ads
If you arrive from a Google ad with Marketing turned on, we keep the ad's click ID with your account. If Marketing is on when you make a purchase, we send Google Ads that click ID and the purchase amount so we can measure the ad. Otherwise we send Google Ads nothing.
Session Replay Privacy
When PostHog session replay is enabled, Wilds configures it to mask text in replays. We also disable autocapture and send only named events to keep collection intentional and controlled.
First-Party Product Analytics
Wilds also records first-party server-side interaction events for product operation, creator attribution, engagement analytics, fraud review, and service improvement. These events are stored in our own application database rather than in third-party advertising trackers.
Signed-in users can disable new account-linked first-party product analytics in account settings. This account-level control is separate from the browser cookie banner.
Guests are handled more conservatively: until a guest browser-analytics decision is synced server-side, new guest-linked interaction analytics stay off by default.
Research and Data Licensing Opt-In
Signed-in users can separately choose whether Wilds may include their de-identified interaction records in internal research, model-improvement, and any future external dataset or data-licensing program.
- This setting is off by default.
- This program-level opt-in is separate from routine product analytics.
- Where applicable, eligible de-identified records can include prompt text or AI-response text.
- We do not treat this setting as permission to disclose identified personal data.
- Current export controls hash actor/session/entity identifiers and scrub direct text identifiers such as emails, URLs, phone numbers, and name-like metadata before staff dataset export.
Personas and Conversation Data
Personas are saved player identities you create. Each persona can hold its own conversations, mood and relationship state, and memory with any character. You can maintain multiple personas under one account.
We store: the persona's name, pronouns, backstory, and any appearance fields you enter; per-persona character chat messages; per-persona relationship and mood state tracked by characters; per-persona uploaded attachments; and (on Plus or higher) AI-generated persona avatars.
Deleting a persona
When you delete a persona you choose one of two modes:
- Keep conversations. The persona record is removed and disconnected from past chats. Those chats remain readable and exportable as "Archived conversations."
- Erase everything. The persona and every character conversation, memory trace, conversation branch, and attachment that was scoped to it are permanently deleted from our primary stores, including the per-persona memory file on disk.
Account deletion always erases every persona and every persona-scoped conversation regardless of which deletion mode you used earlier. See the "Deletion and Retention" section below.
Exporting your persona data
The account export includes each persona's metadata (name, pronouns, backstory, appearance, avatar URL) and counts of conversations per persona with first/last activity timestamps, so you can see what you have before deleting.
Sensitive (Special Category) Information
Some Wilds features involve special category personal data under GDPR Article 9:
- Persona identity fields. Race or ethnicity, religion, and sexual orientation are optional persona fields. They reveal special category data about you.
- Mature-rated content. Roleplay in the Mature (18+) and Private (18+) tiers can involve content concerning sexual activity.
Wilds asks for your explicit consent under Article 9(2)(a) for this processing, separately from accepting these policies. You grant it through a dedicated step, which the app shows before sensitive persona fields are saved and may show before Mature (18+) or Private (18+) content. Each grant is recorded with its date and the policy version in effect.
You can withdraw this consent at any time in Settings > Privacy, Stats & Data Use:
- Withdrawing consent for sensitive persona information clears race/ethnicity, religion, and sexual orientation from every persona on your account.
- Withdrawing consent for Mature (18+) and Private (18+) rated content means a request to set one of those ratings on a story session or a character is refused until you consent again.
Sensitive data is used only to operate the features you chose. Since November 2, 2026, the text of Mature (18+) and Private (18+) sessions and chats is not recorded in our interaction records, and those sessions and chats are left out of the research and data-licensing program.
Deletion and Retention
- Content deletion: When you delete worlds, sessions, characters, personas, or similar user content, we permanently remove that content from the live database, unless a legal hold applies. Copies stay in our backups until each backup expires, as "Backups" below describes.
- Account deletion: When you delete your account, we delete your private content from the live service: chats, drafts, personas and persona-scoped conversation data, runtime state, memory traces, attachments, your WildWeave documents and folders with their snapshots, exports, simulations, film studio edits, proposals, imports, uploaded files, their rights declarations and storage totals, your account’s saved film looks and composers, stock favourites and collections, and the files stored for them (imported media, preview renders, exports, portraits, storyboard images and the references you uploaded), your taste profile, and your auth + linked-provider records. Copies stay in our backups, and earlier versions of stored files stay in file storage, as "Backups" below describes. A WildWeave file another account's work also shows is a shared copy, such as a storyboard clip the shared video cache gave both accounts and the still it was made from: it is kept while another account's work shows it and deleted when none does. The account shell remains soft-deleted for a 30-day restore window so you can change your mind via the link in the deletion confirmation email; after 30 days the shell is also purged. When you delete the account we cancel any paid subscription at once and retry until the payment provider confirms it has ended, and restoring the account does not restart it; we keep the payment provider's customer and subscription IDs until the provider confirms the subscription has ended, and for 31 days after that. First-party interaction analytics keyed by your account ID are deleted in the same pass. Anonymous aggregate statistics that no longer identify you may remain.
- Public content you've published — your choice at deletion time. If you published any characters or worlds to the public catalog, the deletion flow asks whether you want them removed entirely or kept available to other players (forks, in-progress sessions, leaderboard entries, multiplayer co-op invitees) under an anonymized "Anonymous Creator" attribution. This mirrors the freedom-of-expression carve-out in GDPR Article 17(3)(a) and the same pattern used by the Archive of Our Own ("orphan_account"), Reddit ("[deleted]"), and Stack Overflow ("user12345"). If you choose anonymized retention, your display name, username, avatar reference, and creator-attributed metadata are stripped from the artifact; the artifact itself persists. If you choose full deletion (the default), the public artifacts are deleted alongside everything else. Comics you published from WildWeave are not part of this choice: they are deleted with your account. You can also delete an individual world or character at any time, without deleting your account.
- Billing records: Billing and tax records may be retained for as long as required by law.
- De-identified reporting: We may retain anonymized or aggregated statistics that no longer identify you.
- Legal holds: Records flagged with a legal hold (active subpoena, abuse investigation, ongoing dispute) are excluded from automated deletion until the hold is released.
- Banned accounts: When we ban an account for acting against Wilds or its users, such as fraud, threats, extortion or coordinated abuse, we normally take its profile out of public view, take the worlds and characters it published out of browse and search, and hide its comments, reviews and leaderboard scores. A world or character it published can still appear elsewhere on the service, such as at a direct link, while the ban stands. We keep its account record, its content and the identifiers behind the ban (email address, linked Discord or GitHub account, IP address) for as long as the ban stands, and we review each ban at least once a year. We keep the identifiers so that the ban holds, and the account and its content so that we can reverse a mistaken ban and deal with any dispute or legal claim about it. Our legal basis is legitimate interests (Art. 6(1)(f)). A ban is not a deletion request, so the 30-day purge above does not apply while the ban stands. You can still ask for your data, ask us to erase it or withdraw a consent by writing to team@wilds.ai: we erase what we do not need for the ban or a legal claim. Once a ban is lifted the account comes back with its content, unless you had already deleted it yourself, in which case the purge applies as usual.
Backups
We back up the database once a day so that we can recover from a failure. The backup holds your account, worlds, characters, chats and stories, and the memory files your characters keep.
- On our server. Each daily backup stays on the server for up to 9 days.
- At Backblaze. A copy of each daily backup goes to Backblaze B2. We encrypt each copy on our server before it is sent, with a key Backblaze does not hold, and Backblaze encrypts it again at rest. Copies sent before we began this on November 12, 2026 have Backblaze's encryption only. We delete each copy at the first daily run after it is 30 days old, so within 31 days of when it was made. The newest copy stays until a newer one replaces it.
- Linode's backups of the server. Linode, our hosting provider, backs up the server's disk every day and keeps no backup older than 14 days.
- Before a release. We copy the database on the server before each release so that we can undo a failed update, and we keep the three newest copies.
Content you delete from the live service stays in these backups until each one expires. We open a backup only to restore the service after a failure, to recover lost data, or to test that a restore works. We use what is in a backup for nothing else.
If we restore from a backup, we first delete again what our record of deletions lists since that backup was made: accounts, worlds, characters, chats, stories, personas and Wilo conversations. We do this before the service comes back. The record is written when each of those deletions happens and is kept for up to five months. It holds the kind of thing deleted, its ID, the account ID and the time, and no content, name or email address. Smaller deletions are not in that record, such as a single comment, review, memory or WildWeave document. If a restore brings one of those back, delete it again or write to team@wilds.ai.
Pictures, audio, video and uploaded files are kept in Linode Object Storage and are not in the database backup. That storage keeps the earlier versions of a file. When a file is deleted its address stops working, and its earlier versions stay in that storage until we remove them.
Retention schedule
| Data category | Retention | Trigger |
|---|---|---|
| Account profile and creative content | Until account deletion, then a 30-day soft-deleted shell, after which the shell is purged | Account deletion |
| Guest records and guest content | Deleted when a guest that never moved into an account has not been seen for 30 days and staff run the guest sweep, which runs by hand, not on a schedule. A guest record that moved into an account is kept as the record of that move; its IP address hash, display name and character choice are cleared when staff run the sweep after the move is more than 24 hours old | Guest inactivity and a staff sweep; a move into an account |
| Character, session, and persona content | Deleted from the live service at deletion time (a persona deleted in "Keep conversations" mode keeps its chats); copies in backups expire as "Backups" above describes | Content or account deletion |
| First-party interaction analytics | Destroyed with the account; anonymized aggregates may remain | Account deletion |
| Server logs | 90 days | Rolling sweep |
| Consent records | Kept while the account exists, as the record of your consent | Account deletion |
| Email opt-outs, bounces and spam complaints | A one-way hash of the address, kept so no mail goes to it again, including after account deletion | Your opt-out, a bounce or complaint, or a do-not-contact request |
| Billing and tax records | Retained for the period required by applicable tax and accounting law, generally up to 7 years | Legal obligation |
| Banned accounts | Account record, content and the identifiers behind the ban (email address, linked Discord or GitHub account, IP address), for as long as the ban stands; the 30-day purge does not apply | A ban |
| Database backups | Up to 9 days on our server; up to 31 days at Backblaze (the newest copy until a newer one replaces it); up to 14 days in Linode's backups of the server; the three newest pre-release copies | Each daily backup; each release |
| Record of deletions (kind, IDs and time; no content) | Up to five months | A deletion |
| Earlier versions of deleted or replaced files | Until we remove them | A file is deleted or replaced |
| Records under legal hold | Until the hold is released | Legal hold |
We Do Not Sell Raw User Content
Wilds does not sell your raw prompts, full transcripts, or character conversations as standalone personal data products.
We may use or disclose:
- aggregated or de-identified engagement metrics
- world-level and creator-level public statistics
- internal benchmarking and diligence reporting
Wilds now exposes a separate in-product research and data-licensing opt-in for signed-in users. Any future program involving text-bearing interaction records must honor that explicit setting and applicable law.
Automated Decisions and Profiling
Recommendations. Wilds builds a taste profile from your activity to recommend worlds and characters. This is profiling on the legitimate-interests basis. You can object to it by disabling first-party product analytics in Settings > Privacy, Stats & Data Use.
Content moderation and enforcement. Automated systems help detect content that violates our policies and can hide content or restrict an account. If an automated decision restricts your account or content and has a significant effect on you, you can request human review by contacting team@wilds.ai. A person will review the decision, you can give your point of view, and you can contest the outcome.
Your Choices
- Cookie preferences: Use the consent banner, footer "Cookie Settings" link, or Settings > Tracking & Consent to control optional browser analytics cookies/storage, the purchase and gameplay events our servers send to PostHog and Google Analytics 4, and the purchase reports we send to Google Ads.
- Global Privacy Control: If your browser or extension enables GPC, Wilds treats it as a refusal of analytics consent while that signal is present.
- Guest analytics: Guest first-party interaction analytics follow the browser analytics choice once that consent is synced to the server.
- First-party product analytics: Signed-in users can enable or disable new account-linked product analytics in Settings > Privacy, Stats & Data Use.
- Research and data licensing: Signed-in users can separately opt in or opt out in Settings > Privacy, Stats & Data Use.
- Email: Notification emails (the weekly digest, comments, milestones, messages, referrals, Creator Jams, low balance and creator alerts) each have a switch in Settings > Notifications and are off until you turn them on. When you turn one on or off we record which kind, the words the screen showed, the screen, the version of this policy and the time, and we keep that record while your account exists. Every email we send carries an "Unsubscribe" link that works without signing in: in a notification email it turns that kind of email off, and in a sign-in, security, billing or policy email, which have no switch, it turns every notification email off. When you turn emails off through that link, when a mail to you bounces or is marked as spam, or when you ask us never to email you, we keep a one-way hash of your address (not the address) so we can honour it; we keep it after account deletion so the choice still holds.
- Account data: You can request export or deletion through account settings or by contacting team@wilds.ai.
- Support and privacy requests: Contact team@wilds.ai.
Your Rights
If you are in the EU, UK, or Switzerland, you have the right to:
- access the personal data we hold about you;
- rectify inaccurate or incomplete data;
- erase your data (the "right to be forgotten");
- restrict processing in certain circumstances;
- data portability: receive your data in a portable, machine-readable format;
- object to processing based on legitimate interests, including profiling;
- withdraw consent at any time, where processing is based on consent;
- lodge a complaint with a supervisory authority: your local EU data protection authority, the UK Information Commissioner's Office, or the Swiss Federal Data Protection and Information Commissioner.
You can exercise access, erasure, and portability directly in account settings through the export and delete tools. For any data rights request, contact team@wilds.ai. We respond within one month. For complex or numerous requests we may extend this by up to two further months, and we will tell you if we do.
The account export is delivered as a plain JSON, Markdown, HTML, or PDF file over an encrypted HTTPS connection. Once the file is on your device, it is your responsibility to handle it securely: store it somewhere private, and delete it if you no longer need it.
Account deletion is the broadest privacy control. Deleting your account deletes the chats, personas, memory traces and other private content listed under "Deletion and Retention" from the live service, with no grace period for that content. The account shell can be restored within 30 days, via the link in the deletion confirmation email, and comes back without that content. Copies in our backups expire as that section describes. Use account deletion whenever you want a clean exit.
California Residents
The California Consumer Privacy Act (CCPA), as amended, gives California residents rights including the right to know, delete, correct, and opt out of the sale or sharing of personal information, plus the right to receive notice at or before collection. We describe the categories of information we collect and the purposes for which we use them in this policy.
Wilds does not sell personal information in the ordinary sense of data-broker resale, and we do not sell raw prompts or transcripts. To exercise CCPA rights, contact team@wilds.ai.
Nevada Residents
Nevada residents have the right to opt out of the sale of certain covered information. Wilds does not sell covered information for third-party marketing purposes. Requests can be sent to team@wilds.ai.
Data Security
- Passwords are hashed before storage.
- Authentication uses signed tokens and server-side validation.
- Production database and object storage access are restricted to authorized application and operations workflows.
- The database backups we send to Backblaze are encrypted on our server before they leave it, with a key Backblaze does not hold, and Backblaze encrypts them again at rest (copies sent before we began this on November 12, 2026 have Backblaze's encryption only).
- Analytics tools are configured to minimize unnecessary capture and to respect consent controls.
- PostHog session replay is configured with masked text, and research/data-licensing eligibility stays behind a separate user opt-in.
- Staff-only interaction dataset exports require a server-side export salt and de-identification pass before records leave the primary analytics store.
If a personal data breach is likely to result in a high risk to your rights and freedoms, Wilds will notify affected users without undue delay, and notify the relevant supervisory authority within 72 hours of becoming aware of the breach, as required by GDPR Articles 33 and 34.
Children
Wilds.ai is not directed to children under 18. If you believe a minor created an account, contact team@wilds.ai and we will investigate and remove the account if appropriate.
Age is confirmed by your own declaration: we ask for it at sign-up or on your first sign-in, and the app may ask you to confirm it again before Mature (18+) or Private (18+) content. We do not verify age with documents.
Subprocessors
Every external vendor that may receive user data — AI providers, infrastructure, payments, email, analytics — is listed by category at /legal/subprocessors. The page is updated whenever a vendor is added or removed.
International Data Transfers
Wilds is operated from the United States. When you use Wilds from the EU, UK, or Switzerland, your personal data is transferred to the United States and to our US-based subprocessors and AI providers.
For these transfers we rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum for UK data, and the Swiss Federal Data Protection and Information Commissioner's adaptations for Swiss data. Where a recipient is certified under the EU-US Data Privacy Framework, we rely on that certification. The categories of recipients are listed at /legal/subprocessors.
Data Controller and Representatives
wilds.ai is operated by Framers Lab, Inc., 1301 N Broadway STE 78768, Los Angeles, CA 90012, United States. Framers Lab, Inc. is the data controller for personal data processed through the service.
Framers Lab, Inc. is appointing a representative in the EU and a representative in the UK, as required by GDPR Article 27. Their contact details will be published here once the appointments are complete. Until then, EU and UK users can raise any data protection matter directly with team@wilds.ai.
Changes to This Policy
When we make a material change to this policy we post the new version with its effective date and email the verified email address on your account on the day it takes effect. We post other changes with their effective date.
Contact
For privacy questions or to exercise your data rights, contact: team@wilds.ai
See also the Contact page.