Privacy Policy

Version dated 21 October 2026

This policy explains what personal data Qumuna collects, how and why we use it, who processes it on our behalf, how long we keep it, and the rights you have over it.

Data we collect

We collect account details (your name, email, and password), profile information you add (such as a photo, phone number, and birth year), the content you create (announcements, discussions, messages, events, polls, files, and reactions), and technical data needed to run the service (session tokens, device and browser information, and approximate activity timestamps).

How and why we use your data

We use your data to provide and secure the service: to authenticate you, deliver notifications and emails, run your communities, provide support, and prevent abuse. Our legal bases are performing our contract with you, our legitimate interest in keeping the platform safe and reliable, your consent for optional features, and compliance with legal obligations.

Optional AI features

The Support assistant and Translate are optional features provided by OpenAI through Replit AI Integrations. Each requires your separate personal agreement before processing starts. Accepting the User Agreement or a community administrator enabling translation does not replace your personal choice. You may use Qumuna without agreeing to either feature.

For the Support assistant, we send your messages and conversation history, requested language, and relevant account and community context, such as community names and your roles. On the website, this may include relevant plan and billing context. AI also classifies questions and checks replies and, when applicable, summarises the conversation to prepare a handoff to human support. Text you supply may contain personal information.

The assistant conversation is held temporarily for the chat; Qumuna does not save it as a persistent conversation record. Preparing a handoff does not itself submit a support case. If you submit a human-support request, including an edited or AI-prepared summary, Qumuna stores the submitted contact details, subject, message and attachments as support correspondence, with related case records and replies. Those records are separate from the temporary assistant chat and remain after the chat ends. No fixed automatic deletion period is specified here for that correspondence; use the contact options below to request erasure, subject to applicable legal and safety obligations.

For Translate, only the selected item's necessary text and target language are sent to OpenAI through Replit AI Integrations. Names, account or community identifiers and unrelated metadata are not supplied as separate identity fields. Names or other personal information already written within ordinary text may still be included; we do not promise that all such details are removed. Qumuna does not persist the translation or a separate copy of the source text for this translation process. The original item remains subject to its normal storage and deletion rules, and the translation is held temporarily for display.

When you write anything that others can read, including posts, comments, messages, announcements, events, polls, reports and appeals, people who can read it may choose to translate it with Translate, which sends that text to OpenAI through Replit AI Integrations as described above.

Qumuna stores your current choice separately for each AI feature, together with the notice revision and associated choice timestamps, including agreement or withdrawal. These records are not chat transcripts or translations. They remain with your account so that your choice applies across signed-in devices, and are cleared when your account is erased.

On both the website and mobile app, open Settings → AI features → AI support assistant or AI translation → Withdraw for the relevant feature. Withdrawal blocks future AI processing for that feature until you agree again. It does not undo processing already completed or itself erase support correspondence you submitted. Human Contact remains available, including without signing in or agreeing to AI processing.

OpenAI and Replit receive these requests as our service providers. They are contractually required to protect personal data at least as well as this policy. They may keep the data they receive for a limited period under their own terms and legal obligations, for example to detect and prevent abuse. Qumuna does not control those periods, and our temporary handling of chats and translations does not determine how long these providers keep data.

Optional device permissions

Qumuna requests photo-library, camera, microphone or foreground location access when you choose a feature that needs it, not as a condition of using unrelated features. You can deny a request, cancel a picker or recording, or change permission in your device settings (or browser site settings on the web). Where your device offers limited photo access, you can choose which items are available. Denying access stops the related selection, capture, recording or current-location feature; you can still use text and other features that do not need that permission. Revoking permission stops future device access but does not delete files or locations already sent to Qumuna or other recipients. Use the content controls or the deletion and contact options below for those records.

Selected photos, camera captures and audio

When you choose an item from your photo library or a file picker, Qumuna receives the selected file, not your entire library. Selected photos and videos can be uploaded for the feature you chose, such as a profile picture, community files, poll images or discussion attachments. Camera access lets you take a new photo or record a discussion video instead of selecting an existing item. Microphone access lets you record voice messages and the sound in recorded videos. Choosing media or finishing a recording can start an upload before you send the message or save the form. We receive the file and details such as its name, type and size to store, display or play it and operate the service. Our hosting and file-storage providers process these uploads. Visibility depends on the destination and its access settings: recipients may include other community members, message recipients, authorised moderators or staff, and visitors where content or assets are public. People who can access media may save their own copies. Uploaded media follows the retention and deletion rules below, including temporary uploads not yet attached to saved content and records retained for safety or legal obligations; cancelling a draft or revoking device permission is not a request to erase all uploaded copies.

Information embedded in media

Photos may contain embedded metadata, such as capture time, device details and GPS location. Videos and audio may also contain technical, time or location metadata. Depending on the file and device processing, this information may remain in the uploaded file and be available to people who can access or download it. We do not promise automatic removal of image metadata or video metadata. Remove sensitive metadata before uploading if you do not want to share it. Visible or audible details, such as faces, street signs or spoken addresses, can also identify people or places even if embedded metadata is absent.

Device location and community map locations

When you choose “Use my current location” to place a community map pin, Qumuna asks for foreground location permission and uses a current or recent device position. Coordinates may be precise, depending on your device settings and available accuracy. Qumuna does not access your device location in the background. You can instead enter an address or place name, select a search result, or adjust a map pin without granting device-location access. A community location is not necessarily your own position. Qumuna stores independently supplied location text and coordinates separately from Google selections. For Google selections, Qumuna stores a Google Place ID, not Google's returned coordinates, formatted address or address components. Google results are resolved when needed and used transiently, without a persistent results cache. Selecting or dragging a Google map pin does not turn Google's results into independently supplied location data. Saved location data and Place IDs remain with the community until edited, removed or deleted under the retention rules below. Community locations may be visible to members and, where listed publicly, to visitors on Discover and other public community pages. Viewing a Google map connects your browser or mobile app directly to Google, which receives your IP address, request metadata and requested map area. Address lookup, reverse lookup and Place ID resolution go through Qumuna's server to Google, sending the search text, coordinates or Place ID and requested language as applicable, even before you save a location. See Service providers, other recipients and contact below. Revoking location permission does not remove a saved community location or information already received by Google; edit the community location where you have permission, or contact us for help.

