Frequently Asked Questions
Answers to common questions about inCamera, privacy, billing, and more.
Privacy & Security
How does Zero Data Retention work?
Your prompts and documents never touch inCamera servers. They are sent directly from your device to our AI providers under Zero Data Retention agreements. Prompts are processed in memory and discarded immediately after the response is generated. No logs, caches, or stored transcripts are created. inCamera servers only handle authentication.
Can inCamera see my documents or prompts?
No. Your documents are processed locally on your machine and your prompts are sent directly to the AI provider through an encrypted connection. inCamera servers only verify your identity. Because no logs or stored data exist, neither inCamera nor AI provider employees can retrieve or review your content.
What happens if you receive a subpoena?
We can only provide information we have: that you have an account and your billing usage amounts. If compelled by legal process, no prompts, documents, or transcripts can be produced—they do not exist.
Is my data used to train AI models?
No. Our Zero Data Retention agreements explicitly prohibit the use of your data for training. Prompts are processed in memory and discarded immediately after the response is generated. No copy of your content is retained after processing completes.
Does using inCamera risk waiving privilege or work product protection?
No. inCamera is architected specifically to preserve privilege. Your content routes directly from your device to the AI provider under Zero Data Retention agreements—we never receive, store, or have access to your work product. There's no third-party disclosure because there's no third party in the data path. Courts generally recognize a "functionality exception"—using necessary tools (transcription services, cloud processing) doesn't waive privilege if reasonable confidentiality steps are taken. With inCamera, there's no third-party storage; processing is ephemeral. This is architecturally the stronger argument for privilege preservation compared to uploading files to a web server where they sit in a database you don't control.
Architecture & Vendor Comparison
"But my vendor says they encrypt everything."
Encryption at rest protects stored data from unauthorized access to the storage medium. During AI inference, your content is plaintext in the vendor's compute environment—the vendor decrypts to process your query. KMS keys sit on the same infrastructure. "Encrypted" means nothing when the vendor decrypts to process. The question to ask: where does your data exist during processing, and who can access it?
"But they have a ZDR agreement."
ZDR is one layer (Pillar 2 of three). Without a local client (Pillar 1), your content still routes through the vendor's servers—they have it in transit even if the AI provider discards it. Contractual controls help. Architectural controls are the ones that survive a court order. For the full framework, see Why Architecture Matters.
"But we're the data custodian per the contract."
Processor/custodian framing comes from GDPR, not the Stored Communications Act. Under 18 U.S.C. § 2703, if the vendor stores your data on their servers, law enforcement can compel production regardless of what the DPA says about custody. The SCA doesn't care who the contract calls the custodian. For a detailed analysis, see our SCA framework article.
"What about Anthropic's ZDR API?"
Anthropic's API with ZDR addresses one layer: the model provider won't retain your data. But if you're using a SaaS wrapper that routes through their servers before reaching Anthropic, you've added a second entity to the content path. inCamera's architecture adds the client-side layer: your content goes from your device directly to the provider. We're never in the data path.
Using AI
What about AI hallucinations?
AI can generate plausible-sounding but incorrect information—that's true of every AI tool. inCamera doesn't change this; we're a privacy layer, not a magic accuracy filter. You remain responsible for reviewing all AI output before using it. The difference is that with inCamera, your review process isn't creating a discoverable record on someone else's servers.
How does this affect my billing?
That's your call. Some attorneys bill for the time spent reviewing and refining AI-assisted work. Others treat AI efficiency gains as part of their competitive advantage—faster turnaround, same rate. Some pass tool costs through as a case expense. The ethics rules are still catching up, but the principle is consistent: you're billing for your professional judgment and work product, however you produce it.
Billing
When does billing start?
Billing begins after your account is approved and you've activated it. You'll select your plan during the onboarding process in the app.
Can I cancel my subscription?
Yes. You can cancel at any time from your account settings. Your access continues until the end of your current billing period.
Do you offer refunds?
New subscribers can cancel within 14 days for a full refund if inCamera doesn't meet their needs. Contact [email protected] for refund requests.
Account
Why do you verify bar credentials?
Our Zero Data Retention agreements exist because of who uses the platform. By verifying that every user is a licensed attorney in good standing, we can maintain these privacy agreements and ensure the platform is used for legitimate legal work.
How long does verification take?
Most applications are reviewed within 24-48 business hours. You'll receive an email once your account is approved.
Can I add team members?
Yes. Professional and Firm plans allow you to add additional licensed attorneys. Each team member requires separate bar verification. Contact us for adding non-attorney staff under your license.
Technical
What platforms are supported?
inCamera is available for macOS, Windows, and Linux. Download links are provided in your approval email.
Does inCamera work offline?
AI features require an internet connection to communicate with our AI providers. However, your documents never leave your machine unless you explicitly include them in a query.
How do I report a bug or request a feature?
Contact us at [email protected]. We read every message and prioritize improvements based on user feedback.