1. Scope and pre-release status
This is Recalia’s pre-release privacy notice. Recalia is local-first, but optional connected features are not represented as fully local. The notice will be reviewed against the final SDKs, sync behavior, third-party AI options, and server regions before public launch.
2. Account and device information
Recalia may process an email address, internal user identifier, sign-in state, device type, OS version, app version, and security/device-management data. Passwords, verification codes, and API keys are not analytics parameters.
3. Imported knowledge
User-imported PDFs, documents, presentations, images and text can produce parsed text, OCR output, indexes, embeddings, summaries and tags. The product direction is to keep parsing, retrieval and local AI on-device whenever the selected feature supports it.
- General analytics must not contain full document text, file paths, embeddings, complete search queries, complete prompts, or complete AI answers.
- If a user enables sync or third-party AI, the relevant network data flow must be clearly disclosed.
4. Local and connected AI
Local model use is designed for on-device generation. If the user explicitly selects a third-party model or custom API, the context required for that request may be sent to the selected provider. API keys must not be sent as analytics parameters.
5. Analytics
The first public Recalia builds are planned to use Firebase Analytics for global distribution and Umeng Analytics for mainland China. The policy and store disclosures will be updated to match the actual integrated release build.
- No full private documents in analytics.
- No complete prompts or answers in analytics.
- No passwords, verification codes, API keys, or email addresses as analytics parameters.
6. Retention and deletion
Local library data remains under device control. Deletable server-side account, sync, device association, and configuration data should be removed through account deletion, subject to narrowly scoped legal or security retention.
7. Contact
Privacy and data questions can be sent to [email protected]. Do not email passwords, verification codes, API keys, or complete private documents.
