DATA & TRUST
Keep it for the long term.
Keep control of it.
PAIA is your private material first, not a default data feed for a model. These are concrete boundaries in the current design and implementation, not a promise of absolute security.
Everyday use does not require an archive upload.
The core archive is stored locally in the Chrome extension. Ordinary reading, editing, lexical search and context preparation happen on-device. This website does not connect to your extension archive.
“Local-first” does not mean “nothing can ever leave the device.” Explicit use of optional external AI organization can send authorized material to the configured DeepSeek API in the current build. Copying, exporting or using material in another system can also create external copies.
Local storage is not an encryption claim. It cannot protect against every compromised device, deleted browser profile or storage failure. Protect your device and keep independent backups.
Editing today does not rewrite yesterday.
Source records preserve what came from the source. Working text is for everyday reading and editing. AI organization is a presentation derived from that material. Ordinary edits do not overwrite Source. Automatic processing should not silently undo your edits or exclusions.
Each letter should explore one question I genuinely want to understand.
Begin each letter with a concrete observation, then explore one question I genuinely want to understand.
Sending a passage does not necessarily mean believing it. Quotes, third-party material, hypotheses and role-play should not automatically become your lasting opinions. Review AI organization; it should not invent a tidy story of personal growth.
Four actions. Separate boundaries.
- Keep inputs
- Consent to retain eligible user text. Not permission to read arbitrary pages, drafts or files.
- Use external AI
- A separate, explicit action over authorized material. Retention is not permission to upload.
- Copy or export context
- Select and preview, then use it yourself. Preparing is not sending; external copies cannot be recalled.
- Device sync and connected access
- Require independent product and permission boundaries. General cloud sync and a real external AI reader connector are not current release claims.
Hiding, removing from a topic, removing from the archive, permanent deletion and excluding from AI use are different actions. Filtering changes reading visibility, not deletion or permission. PAIA deletion applies within its control, not to third-party platforms or copies already exported.
Worth keeping. Possible to leave.
Open export lets you take understandable material with you; backup is for library recovery. Those paths exist in the current code, but parts of real large-library, private official-export and consumer-distribution verification are still incomplete. Beta should not be your only copy. Check independent backups before updating or restoring.
Deleting a chat on the original platform does not automatically delete content already kept in PAIA. Deleting in PAIA does not automatically delete the original chat.
What about this website?
No analytics scripts, ad trackers, remote fonts or archive connection. Sample inputs live only in page memory and clear on reload. Only submitting a beta application sends its fields through FormSubmit to the project email. Website hosting and the form provider have their own data-processing boundaries.
PAIA · PRIVATE BETA
Give your next thought
somewhere to begin.
Start with the words you already write. Not another habit to maintain.