SD · Stories that answer back

Effective policy · English

Privacy Policy

# Story Divergence Limited-Beta Privacy Policy

**Version:** `privacy-beta-1.0-en`\
**Effective date:** October 25, 2026\
**Organization responsible:** Story Divergence Inc., Ontario, Canada\
**Privacy contact:** [admin@naunasolutions.com](mailto:admin@naunasolutions.com)

## 1. Scope and accountability

This Policy explains how Story Divergence Inc. (“Story Divergence,” “we,” or
“us”) handles personal information in its free, limited-capacity beta for
AI-generated interactive adult romance fiction (the “Service”).

The beta presently has a configured capacity of 21 admitted accounts and may
place additional applicants on a waiting list. It is not a named-invite allowlist
or country geofence. Known intended testers include adults in Ontario, Quebec and
Morocco; that does not mean Story Divergence is conducting a global marketing
campaign or that the Service is legally supported in every country.

The Service relies on an 18+ self-declaration and does not verify identity or age
using government identification. Story Divergence is accountable for personal
information under its control, including information processed by its service
providers.

Private story text and preferences can reveal intimate interests, relationships
or other sensitive information. We treat them as sensitive when associated with
an account.

## 2. Information we handle

We handle:

- **account and admission information:** email address, authentication and
  session identifiers, confirmation state, role, beta status, waiting-list or
  capacity status, 18+ declaration and security events;
- **private story information:** opening and partner selections, protagonist
  name, settings, preferences, instructions, dialogue, private thoughts,
  generated text, saved sessions, branches and story state;
- **community information:** likes, comments, reports, moderation state and the
  private account association for a comment displayed as “Beta reader”;
- **usage and operational information:** free-ruby grants, holds, accepted use
  and balances; request, provider and model identifiers; prompts or context sent
  for a provider operation; provider responses; token, cost, status, timing,
  retry, validation, failure and recovery records; IP address, browser/device,
  rate-limit and security events; and policy-acceptance records; and
- **communications information:** waiting-list or invitation consent evidence,
  unsubscribe state, support/privacy messages and account or incident notices.

The current beta has no integrated payment method or paid subscription and does
not collect payment-card information.

## 3. How and why we use information

We use information to:

- create, authenticate, secure and administer accounts and beta capacity;
- apply the 18+ self-declaration and admission rules;
- personalize, generate, validate, save, display and recover story pages;
- preserve accepted history and branches and avoid duplicate or lost turns;
- administer free rubies and reconcile provider usage and company costs;
- operate genuine likes, comments, reports, moderation and appeals;
- send requested account, security, support and beta communications;
- diagnose failures, preserve continuity and maintain recovery copies;
- prevent and investigate fraud, abuse, prohibited content and incidents;
- document policy acceptance, comply with law and establish or defend claims;
  and
- create aggregated or de-identified statistics that do not reasonably identify
  a reader.

We ask for express consent before processing sensitive private story information
for personalized generation. We do not sell personal information or use private
story text for third-party advertising. A materially new purpose will receive
notice and new consent where required.

## 4. AI and infrastructure providers

For generation, classification, direction, validation or recovery, the server
may send the current instruction, relevant story history, configuration and
generation instructions to one or more configured providers. This may include
private thoughts or other sensitive text you enter. We seek to limit context to
what the operation reasonably requires.

Depending on the deployed release and operation, the Service may use:

| Provider | Role and information | Retention and configuration disclosure |
| --- | --- | --- |
| Amazon Web Services (AWS Lightsail) | Application hosting; traffic and server operational data | The production instance is in AWS `ca-central-1` (Canada). Snapshot and log handling follows the production account configuration. |
| Supabase | Authentication and managed PostgreSQL; account, session, story, community, ruby and operational records | The production database connects through Supabase's AWS `ca-central-1` regional pooler. That Canadian connection endpoint does not establish that every Supabase subprocessor, support function or backup remains in Canada. |
| OpenAI | Prospective director processing and bounded Sol recovery; relevant context and operational output | Requests use OpenAI Responses with `store:false` where configured. This does not prove organization-level ZDR or Modified Abuse Monitoring. API data is not used for training by default under published business/API terms; ordinary abuse-monitoring logs may include content for up to 30 days. |
| DeepInfra | Qwen current-course routing/classification and direct DeepSeek specialist processing and recovery; relevant context and output | Published terms describe non-retention for hosted-model inference with exceptions for some features, support, security, law or third-party routes. We do not promise universal zero retention. |
| OpenRouter | Routing to selected model endpoints; relevant context, output and routing metadata | Route-specific logging, retention and training treatment may depend on OpenRouter and the downstream provider. |
| Anthropic Sonnet through OpenRouter | General story writing; relevant context and generated text | The configured route pins Anthropic and disables provider fallback. Anthropic's direct-API policy does not by itself establish the retention of an OpenRouter endpoint. |
| Fireworks through OpenRouter | DeepSeek specialist standby; relevant specialist context and generated text | The configured route pins Fireworks and disables provider fallback. Stateful, batch, cache or training features can have different treatment from ordinary inference. |
| Zoho ZeptoMail | Operational and archive email; email address and message content | Production operational/archive mail uses ZeptoMail. Provider systems may process information outside Canada. |
| Supabase authentication email delivery | Account confirmation and authentication messages; email address and message content | Authentication email is configured through Supabase. The underlying production SMTP delivery provider is not represented here as ZeptoMail unless that configuration is separately confirmed. |
| Owner-controlled recovery media | Recovery copies of application or database information | Copies are handled separately from active systems and may persist until manually replaced or destroyed. |

