Privacy Policy

This Privacy Policy explains how APEXMART LLC ("we", "us"), the operator of VidBook, collects, uses, stores and shares information when you use our website at vidbook.co and our hosted application (collectively the "Service"). By using the Service you agree to the practices described here.

1. Information we collect

The application processes the following information:

• Account data: your email address, display name and account identifiers. Depending on the deployment, authentication uses Clerk or self-hosted Better Auth. Passwords for email/password accounts are stored as hashes, not readable passwords.
• Project data you submit: text from caption files, transcripts or notes you upload or paste, YouTube URLs from earlier link imports, the transcripts we extract, generated outlines and chapters, publishing metadata and review checklists, and exported PDF, EPUB and DOCX files.
• Billing data from our payment processor (Stripe): customer, subscription and invoice identifiers, subscription status, and payment and chapter-credit receipts. Stripe handles payment-card entry.
• Usage analytics via PostHog: events can be linked to your account and project identifiers and describe feature usage and page paths. The Settings analytics opt-out applies to the current browser on this device. Our analytics instrumentation does not send transcripts or chapter content.
• Funnel counts: to see which steps lead to a finished book, we record one row the first time your account signs up, completes its first book, downloads an export, starts checkout and pays. Each row holds only the step, your account identifier and the date. Marketing pages also count visits: a random first-party cookie is combined with a key that changes every day, and only the resulting hash and the date are stored, at most once per browser per day. Visit counts are not linked to an account. No IP address, browser details or page address are stored with these counts. The visit count is not sent when the Settings analytics opt-out is on in that browser, or when the browser sends Do Not Track or Global Privacy Control.
• Refund-review data: the selected invoice, optional reason, request status and timestamps, payment-verification details, and verification-attempt counters.
• Operational logs: hosting and background-job services may record request metadata and application/job errors to help investigate incidents.

2. How we use it

We use the information above to run the Service, bill subscriptions, generate the books you ask us to generate, prevent abuse and improve quality. We do not sell personal data and we do not use your project content to train any AI model. Relevant source text and drafts are sent to the AI services configured for your deployment: Google Gemini, OpenAI, or OpenRouter and its selected model providers. Scoped OpenRouter deployments may also send assigned source text and chapter drafts to TypeSafe for an advisory source comparison. These services process content under their own terms and data policies. An AI review is not a guarantee that a draft is accurate or legally publishable.

Refund-review data is used to verify and record requests, limit abuse and support individual owner review. The intake does not send your reason or request history to AI services, email or analytics. Do not include card details, passwords, keys or other sensitive information in an optional reason.

3. Subprocessors

• Clerk (authentication in legacy deployments; migrated deployments use self-hosted Better Auth)
• Supabase (database + private object storage)
• Google Gemini (AI generation)
• OpenAI (AI generation)
• OpenRouter and selected model providers, including TypeSafe (scoped AI generation and advisory source review)
• Stripe (billing)
• Resend (verification and password-reset emails in migrated deployments)
• Trigger.dev (background generation and export jobs)
• PostHog (product analytics)
• Vercel or Cloudflare (hosting and edge network, depending on deployment)

4. Account deletion and privacy requests

Settings provides a "Delete account" action. It requires billing cleanup to succeed before application records are deleted. The billing cleanup calls Stripe to cancel subscriptions and delete the customer record; it does not establish erasure of all provider-held information. Database-backed projects, transcripts and chapters are removed with the application account.

Export files are not automatically deleted from object storage by that action. Complete deletion requires verified cleanup of storage objects, provider-held data and backups; that cleanup is not verified in this QA environment.

A privacy-request and personal-data export process is not available in this QA environment. The refund-review form is not a privacy-request channel.

5. Data retention

Some billing receipts are retained after account deletion for reconciliation and duplicate prevention, with the application-account link removed. Where refund intake is enabled, refund-review requests and verification-attempt records are deleted with the application account. There is no automatic cancellation-based project deletion schedule in the application.

Account funnel rows are deleted with the application account. Visit counts are deleted automatically after 90 days.

Retention periods for operational logs, refund-review data and backups are not yet defined or enforced as a complete policy in this QA environment. Public launch requires verified retention and deletion procedures; no fixed retention period is promised here.

6. Security

The application uses authenticated server-side ownership checks, database access controls, and signed download links. Export download links are issued with a five-minute expiry. These controls do not certify security or regulatory compliance.

7. Cookies

Authentication uses an httpOnly session cookie through Clerk or Better Auth. Analytics persistence uses a first-party PostHog cookie + localStorage entry. No third-party advertising cookies are set. The Settings analytics opt-out is stored in the current browser on this device; it is not an account-wide preference. Marketing pages set a first-party visitor cookie that lasts up to one year and is used only for the daily visit count described above; it is not set when the opt-out, Do Not Track or Global Privacy Control applies.

8. Children

The Service is not directed at children under 16 and we do not knowingly collect personal data from anyone under 16.

9. Changes

Material changes require an owner-reviewed notification process. That process is not yet verified in this QA environment.

10. Contact

For support or privacy questions, email apexmartindia@gmail.com. Do not send passwords, payment-card details or private source material. Public launch remains blocked until privacy-request handling and personal-data export processes are established and verified. Listing this contact does not establish those processes or promise a response deadline.