Privacy Details by App

This page adds detail to our Privacy Policy: what each part of Cactive collects, who receives it, where it’s stored and how long it’s kept. The policy’s terms and rights apply to all of it.

• your name, email address and date of birth, when you create your account
• your password, stored only as a one-way hash we can’t reverse, or your passkey’s public key
• phone numbers you add, for sign-in codes and texts
• your two-step sign-in settings: an authenticator app’s secret (encrypted) and backup codes (hashed)
• your profile: display name, username, photo, banner, colours, About Me and language. Your profile photo can be seen by anyone who has its link.
• for each browser session and sign-in: the IP address, browser, operating system, device type, and the country, region and city worked out from the IP address
• for each phone you sign in on or approve sign-ins with: its name, model, operating system, app version and time zone
• if you use your Cactive account to sign in to another company’s app, the details you agree to share with it (your name and email address)
• Apps get only what your date of birth means, such as whether you’re 16 or over, never the date. You can set it once; after that, our support team corrects it if you show it’s wrong.

An organisation’s owners and administrators can:

• see and export its member list: names, email addresses, roles, titles, departments, groups and sign-in status
• see every browser session your account is signed in on, including ones you use outside the organisation, with each session’s IP address and approximate location
• read the organisation’s audit log, which records what members do there and every sign-in to your account, successful or not, with IP address and browser
• block you, sign you out, change your role, remove you (they can restore you for 30 days), and export the organisation’s data, including its mail and files

• Whatever you put in the apps is personal information when it’s about you or someone else: email, calendar events, contacts, files, photos and videos, notes, tasks, documents, spreadsheets, presentations, recipes, meal plans, receipts you send to Food, saved places, customer records, code repositories, messages, posts, voice messages and your conversations with Caity.
• Photos and files keep their metadata, such as where and when a photo was taken. Photos’ shared albums leave out locations unless you include them, and people who open a Drive file through a link get a copy without its metadata.
• Mail uses Amazon’s checks for spam and viruses, and looks up roughly where each message was sent from, using the IP addresses in its headers. Images in incoming mail stay blocked until you allow them. Mail doesn’t track whether people open the mail you send.
• Git and Cloud keep the names and email addresses of commit authors, and build logs for 90 days. Cloud counts visits to the sites you host from request logs without visitors’ IP addresses or browsers.
• You may give us information about other people, such as contacts, customer records, email recipients and people in your photos. Make sure you’re allowed to.
• We receive information about you from people who email you or share with you, your organisation, and services you connect, such as Discord for a connected Mirage server and Last.fm to show what you’re listening to. You can also bring in files from other services, such as a Google Takeout of your photos.

• On iPhone, Health reads the Apple Health data you turn on, such as activity, body measurements, heart, sleep, vitals, cycle tracking, symptoms, medications and mood, including in the background. Sensitive categories start off. It saves entries you add, and meals Food logs for you, back to Apple Health.
• Health information is sensitive information. We collect it only with your consent. Withdrawing consent in Health stops collection and sharing at once; deleting what’s stored is a separate step, Delete everything.
• Your individual readings are encrypted with a key of your own; daily totals aren’t.
• Only you can see your Health data unless you share it: with people or servers in Mirage, with apps or keys you connect, or with Caity once you allow it. Caity gets daily summaries, and never sexual activity.
• We don’t use Health data for advertising, sell it, or store it in iCloud.

• Our phone apps never ask for your location in the background (“Always”).
• Maps shows where you are on the map; that stays on your phone.
• Weather’s My Location and Home’s widgets send your location to us rounded to about 100 metres, to find the weather and aircraft near you. We don’t keep a history of where you’ve been.
• Places you save in Maps and Weather are kept with your account.

• If you turn on Caity by phone, you can call or text Caity from a number you’ve verified. Calls go through Amazon Connect and Caity listens and speaks with Amazon Nova Sonic; texts go through Amazon’s messaging service. We keep a transcript of each conversation for 7, 30 or 90 days (your choice; 30 by default). By default a summary and the transcript are also saved to Notes, where they stay until you delete them; you can choose Tasks instead, or neither.
• Mirage’s voice and video channels run on Amazon Chime SDK. We don’t record them. Voice messages are stored like other attachments.
• We text only numbers whose owners have agreed to receive our texts. Reply STOP to stop them.

• To send notifications to your phone, we keep a push token for it and send each notification through Expo’s push service, which passes it to Apple or Google. A notification can include part of what it’s about, such as a Mirage mention (up to 280 characters) or a post. A Mirage direct message notification shows only who sent it, unless the iPhone app decrypts the message on your phone.
• Home’s widgets read your phone’s calendars, reminders, and today’s steps and distance, to show them on your phone.

Card details go into Stripe’s form and to Stripe, not to us. We keep your Stripe customer and subscription identifiers, your card’s brand, last four digits and expiry date, your billing name, email address and address, your ABN or tax number if you give one, and your invoices.

