← Ballistic

Privacy policy

Effective 23 September 2026

Who we are

Ballistic is operated by Psycode Pty. Ltd. Questions or privacy requests can be sent to [email protected].

Information we handle

You can use the local journal offline without an account. If you create an account or sync, we handle your name, email address, account UUID, and optional phone number, photo and biography. Password accounts store a password hash. Google sign-in provides identity details; Ballistic does not retain Google OAuth tokens.

Content can include tasks, projects, tags, notes and assignee notes. We also handle Ballistic connections and favourites (not your phone book), device and session data, push tokens, notification content, and security and audit records. Native notification services may initialise delivery or installation identifiers before sign-in.

How and why we use it

We use this information to provide accounts, optional sync, collaboration and notifications, keep the service secure, prevent misuse, and answer support requests. Connections and delegation share only the selected task and connection information with the people involved.

Service providers and optional integrations

Ballistic uses Cloudflare to route public traffic, Azure for hosting, AWS SES for email, and Expo and Google services for push delivery. They process the information needed for those services, including notification content and device identifiers, and processing may occur outside Australia. If you connect a third-party AI or MCP client, that provider receives the data you choose to expose and its own privacy policy applies. Ballistic does not include a built-in AI provider.

Security, retention and choices

Data is protected in transit with HTTPS, but Ballistic is not end-to-end encrypted. We do not sell personal information or use advertising, behavioural analytics or crash-reporting services. We do not request GPS, calendar, phone-book or microphone access.

Active data is kept while your account exists and as needed to provide the service. Security and server logs are retained as necessary for operations and security. Local database backups expire on a schedule after 14 days; Azure Blob backups are scheduled to expire after 35 days, although scheduled expiry is not a guarantee of immediate physical erasure. Push providers may retain installation identifiers under their own policies; Google documents that some may persist until API deletion and then for up to 180 days.

You may ask for access, correction, notification opt-out, or request account deletion. Confirmed deletion removes active account data. Shared task content retained by another user, copies sent to an external AI provider, and offline copies on other devices may remain. Erasing this device does not delete server data.

Age

Ballistic is intended for people aged 13 and over. Where local law requires parental consent at a higher age, that requirement applies.