Age requirement

Qumuna is only for people aged 18 and over. We verify your age at sign-up and, for existing accounts, with a one-time confirmation. We store only your birth year as evidence of verification, never your full date of birth.

Your rights

You can request access, correction, export or erasure of your personal data, restriction of processing, or object to certain processing. You can also lodge a complaint with your local data protection authority. For self-service export, optional-data clearing and account deletion, sign in on the web at qumuna.com and open Settings → Privacy & data. Mobile Settings provides Delete account; use the website for export and optional-data clearing. Edit your profile to correct profile information. For other rights requests or if you cannot sign in, use the contact form at qumuna.com/contact or Contact Us in the mobile app.

Deleting your data

On the web at qumuna.com, Settings → Privacy & data lets you clear selected optional information, including your phone number, birth year, registered push devices, or name on past community memberships, while keeping your account. Clearing your birth year does not remove the age-verification record. You can also remove content you created where the relevant community controls allow it. Account deletion is available on that web page and in mobile Settings → Delete account. Choose account-only deletion, which leaves community content attributed to a former member, or account-and-data deletion, which additionally removes supported content and participation data where possible. Deletion does not erase every retained record: sealed identity records, agreement-acceptance evidence, and legally required billing/payment records may remain. See Data retention below. If you cannot sign in, submit a request through qumuna.com/contact or Contact Us in the mobile app.

Data retention

We keep your data for as long as your account is active. Sessions expire automatically, and deleted communities and content stay in trash for a limited grace period before permanent removal. When you clear community attribution or delete your account, we keep a sealed identity record for 24 months to meet legal and safety obligations, after which it is permanently erased. Billing and payment records are retained for as long as the law requires.

Newsletter mailing lists

Community administrators may import email addresses of external contacts to send their community newsletter, and must only import addresses whose owners consented. Every newsletter email contains an unsubscribe link; recipients can opt out with one click and can permanently delete their contact data (email address, name and send history) from the same page, without an account. Contact data is deleted when the community is deleted.

Exceptional confidential investigations

When Qumuna receives a credible report of suspected unlawful use or a verified request from a court or public authority, specially authorised staff may conduct a narrowly scoped, time-limited investigation. Content access requires independent senior approval, is read-only, and is recorded in a dedicated audit trail. We do not notify a community while doing so when notice is legally prohibited or would create a material safety or evidence-preservation risk. When notification is permitted after the investigation, only the community's active administrators receive an approved, redacted account of the outcome; raw evidence and internal notes are not disclosed automatically.

Service providers, other recipients and contact

OpenAI, through Replit AI Integrations, processes the optional Support assistant and Translate requests described under Optional AI features above. This is distinct from the staff reply-drafting workflow described below.

Qumuna uses Stripe for payments, Resend for service emails, Replit for application hosting, hosted PostgreSQL for database records, and Replit Object Storage, backed by Google Cloud Storage, for uploaded files. Our service providers are contractually required to protect personal data at least as well as this policy. If you choose Sign in with Apple or Sign in with Google, Apple or Google handles the sign-in and shares your account identifier and, as you allow, your name and email address with Qumuna. The mobile app checks Expo Updates for app updates, so Expo receives your device's IP address and request details such as platform and app version. In the iOS app, the Google Maps SDK collects diagnostics and usage data, which Google uses for analytics, not for tracking. For optional internal support reply drafting, authorised staff may send OpenAI, through Replit AI Integrations, a minimised case description assembled from fixed support labels, together with approved product knowledge and the requested language. This internal drafting workflow does not send raw case messages, internal notes, phone logs, safety cases, or other customers' case content; a person reviews the draft before sending it. When SMS delivery is configured and you request phone verification, Qumuna sends Twilio the destination phone number, sender number and verification-message text, including the code. When you enable mobile push notifications and register a device, Qumuna sends Expo Push Service its push token, notification title and text, and routing data such as notification, community and target identifiers and notification type, to deliver the notification to that device. Notification text may contain community or member content. Google provides maps and location lookup. Maps load directly from Google in your browser or mobile app, so Google receives your IP address, request metadata and requested map area. Qumuna's server sends lookup requests to Google with the entered address or place name, reverse-lookup coordinates, or a Place ID, and the requested language; Google receives the server's connection details for these requests, rather than a direct lookup request from your device. Device-location access requires permission, but map viewing and manually requested lookups do not require that permission and can send data before saving. Qumuna retains independently supplied location data and Google Place IDs separately; Google's resolved coordinates and addresses are used transiently, not stored as community location data or in a persistent results cache. If a community administrator configures Zapier or an outgoing webhook for a supported integration, Qumuna sends selected community events to the configured destination. Payloads include the event type and community identifier and, depending on the trigger, announcement title/body, event title/description/location/dates, poll question/type/deadline, author identifiers/names, or a member's identifier, name, role and joining/departure details; joining payloads may include email. These destinations are chosen by the community administrator, not automatically appointed as Qumuna service providers. Their handling of received data depends on that recipient and the community's setup. We do not sell your data. See our cookie policy for cookie details. For privacy questions or rights requests, use qumuna.com/contact or Contact Us in the mobile app.