• Caity and the AI help in Documents, Sheets, Slides, Video and Food use models made by Anthropic (Claude), Amazon (Nova) and OpenAI (gpt-oss), run by Amazon Web Services in Amazon Bedrock. Your content goes to AWS, not to the companies that make the models.
• Caity receives what you ask, your name, email address and organisations, and what it reads to answer from the apps it can use for you. It can’t use Photos, Health or Mirage until you allow it. In a Mirage channel, Caity reads the channel’s recent messages when someone asks it something; never direct messages.
• If your organisation connects Caity to another company’s service, the requests Caity makes there for you go to that company.
• Your conversations with Caity are kept until you delete them.
• Food reads photos of recipes and pantry shelves with Claude, then deletes the photos. Video makes captions with Amazon Transcribe, then deletes the audio it sent.
• Under AWS’s terms, Amazon Bedrock doesn’t use prompts or responses to train models or share them with the companies that make the models.

• Messages in servers and channels are stored so their members can read and search them. Direct messages are end-to-end encrypted: we store them encrypted and can’t read them, but we can see who messages whom, when, and the size of files. On the web, our servers fetch previews of links you send.
• Your social profile can be seen by signed-in people aged 16 or over unless you make it followers-only or private. A community server’s public page shows its name, banner, description and member count to anyone.
• Members of your servers, your friends and the people you message see your profile and whether you’re online, unless you’ve blocked them. How far you’ve read goes only to your own devices.
• Server moderators see reports about their server without who sent them; our staff see every report and who sent it. Reporting a direct message sends us the reported messages, decrypted. We keep reports and a copy of what was reported.
• Bots a server’s managers add receive messages that mention them and news of members joining, and can read channel history and the member list within the permissions they’re given; never direct messages.
• If a server is connected to a Discord server, messages, edits, reactions and files in its connected channels go to Discord under your name and profile photo, and messages from Discord come in under the sender’s Discord name and picture. If you link your Discord account, we keep its identifier, names and picture.
• GIF searches go to our GIF provider (KLIPY or GIPHY) with an identifier that isn’t your account’s.
• Deleting a channel message deletes it and editing one replaces it; a post keeps its edit history until you delete it. Deleting a channel message or a post doesn’t delete files attached to it; ask us and we will. Stories move to your archive after 24 hours.

• cactive.com.au sets no cookies of its own and runs no analytics or advertising scripts (Cookie Policy).
• Our delivery network logs each request to the website and the apps: the time, address, status, country and edge location, without your IP address or browser. We keep these logs for 90 days and use them for traffic totals.
• Our servers keep operational logs for up to 3 months, to run the service and fix problems.
• Feedback you send from an app includes what you write, any screenshot you attach (you can blur parts of it first), and details of the app, browser, page and recent errors; your email address only if you agree. It never includes cookies, sign-in tokens or what you’ve typed into forms.

Our phone apps ask for a permission only when you use a feature that needs it, and you can change your answer in your phone’s settings:

• camera: to scan QR codes, take photos and videos to upload or attach (recipes, pantries, issues, stories), and for Mirage calls
• microphone: Mirage calls and voice messages, and sound in videos you record
• photo library: to pick photos, and for Photos’ backup if you turn it on
• location, while you use the app: Maps, Weather and Home’s widgets
• calendars and reminders: Home’s widgets, and Food’s shopping list
• Apple Health: Health, and Home’s activity widget
• Face ID: to unlock the Authenticator
• notifications

The apps contain no advertising or analytics from other companies and don’t track you across other companies’ apps or websites.

Your history, bookmarks and site permissions stay on your Mac. Cactive Browser checks our download server for updates, downloads lists of ads and trackers to block from Ghostery each day, and sends what you search for to the search engine you choose (Google unless you change it). It sends us feedback only when you send it from the Help menu.

• Have I Been Pwned: if you turn on Watchtower in Passwords, your phone sends the first five characters of a password’s hash, which can’t identify you or the password.
• Our domain names are managed with Cloudflare; your traffic doesn’t pass through it. Maps’ flight and emergency information comes from public feeds; the areas people look at are added to our flight data requests without identifying anyone.

• Australia, in Amazon Web Services’ Sydney region: the apps and the API, our databases, file storage, Git and builds, captions and speech, and Caity’s requests to Claude.
• The United States, in Northern California, while our move to Sydney finishes: a second copy of our databases, our backups, the keys that encrypt stored data (with copies in Sydney), email sending and receiving, request logs, and some older file storage.
• The United States, in Oregon: Mirage voice and video, Caity by phone, face age checks, image generation and our backup AI model.
• The United States, in Northern Virginia: request logs on their way to storage.
• Around the world: Amazon CloudFront serves the apps from the location nearest you. Our service providers handle what they receive where the Privacy Policy says.

Most information stays until you delete it, or your account or organisation is deleted. Some goes sooner:

• an unfinished sign-up: 15 minutes
• sign-in history: 90 days
• an organisation’s audit log: 90 days to 3 years, depending on its plan; a Mirage server’s audit log: 45 days
• notices: 90 days; the record of notifications we’ve delivered: 30 days
• Mirage notifications: 90 days; what Feed ranks by: 60 days
• Caity by phone transcripts: 7, 30 or 90 days, as you choose; texts with Caity: 1 day
• delivery and server logs: 90 days and 3 months
• items in Trash in Drive, Photos and Mail: 30 days
• deleted information in backups: daily backups 35 days, monthly ones a year