We do not represent that every provider is used on every request or that a route
has zero retention unless that exact account and endpoint support it.

## 5. Disclosures and public visibility

Private story sessions are not public comments. A comment and like count may be
shown publicly under “Beta reader.” Story Divergence privately retains the
account association needed for ownership, security and moderation.

Authorized personnel may access private information only where reasonably
needed for support, security, abuse investigation, reconciliation, recovery,
service operation, legal compliance or a privacy request. We may also disclose
information to service providers performing contracted functions, advisers
under appropriate duties, authorities where required or permitted by law, or in
connection with a confidential financing, reorganization or sale subject to law.

## 6. Processing outside your jurisdiction

Story Divergence is based in Ontario. Providers may process information in
Canada, the United States and other countries where they or their subprocessors
operate. Information there may be subject to foreign law and lawful access by
foreign authorities. Story Divergence remains responsible for selecting
providers and using contractual and other safeguards appropriate to the
information.

Ontario governing law does not remove mandatory privacy rights that apply where
you live or use the Service. Morocco-specific territorial and filing questions
are not represented in this Policy as finally determined.

## 7. Current retention and deletion behavior

The beta retains saved stories and account information for continuity. It also
retains accepted and failed operation records, provider request/response
artifacts, and accounting and recovery evidence to settle usage, diagnose
failures, prevent duplicate results and support recovery. A story reset or an
export email does not by itself delete those records, accounts, balances,
communications or recovery copies.

Account, profile, accepted stories, preferences and saved branches are generally
kept while the account or story remains active. Operational records may remain
while reasonably needed for continuity, settlement, error or security
investigation, or a dispute. Non-story accounting, consent, security and legal
records may remain after closure where reasonably required. Visible comments
remain until deleted or moderated, with limited evidence retained where needed.

The beta does not promise an automated deletion deadline or universal provider
zero retention. Owner-controlled recovery copies may remain until manually
replaced or destroyed. Personal information must not be kept longer than
necessary for identified purposes or legal obligations.

## 8. Your choices and rights

You may ask whether we hold personal information about you, request access,
challenge accuracy, request correction, withdraw consent, request an available
export, or request account closure and deletion of information no longer
required. Quebec users may also exercise applicable portability rights for
computerized information collected from them.

Send requests from the account email to
[admin@naunasolutions.com](mailto:admin@naunasolutions.com). We may request only
what is reasonably necessary to verify identity and locate records. Requests are
handled manually; the beta does not promise a self-service export or deletion
tool. We respond within the time required by applicable law and explain any
lawful refusal, extension or information that must remain.

Withdrawing consent needed for personalized generation may require closure of
the account or feature. You may complain to the Privacy Officer and to an
applicable privacy regulator.

## 9. Email, browser technologies and security

We send confirmation, security, service and support messages needed to
administer an account or answer a request. No promotional waiting-list or launch
campaign is currently being sent. Future commercial messages will require the
applicable legal basis, sender identification, contact information and
unsubscribe mechanism.

The Service uses authentication/session and security technologies needed to sign
users in and protect accounts. Necessary browser local storage may hold pending
or submitted reader text, story access/capability data, settings and recovery
state; session storage may hold timing metadata. Clearing browser data removes
those browser copies or settings but does not delete account, story or
operational records held on the server. Server-side requests must be made through
the privacy contact above.

We use safeguards proportionate to sensitivity, including server-side
authorization, access restriction, encryption in transit, secret management,
request minimization, rate limits and recovery controls. No system can be
guaranteed perfectly secure. We investigate incidents, maintain legally required
records and notify people and regulators when required.

## 10. Language and changes

French and English versions are available for a Quebec user. If the user elects
English after receiving access to French, the acceptance flow records that
express language choice with the accepted Terms and Privacy versions. Mandatory
rights are not waived by choosing English.

We identify each version and effective date, give reasonable notice of material
changes and seek new consent where required. A later policy does not
retroactively authorize earlier processing.

## 11. Contact

Privacy Officer\
Story Divergence Inc.\
Ontario, Canada\
[admin@naunasolutions.com](mailto:admin@naunasolutions.com)