Your information, explained
Privacy
with clear choices.
A practical overview of what stays on your device, what you choose to send, and the services involved.
Last updated September 13, 2026 · AXIS private Android edition
Visiting this website
This site does not include advertising trackers, analytics scripts, account forms or payment forms. Its images and fonts are served with the site. The hosting service may process standard request information, such as your IP address and browser details, to deliver and protect the website.
Your local workspace
AXIS keeps supported chats, notes, tasks and document records in an encrypted local database. Imported document files live in the app’s private storage. Device storage protections, screen locking and the security of your Android device remain relevant to those files.
You can edit or remove saved content using the app’s controls. Signing out restricts access to the workspace; it does not by itself erase the local records retained for your next sign-in.
Optional cloud sync
When cloud sync is enabled, supported chats, notes, tasks and document contents are encrypted on the device before upload. Your workspace recovery key is used to derive the encryption key. Cloud storage also holds account information and operational records needed to provide the service.
Cloud sync is not a permanent backup or an archive of every past version. Keep a safe copy of important original files. Network access and an available storage service are required to sync between devices.
When you ask AI for help
Sending a chat question or starting a voice conversation shares the information needed for that request with the connected AI service. This may include your message, relevant conversation context, preferences or saved memory supplied to the assistant.
If you attach an image or document, the selected content is sent for processing. Importing a document into your private library does not, by itself, send it as an AI request. Temporary chat changes how a conversation is retained in the app; it does not mean the request is processed only on your device.
AXIS uses ElevenLabs for its connected AI and voice functions. Provider processing is also subject to the provider’s own policies and the configuration of the connected workspace. AI responses can be wrong, so review important information and proposed actions.
Calls and approved follow-ups
The call inbox displays supported calls from a connected phone service, including available recordings, transcripts and summaries. Availability depends on the phone integration, provider settings and retention.
A callback requires review and approval of its recipient and message. The service retains operational and approval records to associate the follow-up with the correct call and prevent duplicate actions. Approved calls or messages share the necessary recipient and message information with the connected calling or messaging provider.
Voice cloning
A selected voice sample is uploaded to ElevenLabs to create a private voice. You must own the voice or have the speaker’s explicit permission. AXIS stores an enrollment record that associates the voice with your workspace and records the consent version. The assistant continues to identify itself as AI.
Use the voice controls in the app to review or remove an enrollment. Provider availability, verification requirements and allowance affect whether voice creation can complete.
Device permissions
Features may request microphone, camera, contacts, calendar, location or notification access when needed. You can decline a request or change access in Android settings. The related feature may be limited while permission is off.
Opening an email draft, map or another installed app hands the selected information to that app. Review what is being shared and the destination app’s own settings.
Account access and recovery
The current edition is restricted to its authorized account and does not offer public registration. Credentials and recovery material should be kept private. Losing the recovery key and all devices that retain it can make encrypted content inaccessible.
Some local, cloud and provider records are managed separately. Removing a local item, signing out or uninstalling the app should not be assumed to erase every provider-held record. Review the relevant in-app controls and connected provider settings when managing retained data.