Your data deserves care

How is my data protected?

With care. Seriously! Your archive lives on your devices. When a feature uses the Internet, you deserve to know what leaves, where it goes and why.

Devices & QR · AI & audio · Draft links · Your choices

Your data has a home. Yours.

Your Personal Hub is the computer you choose to keep your people, conversations, notes, files and service connections. Linked devices hold encrypted local copies. Gravify’s account service handles accounts, licences and downloads; it does not store or back up your private archive.

Local non-AI work remains available without Internet. Sync, new downloads and remote services wait for connectivity. Assistant functions running on the Hub need a reachable Hub.

Your devices, a protected connection.

The QR pairs your own device with your Hub. Treat it as a secret invitation: it expires after ten minutes. Do not publish or share it. The alternative code retrieves the same encrypted invitation from a temporary mailbox. Its decryption key is derived from the code and is not sent to the server. Expired invitations are removed from service memory.

A Gravify service helps devices find each other across networks. When needed, a relay forwards encrypted traffic. Your device and Hub decrypt the content; the relay does not. Your Hub must stay on and reachable: we do not upload an online copy to replace it. Remote connectivity is still experimental.

Encrypted does not mean invisible. The service handles IP addresses, connection details, times and pseudonymous identifiers. Saying no data passes through our servers would be inaccurate. A direct address on your local or private network avoids Gravify’s sync relay; any VPN has its own infrastructure and policies.

Open projects and standards, if you like looking under the hood

We use the open source Coturn relay and aiortc on the Hub. WebRTC DataChannels use SCTP over DTLS. Connection descriptions, including certificate fingerprints, are authenticated with HMAC-SHA-256 and a pairing secret held by the endpoints. Mailbox invitations use AES-256-GCM. See WebRTC Security Architecture.

Installed replicas use SQLite encrypted with SQLite3 Multiple Ciphers. Service credentials stay encrypted on the Hub and are not returned to clients. Protect the Hub with screen locking, disk encryption and your own backups too: Gravify does not replace them.

Your AI choice. Local included.

Assistant settings → AI providers & voice lets you choose separate text and transcription services. With OpenAI or OpenRouter, the context needed for the request, or the audio you ask to transcribe, goes to that service. OpenRouter also involves the provider running the model. Requests leave your Hub directly, without a Gravify AI proxy.

Local AI accepts OpenAI-compatible servers on the Hub computer or your private network. You start the server and download its models; Gravify does not install them. Secretary functions need a model that supports tools. If your local service fails, the request fails there: it never falls back automatically to external AI.

A local address alone is not enough: the server must actually run downloaded models rather than forward to the cloud. Separately configured external agents use their own selected service and model. Separate worker sessions are not yet supported by local models: automatic delegation stops with an explanation instead of starting an external agent. Use HTTPS on shared networks: HTTP between computers does not encrypt the content. Automatic transcription of received audio stays off until enabled and respects the assistant’s access permissions.

Getting started with local engines

Ollama documents a compatible chat API. whisper.cpp server is an open source local transcription project; its native endpoint may need an OpenAI-compatible adapter. The server needs the corresponding /chat/completions or /audio/transcriptions endpoint with JSON responses and, for interactive chat, SSE streaming. Check model capabilities, paths and the version you install: servers are not all interchangeable.

Your Hub generates a reference to the workspace and review. The link contains no draft text, recipient or access credential. The website serves a generic page that opens your already linked app.

The reference follows #, so the browser does not include it in its HTTP request. Our script reads it on your device, prepares the app link and removes the fragment from the current address. The app checks the matching Hub. Opening a link never approves a change or sends a message.

The website still receives a visit to the generic page and normal technical metadata. The full reference may remain in your chat, clipboard or copied links: it is not anonymous, but it does not grant access to the draft. The messaging service remains an external service with its own terms.

How the opening page is protected

No third-party scripts or draft retrieval. Content Security Policy blocks script network requests; Referrer-Policy: no-referrer prevents referrer disclosure. The fragment itself is not encrypted: protection also relies on the integrity of your browser and the page served by the website. See URL fragments.

More control. Less noise.

To keep processing content on your hardware, use genuinely local text and audio models and a direct network connection, avoiding external features you do not want. Accounts, first activation and downloads still use online services. This does not make WhatsApp, email, web searches or other connected providers local. Downloaded maps stay local; fetching new detail sends map-area tile indices to the provider, without people’s names, notes or meeting times.

Disconnecting stops new access; removing imported content is a separate action. Closing your online account does not remotely erase your local archive. Read the privacy notice for account data, retention and privacy requests.

Open source lets people inspect those components; it is not an automatic security guarantee. Gravify is proprietary software that also uses open projects. We explain our choices and limits so you can make an informed decision.