Tacitum Privacy Policy

Last updated: 28 October 2026

Tacitum is a private messaging application operated by the Tacitum developer. Ordinary private messages, voice messages, and chat files are encrypted on your device before transmission. Account profiles, delivery metadata, and information you choose to submit in a report are handled separately as described below.

Data we process

We use this information to authenticate accounts, deliver messages and calls, display the profiles and groups you choose to share, synchronize devices, send service notifications, provide support, and prevent or investigate abuse. We do not sell personal data, use it for advertising, or combine it with other companies' app or website data for advertising tracking.

End-to-end encryption

The service stores and relays ordinary private-message and chat-file ciphertext without the keys needed to read that content. Encryption does not conceal the delivery and account metadata listed above. A recipient can save, copy, forward, or choose to report content that they can already view.

One-to-one voice calls use WebRTC with DTLS-SRTP. The service processes call signaling and connection metadata to connect the participants. That signaling is encrypted in server storage with a server-held key; it is not end-to-end encrypted from the service. A relay may carry encrypted audio packets when a direct connection is unavailable. Tacitum does not record or decode call audio.

Independent encrypted cloud space

SVIP members can upload images and other files from their device, save text or links, and optionally create encrypted chat-history snapshots. This personal storage allowance is separate from group-file space. File names, types, text, links and contents are encrypted on your device. The app shows the total allowance and usage, including encryption overhead and incomplete uploads.

The app encrypts cloud content with a random account-specific cloud key before upload. Your account password protects a copy of that key, allowing another device signed in to the same account to unlock it. An unlocked device stores the cloud key in its protected Keychain so you do not need to enter the password every time. The service stores the encrypted key wrapper and its salt, derivation parameters and revision, rather than a plaintext cloud key. Account passwords are transmitted over HTTPS for authentication; password-based cloud recovery therefore shares the security boundary of account authentication and does not offer the same isolation as a separate recovery secret. A normal password change updates the encrypted key wrapper together with the account password. After a forgotten-password reset, an already-unlocked device or the previous cloud password may still be needed to recover existing content; resetting a password does not erase cloud files. Earlier phrase-based cloud spaces can be linked to the account password from a device holding their key or after entering their original phrase once.

We store encrypted chunks and manifests, an encrypted key-verification record, public format and key identifiers, account and upload identifiers, ciphertext sizes and hashes, transfer progress and timestamps. Downloads do not depend on the original uploading device. Previews retrieve encrypted content and decrypt it on your device into temporary files, which the app removes when the preview closes or the account locks. Files you explicitly export to other apps or save to Files are controlled by those destinations.

Completed cloud items and history snapshots have no automatic expiry. Creating a new item does not overwrite or delete earlier items. Group-file expiry, membership expiry and storage limits do not automatically delete completed cloud items. When the allowance is full, new uploads stop until you make space. Losing SVIP prevents new uploads, while existing items remain available for download and manual deletion. You can explicitly delete an item, or request deletion of your account and associated cloud data. Uncommitted temporary upload chunks expire after 24 hours; this does not delete saved cloud items.

Optional chat-history snapshots include readable history cached on the current device and locally available downloaded attachments, up to the scope shown in the app. They do not automatically retrieve every past or undownloaded item; disappearing messages are excluded. Merging a history snapshot back into live chats uses online access checks and skips records that were recalled, cleared, expired or are no longer accessible. Separately uploaded cloud files, images, text and links do not depend on a chat or group remaining available.

Group files and group assistant

Group-file capacity and retention follow the group owner's current membership level. For ordinary owners, files expire after seven days. Files present when the rule first applies, including after an owner loses a qualifying membership, receive a transition period of at least seven days. Qualifying VIP and SVIP groups have larger allowances without that seven-day automatic file expiry; normal deletion, recall, disappearing-message and safety rules still apply. This policy does not delete personal cloud backups. The group-file screen shows the applicable allowance and expiry information.

Only group owners and administrators can operate the group assistant or send an everyone mention. Assistant notifications and scheduled reminders are encrypted and signed on the operator's device. The service stores ciphertext together with the group, operator, device, key epoch, scheduled time, delivery state and error reason. It cannot read the notification text. Tasks are rechecked at delivery and paused when relevant membership, keys or permissions change. Canceling a pending task removes its task ciphertext; non-pending task records are cleaned up after 30 days. Delivered messages follow the normal conversation rules. Mentioning members does not bypass their notification permissions or mute settings.

Device permissions and Apple services

You choose whether to allow camera access for QR scanning, photos for selecting pictures and media, microphone access for calls, voice messages and dictation, notifications for service alerts, and Face ID for app unlock and protected recovery-phrase access. Tacitum receives an authentication result from the system, not your Face ID biometric template.

Optional speech-to-text features use Apple's Speech framework. Depending on device and language support, audio may be sent to Apple for recognition when you choose dictation or transcription; those features do not always require on-device recognition. This processing is separate from encrypted message delivery. Apple Push Notification service processes notification tokens and notification payloads to deliver alerts. Apple's services are also subject to Apple's privacy policy.

Reports and safety

You can report messages, users, groups, group members, and files, and block abusive users. Ordinary encrypted messages are not automatically scanned or decrypted by the server. The report form lets you choose whether to submit the locally readable text offered as evidence. It does not upload a screenshot automatically. Report details and submitted text are deliberately shared with the service for manual review. Evidence text is encrypted in server storage with a server-held key and can be read by authorized reviewers.

Safety review may result in warnings, account restrictions or bans, and removal of reported messages or access to associated files. Restricting a stored file also prevents further downloads and forwarding through that storage reference. We cannot erase recipients' local copies or identify every separately re-encrypted and uploaded copy.

Account deletion

Request deletion at Me → Settings → Delete account. You have a 24-hour grace period in which you can cancel. After that period, a server cleanup task processes the request and deletes the account and its associated active-service profile, sessions, device and push-token registrations, encrypted backups, messages, and owned attachments. Deletion is processed by the service rather than at the exact second the grace period ends. Groups or conversations owned by a deleted account can also be removed with their server-side history.

Account deletion does not erase information another person has already saved or exported. Reports submitted for safety review, restricted-content references or isolated encrypted files, and the minimum associated object identifiers, reasons, administrative audit and security records may remain separately for abuse prevention, review, appeals or legal obligations. They are not restored as ordinary chat content or made available for normal file download.

Retention and security

Account and conversation data generally remain while you use the service, subject to deletion, recall, disappearing-message settings and safety actions. The service has no single automatic expiry period covering all security, support and moderation records. Contact us if you have a question about a retained record or want to request its review or deletion. Retention needed for an ongoing safety issue, dispute or legal obligation is considered separately from account deletion.

Access controls and administrative permissions limit access to service data. Report evidence and call signaling use server-side encryption at rest; ordinary private messages and chat files use the separate end-to-end encryption described above. These protections do not make all account or metadata records unreadable to the operator. Hosting and network infrastructure process data needed to run the service.

Your choices

You can edit or clear optional profile fields, change profile visibility, searchability, online and device visibility settings, block contacts, manage app permissions in system settings, and request account deletion. Hiding a field from other users does not remove the underlying service record. For access, correction, retention or deletion questions, contact us using the links below.

Contact

For privacy requests, account deletion questions, or safety reports, contact the Tacitum developer at dajid4495@gmail.com or visit Tacitum Support. Please provide your Tacitum ID when relevant, and never send a password, recovery phrase, or private encryption key.

Changes

We may update this policy when the service changes. The current version is always available at this URL.

Terms of Service · Support