Privacy Policy

Vocifer AI Inc. ("Vocifer AI," "Vocifer," "we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, disclose, retain, and safeguard information when you visit vocifer.com, use our hosted model inference APIs (including OpenAI-compatible endpoints), join a waitlist, create a workspace, or interact with our sales and support teams (collectively, the "Services").

By using the Services, you agree to this Privacy Policy. If you do not agree, do not use the Services.

1. Scope and roles

This Policy applies to:

• Visitors to our website and marketing pages.
• Customers and authorized users who access inference APIs, dashboards, billing, and documentation.
• End users of applications that send traffic to Vocifer-hosted models through a Customer's integration (where applicable).

Controller vs. processor. For account registration, billing, website analytics, and direct communications with Vocifer AI, we act as a data controller. For prompts, completions, embeddings, and other content submitted through our inference APIs ("Customer Content"), we generally act as a data processor on behalf of the Customer (the data controller), except where we use aggregated, de-identified telemetry to operate and improve the platform.

2. Summary — API inference data (OpenRouter / marketplace disclosure)

The following summary is provided for transparency with routing partners (including OpenRouter) and customers evaluating data policies:

This summary reflects our default production inference tier. Enterprise contracts, confidential-compute preview programs, or specific SKUs may specify different retention or residency controls in writing.

3. Information we collect

a. Account and contact information

• Name, email address, company name, billing contact, and login credentials.
• Waitlist and early-access forms (email, company, use case notes).
• Support and sales communications you send to us.

b. API and inference usage data

• Customer Content: prompts, messages, tool payloads, files, or other inputs you send to our inference endpoints, and model outputs returned to you.
• Usage metadata: API keys (hashed at rest), organizationId, model identifiers, token counts (input/output/cache), streaming session metadata, error codes, and billing meters.
• Technical telemetry: request IDs, timestamps, source IP or network metadata, and routing information needed for abuse prevention and capacity planning.

c. Website and device data

• Log files, browser type, device information, referring URLs, and cookie or analytics events on our marketing site and docs.

d. Payment information

Payment card and invoicing details are processed by our payment processors (e.g., Stripe). We do not store full payment card numbers on our servers.

4. How we use information

We use information to:

• Provide, operate, and secure hosted model inference (including routing across hypervisors and GPU fleets).
• Apply performance optimizations—such as continuous batching, KV-cache–aware scheduling, and hardware-aware placement—to deliver lower latency and higher throughput. These techniques operate on in-flight request data and do not change our default policy against training on Customer Content.
• Meter usage per organizationId, generate invoices, and enforce plan limits.
• Detect fraud, abuse, policy violations, and security incidents.
• Communicate about service updates, incidents, billing, and onboarding.
• Improve the Services using aggregated or de-identified telemetry (e.g., error rates, latency percentiles, model popularity)—not using Customer Content for model training.
• Comply with legal obligations and enforce our agreements.

5. How we process inference requests

Vocifer AI hosts open-weight and frontier models on production infrastructure that may span multiple cloud regions and hypervisor stacks. Customer Content is transmitted over TLS, processed to produce a model output, and—by default—discarded from durable storage once the request completes and any legally required billing metadata is recorded.

We may temporarily retain Customer Content in memory, encrypted queues, or short-lived caches strictly as needed to complete inference, streaming, or failover. We do not build cross-customer datasets from API payloads.

Where we offer a confidential-compute or attested-inference track (in preview or under contract), additional technical and contractual controls may apply; those programs are described separately during onboarding.

6. Data retention

• Account data: retained while your account is active and for a limited period afterward for legal, tax, and audit purposes.
• API Customer Content: not retained in durable storage by default after delivery; optional debug retention only with consent or a support agreement.
• Usage and security logs: typically up to 30 days, unless a longer period is required for an investigation or legal hold.
• Marketing contacts: until you unsubscribe or request deletion, subject to suppression lists.

7. How we share information

We do not sell personal information. We may share information with:

• Infrastructure subprocessors (cloud providers, colocation, networking, observability) under confidentiality and data-processing terms.
• Payment processors to complete transactions.
• Routing or marketplace partners (e.g., OpenRouter) only to the extent required to list endpoints, attribute traffic, or comply with their provider programs—not to sell Customer Content.
• Professional advisors (legal, accounting) under duty of confidentiality.
• Authorities when required by law or to protect rights, safety, and integrity of the Services.
• Successors in a merger, acquisition, or asset sale, subject to this Policy or notice to you.

A current list of subprocessors is available on request at privacy@vocifer.com.

8. International transfers

We may process data in the United States and other countries where we or our subprocessors operate. Where required, we use appropriate safeguards such as Standard Contractual Clauses or equivalent mechanisms. Enterprise customers may request region-specific deployment options where available under contract.

9. Security

We implement administrative, technical, and organizational measures designed to protect information, including encryption in transit (TLS 1.2+), access controls, API key hashing, network segmentation, and vendor review. No method of transmission or storage is completely secure; you are responsible for safeguarding your API keys and workspace credentials.

10. Your rights and choices

Depending on your jurisdiction, you may have the right to:

• Access, correct, or delete personal information we hold about you.
• Object to or restrict certain processing.
• Port your data where applicable.
• Opt out of marketing emails (service emails may still be sent).
• Opt out of certain analytics cookies via your browser settings.

California residents may have additional rights under the CCPA/CPRA, including the right to know, delete, correct, and opt out of certain sharing. We do not sell personal information as defined by California law.

To exercise rights, contact privacy@vocifer.com. If you are an end user of a third-party application that calls Vocifer APIs, contact that application's provider (the data controller) first; we may redirect you accordingly.

11. Children

The Services are not directed to individuals under 16 (or 18 where applicable). We do not knowingly collect personal information from children.

12. Changes

We may update this Policy from time to time. We will post the revised version with a new "Last updated" date and, where required, provide additional notice (e.g., email or dashboard announcement). Material changes to API data handling will be highlighted in release notes or customer communications.

13. Contact us

Vocifer AI Inc.
Email (privacy): privacy@vocifer.com
Email (support): support@vocifer.com

For enterprise data processing agreements (DPA), subprocessor lists, or confidential-compute preview terms, contact privacy@vocifer.com.

See also our Terms of Service.