Privacy Policy
This Privacy Policy explains what information ImmersivePage collects, how it is used, who it is shared with, and the choices you have. We have written it in plain language. If anything is unclear, please contact us at privacy@nightstandlabs.com.
1. Privacy at a glance
- You bring the content. ImmersivePage only processes documents that you upload, paste, link to, or import. We do not scrape, harvest, or pre-load any third-party content.
- Offline mode exists. When you use only on-device voices (Apple, Windows, Piper, Kokoro) and the rule-based "stub" cast analyzer, your document text never leaves your device or our server.
- Cloud AI and cloud voices are opt-in. If you enable an OpenAI-compatible LLM (for the optional experimental AI overlay) or a cloud TTS engine (Azure, ElevenLabs, Microsoft Edge online), the relevant portions of your content are sent to that provider under their own terms.
- Your keys, your relationship. When you provide your own API key for a third-party provider, requests are billed to your account and governed by that provider's privacy policy.
- We do not sell personal information.
- You can delete your data. Documents and cast profiles can be deleted from the library at any time.
2. Who we are
ImmersivePage is provided by Nightstand Labs LLC ("Nightstand Labs," "we," "us," or "our"), an Oregon limited liability company.
3. Information we collect
3.1 Information you provide
- Documents and content. The files you upload, the text you paste, and the URLs you link to. This includes the full text content of those documents and any images embedded in them (for the Illustrated mode feature).
- Cast and voice assignments. Characters, voices, traits, director presets, acting notes, and other production metadata you create or accept while reviewing the cast.
- Account information (if you create an account): email address, hashed password or third-party identity provider identifier, and subscription status. Authentication uses a JWT session token stored in your browser.
-
API keys. If you supply your own OpenAI,
Anthropic, Gemini, Azure Speech, ElevenLabs, or similar provider
API key, that key is stored on the server only for the duration
of your request, or in your local
.envfile if you are self-hosting. We do not transmit your keys to any party other than the provider you are calling. - Payment information (Pro subscribers only). Handled by Stripe. We do not see or store your full payment card details; we receive only the limited tokens, last-four digits, and webhook events Stripe sends us.
3.2 Information we collect automatically
- Product usage metrics (optional). Anonymous counts and timestamps to improve performance and reliability — for example: books uploaded, processing completed, listen time per book, how far you got in a book, manual speaker corrections, wizard steps visited, days since last use, and error categories. We do not include dialogue text, character names from your manuscript, or API keys in these metrics. You can turn this off anytime at the bottom of this Privacy Policy page.
- Diagnostic data. Server error logs, browser type, and timestamps when something fails — used to fix bugs.
-
Local preferences. Your theme, immersion preset,
speed, voice selections, and per-book preferences are stored in
your browser's
localStorage/sessionStorageon your device. -
Workspace files. Processed documents are stored
on the server (or your own machine if self-hosting) under
workspace/active/or per-user directories.
3.3 Information we do not collect
- We do not collect the contents of other documents on your device.
- We do not access your contacts or location.
- If you choose Photo or scan or Video page-flip (Pro), your browser may ask to use the camera; photos or recordings you add are uploaded for OCR and stored with your document like other imports. Uploaded videos are deleted after pages are extracted successfully.
- If you choose Dictation, your browser may ask to use the microphone. Audio you record is uploaded for speech-to-text transcription and stored with your document like other imports.
- We do not use behavioural tracking pixels or third-party advertising trackers in the product UI.
4. How we use information
We use the information described above to:
- Provide the service — import your document, split it into segments, identify characters and dialogue, assign voices, and produce playback.
- Save your library so you can resume listening, return to past books, and reuse cast profiles across a series.
- Personalize the experience — your theme, immersion preset, voice selections, bookmarks, and per-book preferences.
- Process payments for Pro subscribers via Stripe.
- Diagnose, debug, and improve the product based on aggregated usage and error data.
- Communicate with you about your account, service updates, security notices, and (only if you opt in) product news.
- Comply with legal obligations and protect against fraud, abuse, or violations of our Terms of Service.
5. Third-party services and your API keys
ImmersivePage can route different parts of your workflow to different providers. Each provider listed below handles your data under its own privacy policy. Cloud providers are opt-in (enabled by you when you choose a cloud TTS engine, provide an API key, or enable the experimental AI overlay). The free/offline configuration uses none of them.
5.1 Speech (TTS) providers
- Apple AVSpeechSynthesizer (iOS, macOS) — runs on your device. No content leaves the device for synthesis.
- Windows SAPI — runs on your PC. No content leaves the device for synthesis.
- Piper and Kokoro — offline neural voices that run on the server or your local machine. No content leaves your environment for synthesis.
- Microsoft Edge online voices — utterance text is sent to Microsoft's TTS service. See Microsoft Privacy Statement. We treat Edge TTS as preview-only and do not use it for paid production builds.
- Microsoft Azure Speech (Pro tier) — utterance text is sent to Azure using your or our subscription key. See Microsoft Privacy Statement.
- ElevenLabs — utterance text is sent to ElevenLabs using your API key. See ElevenLabs Privacy Policy.
5.2 Experimental AI overlay (LLM) providers
The optional experimental AI overlay sends chunks of your document text to an OpenAI-compatible LLM endpoint that you configure. The chunks are typically a few thousand tokens each and are used by the model to identify characters and attribute dialogue. Supported endpoint families include:
- OpenAI — OpenAI Privacy Policy.
- Anthropic / Claude (via OpenAI-compatible proxies) — Anthropic Privacy Policy.
- Google Gemini (via compatible endpoints) — Google Privacy Policy.
- Local / self-hosted runners (Ollama, LM Studio, vLLM, LiteLLM, etc.) — runs on your machine; no content leaves your network.
When you use the rule-based "stub" engine (the default when no API key is configured), document text is processed locally and is not sent to any LLM provider.
5.3 Payment processing
Pro subscriptions are billed via Stripe. See Stripe Privacy Policy. We receive subscription status, last-four card digits, billing country, and webhook events. We do not receive or store full payment card numbers. Refund and cancellation rules are described in our Refund Policy (incorporated into our Terms of Service).
5.4 Hosting and infrastructure
When you use our hosted service, document processing and storage take place on cloud infrastructure under contract with us. Provider identities, regions, and data-processing agreements will be listed here when the hosted production service launches. When you self-host via Docker or run the wizard locally, hosting is on your own infrastructure and we have no access to your content.
6. Offline / local-only mode
ImmersivePage is designed so that a complete reading experience is possible with no network traffic at all. To run fully offline:
- Run the wizard locally (or use the iOS / macOS app).
- Use only offline voice engines (Apple, Windows, Piper, Kokoro).
- Use the rule-based "stub" cast director (the default when no LLM key is configured).
- Do not enable Microsoft Edge online voices, Azure, ElevenLabs, or any LLM provider.
In this configuration, your document content stays on your device. The product is fully usable.
7. Storage, retention, and deletion
- Document workspaces. Processed documents are retained as long as your account is active or the file is in your library. You can delete any document from the library at any time. Deletion is immediate for active workspace files and is generally completed within 30 days for backups.
- LLM caches. Results from experimental AI overlay runs are cached on disk to avoid re-billing the same passages. These caches are deleted with the document.
- Account data. Retained for the life of the account. Account deletion is available on request via privacy@nightstandlabs.com; self-serve account deletion will be added to the product before paid launch.
- Audit and billing records. Retained as required by tax, accounting, and anti-fraud laws (typically up to seven years), even after account deletion.
-
Local data. Settings stored in your browser's
localStoragecan be cleared at any time through your browser's developer tools or by clearing site data.
8. Security
We use industry-standard security practices, including:
- TLS (HTTPS) for all hosted-service network traffic.
- Hashed passwords with modern key-derivation (e.g., bcrypt or argon2).
- JWT session tokens with reasonable expirations.
- Path-traversal guards on per-document asset routes.
- Principle of least privilege for service-to-service credentials.
No security system is perfect. If you discover a vulnerability, please report it responsibly to security@nightstandlabs.com.
9. Your rights
Depending on where you live, you may have rights regarding your personal information, including:
- Access — request a copy of personal data we hold about you.
- Correction — ask us to fix inaccurate information.
- Deletion — request that we delete your personal data ("right to be forgotten").
- Portability — receive your data in a structured, machine-readable format.
- Restriction or objection — limit how we process your data, including for direct marketing.
- Withdrawal of consent — where processing is based on consent, withdraw it at any time.
California residents (CCPA / CPRA): we do not sell or "share" personal information as those terms are defined in California law. You retain the rights of access, deletion, correction, and non-discrimination described above.
To exercise any of these rights, email privacy@nightstandlabs.com. We will respond within the timeframes required by applicable law (typically 30–45 days).
10. Children's privacy
ImmersivePage is not directed to children under 13 (or under 16 in the EU/UK). We do not knowingly collect personal information from children. If we learn that we have collected personal information from a child without verifiable parental consent, we will delete it. Parents or guardians who believe their child has provided us with personal information should contact privacy@nightstandlabs.com.
12. International data transfers
We are based in Oregon, USA. If you access ImmersivePage from outside the United States, your information may be transferred to and processed in the United States and in the countries where our third-party service providers operate. Where required, we rely on Standard Contractual Clauses or equivalent transfer mechanisms.
13. Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top and notify you via the product, by email, or both. Your continued use of ImmersivePage after a change becomes effective constitutes acceptance of the revised policy.
14. How to contact us
For privacy questions, requests, or complaints:
- Email: privacy@nightstandlabs.com
- Subject line suggestion: "Privacy request — [your request type]"
- Mailing address: to be published once entity formation is complete
15. Your preferences
You can change product settings that affect privacy here while signed in (or in local dev mode).