Tasks should access only what they need.
Your data should remain
your data.
AJ is a personal AI, which means privacy cannot be an afterthought. This page explains what AJ currently does with personal information, the choices available to you, and the stronger user-owned architecture we are building through Project Sovereign.
Know you.
Not own you.
Project Sovereign is designed to reduce how much readable personal information AJ needs to hold or expose. The architecture is being rolled out progressively; planned cryptographic capabilities are not described here as current features.
Access should be tied to a defined reason.
One agent should not automatically inherit another agent's data.
Credentials and equivalent sovereign secrets should never enter model context.
Users should be able to withdraw access and delete information.
Our goal is to make significant data access understandable and auditable.
Who is responsible. LEDGERSLABS.AI LIMITED is the data controller for personal information collected by AJ and through this website. Privacy requests can be sent to privacy@ajassistant.com.
What AJ may process
Depending on the features you choose to use, AJ may process identity and contact information, messages and instructions, connected email/calendar/document data, personal memories and preferences, travel information, financial information, health or wellness information, and connector authentication information. Access depends on the service and permissions you connect.
Connected services
AJ is designed around scoped connectors. Connecting a service does not mean every AJ agent should receive unrestricted access to everything in that service. Project Sovereign is extending capability-level controls so access can be constrained by purpose, data sensitivity and agent.
AI models and external services
Some AJ tasks require external AI models or service providers. AJ's architecture already includes provider-egress policy and redaction for public-search queries, and Project Sovereign is being built to apply a shared data-classification and privacy-policy boundary more broadly. We do not claim that all processing is currently local, zero-knowledge or end-to-end encrypted.
If you use AJ through WhatsApp, WhatsApp/Meta remains the messaging provider and processes information under its own systems and policies. AJ can minimise what it retains, but it cannot make WhatsApp a sovereign or AJ-controlled transport. Messages and records held by WhatsApp or on your own device are not controlled by AJ.
Security
Our security architecture and Project Sovereign roadmap are explained on the Security page. Security claims are limited to properties we can support technically.
This section covers the Request Access form on this website.
What we collect
Your first name, email address and WhatsApp number, the time you agreed to this note, and which version of it you saw. We don't store your IP address with your request.
Why we collect it
To consider your request and, if you're invited, to message you on WhatsApp to set up AJ. We rely on your consent, which you give by ticking the box on the form.
- Joining the waitlist doesn't give you access to AJ, and we won't message you unless you're invited.
- We don't use your waitlist details for marketing, sell them, or use them to train AI models.
- We use Render to host the waitlist and WhatsApp to send your invitation if you're invited.
- Requests are stored on AJ's own servers, hosted by Render in the EU (Frankfurt).
How long
If you're invited, your details become part of your AJ tester account and are then covered by the applicable tester privacy information. If you are never invited, we delete your waitlist entry after 12 months.
You can withdraw consent, ask for a copy of what we hold, ask us to correct your details, request deletion, request restriction of processing or a portable copy where those rights apply, and object to certain uses where applicable.
For privacy or data-rights requests, email privacy@ajassistant.com. Withdrawing consent does not affect the lawfulness of processing before withdrawal.
For step-by-step deletion instructions, see Delete your AJ data. You can also revoke AJ's access to connected services in those services' account settings.
If you're unhappy with how we handle your request, you can complain to the UK Information Commissioner's Office.
Where privacy is going next.
Our roadmap includes a privacy ledger, governed memory, more granular capability permissions, user-facing data controls, local-first processing, stronger user-controlled key custody and confidential-compute research. These are goals and staged implementation work—not claims that every capability is live today.
See the security architecture →