How Vocalis handles information across content workflows and connected systems.

Scope and operator

This policy covers the Vocalis website, application, workspaces, support interactions, and connected features. Vocalis is a product and service operated by OXEFY FITNESS SERVICES (OPC) PRIVATE LIMITED.

The operator can be contacted for privacy and data requests at [email protected]. Processing is limited to operating and securing the service, fulfilling customer requests, administering accounts and subscriptions, meeting legal obligations, and optional activities for which consent is requested.

Account, workspace, and membership data

Vocalis processes authentication identity and profile information such as email address and name, together with workspace names, settings, roles, membership, invitations, and access records needed to provide and secure the service.

Workspace owners and administrators control membership and settings within the permissions made available by the product.

Voice, Persona, and brand data

The product may process Voice and Style settings, Persona selections and records, brand identities, brand kits, generation presets, templates, logos, background assets, and other customer-provided brand material.

Brand Knowledge features may process uploaded sources, extracted text, documents, chunks, refresh records, and embeddings so requested content can use approved workspace context.

Inputs, generated content, and workflow history

Vocalis processes prompts, voice or text inputs, uploads, draft projects, generated text and media, editing/version activity, topics, trends, ideas, quality results, and related workflow records when customers use those features.

Customers remain responsible for having the rights needed for their inputs and for reviewing generated output before use or publication.

Connected platforms and OAuth data

When a customer connects a supported platform, Vocalis may process platform identifiers, account or page names, selected destinations, granted scopes, connection health, publishing jobs, provider post identifiers, and authorization credentials needed for the requested integration.

OAuth access and refresh credentials are encrypted before local persistence and excluded from public projections. Disconnecting always clears locally stored authorization secrets. Vocalis also attempts provider-side revocation or disconnection where a verified provider endpoint is supported; failures are recorded for bounded retry, and some providers require a manual action in the provider’s account settings.

Disconnecting Vocalis does not automatically remove content already published to a third-party platform. Customers may need to manage that content directly with the platform.

Billing, usage, and operational records

The service processes plan, subscription, transaction, invoice-reference, entitlement, usage, fraud/risk, support, notification, job, audit, and security records needed to operate and protect paid and free workflows.

Payment details are handled through the provider shown for the checkout route. Razorpay processes India checkout in INR; Paddle may process international checkout in USD where enabled and approved; governed routing may use Razorpay in USD when Paddle is unavailable.

For Paddle transactions, Paddle acts as merchant of record where applicable. Razorpay processes payment on behalf of OXEFY FITNESS SERVICES (OPC) PRIVATE LIMITED. Vocalis does not store full payment-card details.

Cookies, browser storage, and analytics

Necessary browser storage supports authentication, session continuity, consent state, and application operation. The product stores a versioned vocalis_cookie_consent record in local storage.

When configured, PostHog initializes only after the relevant optional consent is granted. The banner and persistent Cookie Settings control allow Analytics and Marketing to be selected independently. Withdrawing all optional consent opts out and resets PostHog on that browser.

Paddle or Razorpay browser scripts and storage may be used only when the corresponding checkout flow is opened.

AI processing

When requested functionality uses AI, Vocalis may send the relevant prompt, instructions, content, file, or structured context to an enabled AI service provider for that request.

The provider allowlist includes conditional AI providers, but only a provider enabled and selected for a requested task receives the relevant data. Inclusion in the allowlist does not mean every provider is active or used simultaneously.

Purposes and sharing

Vocalis processes data to authenticate users, operate workspaces, generate and review content, manage brand context, connect selected services, publish when instructed, administer subscriptions, communicate service events, prevent abuse, provide support, and diagnose reliability.

Data is shared with infrastructure, payment, communication, analytics, AI, or customer-selected publishing providers only when the relevant service is enabled or requested. Provider-specific disclosure requires verified Production use and role classification.

Security and retention truth

Vocalis uses reasonable technical and organizational safeguards evidenced in the product, including authenticated access, workspace authorization, encrypted credential storage, and secret-safe projections. No system is risk-free.

Vocalis maintains a server-owned, versioned category retention registry and a bounded purge executor. An owner-approved schedule applies minimum-necessary periods by data category, uses explicit reviewed exceptions, and gives verified erasure priority wherever legally possible. Production destructive purge remains subject to a controlled release and clean 24-hour dry-run review.

Approved erasure deletes live customer content and records a hashed tombstone. Backups remain governed by infrastructure-provider expiry and recovery behavior; reconciliation reapplies tombstones after a restore so deleted profiles and anonymized workspace shells do not silently reappear.

Deletion truth

Authenticated customers can request account erasure from My Profile, and workspace owners can request workspace erasure from Workspace Settings. Server preflight blocks unsafe requests involving active subscriptions, active publishing work, or unresolved ownership duties.

Approved requests run asynchronously with idempotent step receipts. Customer content, derived records, allowlisted storage objects, local provider credentials, and scoped memberships are deleted; legally required financial evidence and security/audit integrity may be retained in minimized form. A non-customer-content anonymized workspace shell may remain where referential integrity requires it.

Privacy requests and policy updates

For access, correction, deletion, restriction, or other privacy questions, contact [email protected] and include enough account or workspace context for the request to be verified. Rights depend on applicable law; we aim to acknowledge normal enquiries within 2 business days without promising resolution in that period.

The policy ID, version, effective date, and last-updated date appear above. Material changes are reflected in a new version. Terms acceptance is stored as append-only evidence tied to the exact policy version and revision hash; reacceptance is requested only when the server-owned policy registry marks it as required.