V≡CTOR Privacy Policy

01 — WHAT V≡CTOR STORES

Account and authentication details needed to operate your account, such as your email address and profile information you choose to add.
Your longitudinal product state: Scan answers, Position history, sector evidence, Constraints, Priority, Destinations, Milestones, Experiments, Actions, Weekly Reviews, Life Log, assumptions, decisions, Memory, Patterns and related reasoning lineage.
Student academic records, authored learning evidence and saved study resources remain scoped to the authorized Student workspace; uploaded course sources use private storage and bounded indexing.
Business company models, operating observations, objectives, interventions, decisions and reviews remain scoped to authorized company workspaces.
Product-specific Paddle subscription records and access grants determine paid capabilities without turning company ownership or an unrelated purchase into payment authority.
Circle state you create or participate in, including authored updates, replies, reactions, relationship edges, sharing recipients, blocks, reports and accountability sharing.
Account-linked operational metadata needed to enforce limits, secure the service, administer subscriptions and understand product usage.
The exact Terms and Privacy versions recorded for your account and the time/source of that legal record.

02 — WHY IT IS USED

To maintain your Position and history over time instead of restarting reasoning from zero.
To generate and explain Constraints, Priority, Experiments, Actions and other V≡CTOR reasoning surfaces.
To operate account security, entitlements, billing, abuse limits, Circle privacy and product reliability.
To measure how the product is used and improve V≡CTOR without turning personal content into advertising.

03 — AI REASONING

V≡CTOR sends operation-specific context through the Lovable AI Gateway to the selected model provider when an AI-backed reasoning operation is required.
Before outbound AI requests, detected email addresses, phone numbers and card-like numbers are replaced with request-local placeholders. This is minimisation, not anonymisation: names and every sensitive fact cannot be reliably detected by deterministic matching.
Outbound requests currently use store:false where supported by the gateway request. V≡CTOR does not describe that setting as a guarantee of zero provider retention.
AI output can be incomplete or wrong. V≡CTOR preserves user authority: recommendations are proposals, not automatic permission to mutate major life decisions.

04 — EXTERNAL PROVIDERS

Supabase is used for authentication, the V≡CTOR database and private storage such as avatars and temporary privacy-export artifacts.
Paddle is used for checkout, subscription state and billing administration. Payment card details are handled by Paddle and are not stored in the V≡CTOR application database.
V≡CTOR does not claim provider-controlled retention periods it cannot itself enforce. Provider records may be subject to the provider's own operational, merchant or legal obligations.

05 — CIRCLE & OTHER PEOPLE

Your private product data is not automatically published to Circle.
Circle visibility is controlled by the sharing state you choose. Removing or blocking a person revokes the relevant relationship/sharing state rather than relying on an engagement feed or follower model.
Your data export contains your own Circle content and privacy state, but it does not copy another person's private profile/content merely because you shared a Circle surface with them. Other people are represented with export-local aliases where needed.

06 — YOUR CONTROLS

Profile → Privacy & Data Controls shows the current legal versions, provider boundaries, data export, retention classes and permanent account deletion controls.
Export My Data queues a durable private JSON build of your account and longitudinal V≡CTOR history. Completed artifacts are available temporarily for 24 hours through short-lived owner-checked download links, and generation fails rather than silently pretending a capped dataset is complete.
You can correct user-controlled data through the relevant product surfaces and Memory controls. Contact support if something cannot be corrected through the product.
You can permanently delete a normal user account from Profile. Download an export first if you want to keep a copy.

07 — WHAT ACCOUNT DELETION DOES

Permanent deletion is a durable staged process: V≡CTOR accepts a deletion request, cancels linked billing, removes temporary privacy-export/avatar objects, purges account-linked database state, deletes the authentication principal and only then marks the request complete.
If several Paddle product subscriptions are linked, the deletion workflow enumerates their distinct verified provider identities before continuing; a single newest subscription does not stand in for the account.
If a linked Paddle subscription exists, V≡CTOR must confirm cancellation before the database/authentication deletion stages continue. A crashed worker retries from durable state rather than reporting completion early.
A recent unconsumed checkout temporarily blocks deletion until that checkout window expires.
Admin/operator accounts do not use the self-service deletion path because CONTROL audit authority must not be silently destroyed.
Minimal security evidence may remain only after account identity and account-linked metadata are removed. A one-way SHA-256 fingerprint of a previously linked Paddle subscription may remain solely to prevent late billing webhooks from recreating deleted account state.

08 — RETENTION & SECURITY

V≡CTOR separates user-controlled product data, derived AI artefacts, shared/social state, security evidence, provider-controlled billing records and minimal deletion-integrity records instead of pretending they all have the same lifecycle.
V≡CTOR does not publish a fixed retention period for a class unless that period has a real basis and is operationally enforced.
Sensitive authenticated surfaces are designed to be private/no-store, service-role credentials stay server-side, and database/storage access is bounded by authentication and server/database authority.
No security statement means the service is 'unhackable'. Security hardening and later adversarial testing are separate disciplines.

Find your bearing.