1. Scope and roles
IndivieuOS is operated by Indivieu LLC. The parties' roles depend on the processing. A customer generally controls the purposes and use of personal information it places in its workspace; Indivieu processes that information to provide the requested service. Indivieu separately determines purposes for account administration, authentication, billing, security, service operation, support, and legal records. These descriptions are factual summaries, not legal conclusions about a party's role under a particular law.
Clerk provides account identity, authentication, sessions, and organization membership. IndivieuOS also keeps local account and membership records needed for product features. External providers control their own services and canonical records.
2. Data and processing purposes
Depending on the enabled products and features, processing may include:
- Account identifiers, email, membership, preferences, and access records to authenticate users and provide workspace access.
- Customer-entered business and project records, app state, files, and authorized CRM information to provide requested workspace features and integrations.
- File metadata and private file content for storage, scanning, preview, sharing, download, and customer-requested deletion. Files are organization-owned; authorized sharing is read-only and time-limited.
- Subscription, billing, payment-status, and provider-reference data to administer and reconcile billing. Payment-card details are entered with Stripe and are not intentionally stored in IndivieuOS.
- Support report content and optional, per-report coarse screen-size and online/offline diagnostics. Diagnostics are off by default. OS support reports are handled by the OS API and database; the reviewed application configuration did not identify a separate ticketing provider.
- Security, audit, and operational records to protect and operate the service, investigate issues, and reconcile transactions.
- Website and product analytics, including page and interaction activity and technical/session metadata. The current browser SDK does not expose an application-supported opt-out.
Product flows are not interchangeable. SalesVieu is a separate product path; its Viera service is not controlled by the OS Viera gate. Products that are not enabled or available to a customer should not be treated as active processing.
3. AI and optional product data
OS Viera setup and chat are blocked unless an explicit data-policy approval switch is enabled after the deployed provider configuration has been verified. The OS request path can send a question, up to 20 recent user turns, and one selected authorized workspace, project, or readable text document context through a separate Viera service. Its chat history is held in the current browser tab; the OS API does not persist it.
The product owner identifies Google Gemini as the Viera model provider, but the deployed API surface, billing status, model, provider-side logging, retention, processing locations, and subprocessors are not verified. The filter for recognized sensitive formats is incomplete. Do not submit secrets or unnecessary personal, sensitive, or confidential information. SalesVieu Viera is a separate service and its data handling is not verified here.
If OS Viera setup is enabled after the required approval, provisioning sends the authenticated user and organization identifiers, organization name, and an opaque workspace reference to the separate Viera service; it does not send chat history or Files content.
4. Providers
The current provider inventory was reviewed on November 6, 2026. Which provider receives data depends on the product and feature used. Provider-specific locations, transfer mechanisms, retention, and contractual references are not verified unless expressly stated in the inventory.
| Provider | Purpose | Data categories | Location |
|---|---|---|---|
| Replit | Application hosting, managed database, and private object storage | Account and workspace records, uploaded files, support reports, and technical or service records stored or processed by IndivieuOS. | Provider-specific processing locations and transfer details have not been verified; no country or transfer mechanism is claimed. |
| Clerk | Account authentication and organization membership | Account identifiers, email address, authentication and session records, and organization membership information. | Provider-specific processing locations and transfer details have not been verified; no country or transfer mechanism is claimed. |
| Stripe | Subscription checkout, payment processing, and billing operations | Billing identity, subscription and transaction details, payment status, and payment references. Payment-card details are entered with Stripe and are not intentionally stored in IndivieuOS. | Provider-specific processing locations and transfer details have not been verified; no country or transfer mechanism is claimed. |
| HeyCatch | Website and product analytics | Page views, click and rage-click activity, technical and session metadata, and custom events limited to approved service, category, placement, and state values. The application no longer links analytics to authenticated user IDs, names, email addresses, or signup timestamps. | Provider-specific processing locations and transfer details have not been verified; no country or transfer mechanism is claimed. |
| HubSpot | CRM integration and agency-service request tracking | For a connected CRM, information available under the permissions granted by the customer. For agency-service tracking, contact and organization identifiers, service request details, timelines, briefs, and submitted intake information. | Provider-specific processing locations and transfer details have not been verified; no country or transfer mechanism is claimed. |
| Google Gemini — OS Viera | Model provider identified for Viera. OS setup and chat remain blocked unless the OS data-policy approval switch is enabled after verification; this control does not apply to SalesVieu. | Potentially questions, recent user turns, and selected authorized workspace, project, or text-document context. The downstream Viera-to-Google request payload is not visible in this repository. | The deployed API surface, billing project, processing locations, transfers, retention/deletion controls, and subprocessor chain have not been verified; no country or safeguard is claimed. |
| Google Gemini — SalesVieu Viera | SalesVieu's separate stateful chat source uses the Gemini Developer API SDK. Its current model fallback list is Gemini 3.1 Pro Preview, Gemini 3 Flash Preview, Gemini 2.5 Pro, and Gemini 2.5 Flash; the deployed selection and billing state are not verified. | Current chat prompt, up to ten prior turns, optional editor draft, and server-assembled workspace context. The route does not persist transcripts; its separate credit ledger stores usage metadata and a SHA-256 request hash, not raw prompt text. | The live Gemini billing project, Google processing locations, transfers, provider-side retention/deletion, log retention, and subprocessor chain have not been verified; no country or safeguard is claimed. |
Customer-authorized integrations are not automatically Indivieu-appointed subprocessors. Their use depends on the permissions the customer grants and the service flow.
5. Security and retention references
Current public control summaries: Protected SalesVieu and billing operations check authenticated organization context. Billing and SalesVieu seat management require administrator access. Cross-origin browser access to the API is configured with an explicit allowlist. Credential-bearing authorization and cookie headers are configured for log redaction. Billing card details are handled by Stripe rather than stored by IndivieuOS. These are limited descriptions of implemented controls, not a certification or independent assessment. See the Security Practices page and the Privacy Policy.
Retention varies by data class; no general production deletion period for all workspace data is implemented. Membership removal, app uninstall, or subscription changes do not delete organization data. Account deletion removes the OS login and selected personal records, but not organization files, app data, or billing records. Files can be explicitly trashed, restored, or permanently deleted. The 30-day scheduled Trash purge is development-only, not production or staging.
Personal exports are generated on demand, are not permanent archives, and their download expires after 24 hours. They include the requesting user's profile and membership information, desktop preferences, completed setup tasks, user-scoped app data, notifications, service requests submitted by that user, and metadata for files uploaded by that user. They do not include file contents or all organization records.
Organization workspace exports are available to current owners/admins, expire after 24 hours, and provide a bounded live Projects and Files manifest with authenticated file retrieval paths, not embedded file bytes. They are not atomic snapshots or backups. Generic opaque app state, credentials, billing, security/audit, support, and SalesVieu/external-product records are excluded; results may be partial.
Authentication security events have a separate 180-day rule; resolved billing-recovery records have a separate 90-day rule. These specific rules do not establish a common retention schedule. See the Privacy Policy
6. Request a DPA
To request review of a Data Processing Addendum, email legal@indivieu.com with the subject DPA Request. Include the contracting organization's legal name, the workspace or product(s), your business contact, and relevant jurisdictions or processing questions. Do not include credentials, payment-card numbers, or unnecessary personal or customer content.
The request is subject to business/privacy and legal review, including verification of the applicable product and provider scope. A request, acknowledgement, or this overview is not acceptance and does not create or change a contract. Any DPA applies only if a separate version is reviewed and executed in writing by authorized representatives of both parties. No availability, turnaround time, or terms are promised by this request path.
This review copy is version 0.1, prepared November 5, 2026. It is not an operative DPA. Changes to this overview will receive a new version and preparation date.