Privacy policy

Effective 11 October 2026. Tap Folk is operated by 2G Solution LLC. Contact support@2-g.net.

No accounts

Tap Folk does not ask for an account, email address, phone number, contacts or a public profile. A private invitation creates a temporary conversation for exactly two participants. There are no advertising or analytics SDKs in this application.

Conversation content

Messages, attachment names, file keys and files are encrypted on the participants’ devices. The relay processes encrypted packets and cannot decrypt ordinary conversation content. The invitation includes a secret in its link fragment; share it only with the intended person. Network transport uses HTTPS.

Data the service processes

The service processes network addresses and request times to route requests and limit abuse. Short-lived keyed digests are used for application rate limits. It also processes random conversation identifiers, capabilities, timing, status, packet sizes and ciphertext. Standard hosting access and error logs can include network addresses, request URLs, browser identifiers, times and response codes; these are separate from conversation storage and follow hosting operational retention. Tap Folk does not collect precise or approximate device location, request location permissions or provide live-location sharing. Application security metadata is used for routing and abuse prevention, not location tracking. We do not claim that all network metadata is erased when a conversation ends.

Retention and deletion

Invitations expire after 15 minutes. A pending reservation or encryption handshake has a 60-second deadline. Conversations last at most 24 hours. When one person ends, further chat stops and a five-minute closing deadline applies; when both finish, the relay removes the conversation and its packets. End and block requests immediate deletion. Devices clear the application’s session content when ending, blocking or expiry is handled. Closing the application does not provide conversation recovery.

Production conversation databases and journals use dedicated volatile, non-swappable RAM storage outside cPanel file backups. Application records are removed by requests and scheduled cleanup. A server reboot loses this storage. We cannot erase copies independently saved by a participant, invitation copies in another service, screenshots, operating-system copies or network-provider metadata.

Deletion requests for voluntarily submitted reports and identifiable operational data can be made through Support. A report receipt is required to verify control. Security or legal retention requirements can limit removal of operational records; conversation deletion does not remove independently saved copies.

Attachments

The receiver must accept an encrypted file offer before transfer begins. Supported files are JPEG, PNG, WebP, supported H.264 MP4 video, PDF and app-recorded disguised WAV voice messages, subject to validation and size limits. Previews use application memory and do not automatically save received files. Images are normalized to remove supported metadata; video and PDF can retain metadata. Validation is not a malware-scanning guarantee.

Voice messages and emoji

Microphone access is requested only when you choose to record a voice message. Recording is limited to 60 seconds and processed in application memory. The app changes the pitch locally and lets you preview the transformed recording before sending. Only the transformed, canonical WAV is offered for encrypted delivery. The original recording is discarded by the app and is not sent to the relay. Pitch effects do not guarantee voice anonymity. Discarding, ending the conversation or leaving the active app cancels the recording. Emoji selection does not keep a persistent recent-use history.

Individual deletion and replies

You can select multiple entries and remove them from your current app view. You can also request removal of your own entries from both participants’ app views; this requires encrypted delivery to the peer. Entries disappear without a deleted-message placeholder. Reply previews resolve the original entry in the current conversation, so removing that original also removes its reply preview. Removing an individual entry does not prove immediate erasure of encrypted relay packets or copies already saved or captured by a peer.

Screen capture protection

Android uses the operating system secure-window flag for screenshots and screen recording. iPhone hides private content during detected screen recording, mirroring and app inactivity, and pauses private media. Supported iOS APIs cannot guarantee prevention of a still screenshot. Browsers and macOS do not provide equivalent guaranteed screenshot prevention. These measures cannot prevent external cameras or a modified device.

Voluntary safety reports

A participant can choose a reason and up to ten text messages, then explicitly consent to share that selected readable content with 2G Solution LLC for review. This report is separate from end-to-end encrypted conversation delivery. Reports are encrypted at rest, kept up to 14 days, and can be lost earlier on server reboot. Reporting does not give us the rest of the conversation or attachments. Keep the report reference when contacting support.

Your choices and limits

You can decline a file, cancel transfer, end and block, or contact support about a report. There is no account to delete. A peer can capture content, and managed runtimes or media decoders can retain copies outside application control. Compare the safety fingerprint through a separate trusted channel before sharing information.

Security status and changes

This release is undergoing security and platform acceptance validation. It has not completed an independent cryptographic audit. Avoid sensitive use during validation. We will update this page when data practices change.