Help · version 0.1.13
Your data and privacy
Your imported private content, source credentials, relationship calculations, and personal settings stay in the Personal Hub on hardware you control. Gravify's hosted account and licence service verifies your account and licence; it does not receive your imported messages or relationship map.
Connecting a source authorizes your Personal Hub to obtain the history that source makes available. You remain in control of disconnecting it, exporting your data, or deliberately deleting local data. See Uninstall and deletion before removing Gravify.
Device access is under your control
Open Settings → Privacy & Permissions to inspect contact, location and notification access on this device. Device permissions and notification delivery preferences apply separately to each client. A system status of Allowed does not mean you enabled every Gravify feature.
Windows device contacts require an explicit confirmation in Gravify and are imported read-only. Turn off contact access stops further reads; it does not erase people already imported. Location is used only on an explicit foreground action, with no background location tracking. Test current location reports whether a position was found without saving it. System permissions are managed through the linked operating-system settings; provider account access is managed in Accounts & Data Sources.
See Settings and customization for the controls and Importing and storage for the address-book workflow.
AI and external content
If you use Assistant, relevant context goes to the model provider you choose. External email images can contact their host when loaded. Keeping your archive on your hardware does not mean these explicit network features run entirely offline.
Follow the data
How Gravify takes care of your data explains device linking, encrypted remote relay traffic, QR invitations and private draft links, including the open projects and standards involved. The small data-protection link is also available while pairing and on the browser page that opens a review.
In Assistant settings → AI providers & voice → Local AI, configure separate OpenAI-compatible API base URLs and model names for chat/generation and audio transcription. Addresses are reached from the Hub: 127.0.0.1 means that computer, not the phone. Start your own server and download its models first; Gravify does not install a model runtime. Chat requires tool-capable models and streaming SSE. API keys are optional for local servers.
Only localhost or numeric private-network addresses are accepted for Local AI. A base URL such as http://127.0.0.1:11434/v1 receives /chat/completions; the transcription base receives /audio/transcriptions. Some speech servers need an OpenAI-compatible adapter. Use downloaded local models rather than cloud-forwarding modes. Local requests bypass system proxies, reject HTTP redirects and never fall back to an external AI service. Separately selected external agents retain their own provider boundaries. Automatic received-audio transcription remains opt-in.
Direct Hub access over your own local/private network avoids Gravify's sync relay. Remote linking can instead use a relay which forwards encrypted content but handles connection metadata. Account activation and downloads remain online services; choosing local AI does not make connected messaging, mail, maps or web tools offline.
Local AI handles the secretary conversation, generation and transcription. Separate entrusted worker sessions still require an explicitly selected supported external executor; automatic delegation while Local AI is selected stops with an explanation instead of choosing one.
