FRAME

Privacy

Effective 15 September 2026

Data FRAME uses

Offline play stores settings, match progress, achievements, and a display name on your device. Online guests receive a random account identifier and expiring session token. Email accounts store the verified email address, display name, login times and device labels, synced progress, and server-verified online results.

Online games

The service stores room membership, display names, commands, table snapshots, connection times, and outcomes so it can enforce turns, recover games, and prevent duplicate commands. Opponents never receive your email address.

Player names, photos and career cards

You may choose a display name, select an earned title, and optionally select a photo. The app centre-crops and resizes it to a 128-pixel square before sharing. The server creates a new PNG from the resulting pixels; it does not receive the original file, filename, location tags or other image metadata. Only authenticated players in your match can retrieve these profile cards and photos. Offline photos remain on your device until shared in an online match. Career XP, levels, titles and milestones are device-reported; online win totals come from FRAME match results. Matches are not competitively ranked.

Remove a photo from Profile and save to delete the ordinary online copy. Server photos persist with the associated guest identity or account until removed, replaced, deleted or cleaned up under the service retention policy. A local device/account photo cache allows offline display. Verified-account deletion clears this app installation's account-photo cache; other installations may retain their own cached copy until local data is cleared. Profile reports can retain the reported name and normalized image for the support-review period (normally up to 30 days), even after a photo is replaced or an account is deleted. Block hides the opponent's profile photo and suppresses their chat. Already viewed images cannot be recalled from another person's device or screenshots. Backups follow the operator's published retention policy.

In-game chat

Optional text chat is shared with the other player in your online match after you accept the chat rules. The FRAME server stores message text, display name, sender seat, timestamps, delivery receipts, and your consent and blocked-player preferences. Normal history is limited to the latest 100 messages per match and removed after 24 hours by service maintenance. Support reports include the reported message and recent match-chat context, retained for up to 30 days for review. Moderation staff may review reported content; chat is not end-to-end encrypted. Server backups can retain older records according to the operator's published backup-retention schedule. Deleting a verified account removes its normal authored chat messages; relevant safety reports may remain for their limited review period. Block and Report are available from the chat panel. A guest's preferences belong to that guest identity, not permanently to the device.

Security and retention

Sign-in codes expire and are stored as hashes. Session tokens are stored as hashes on the server. Finished rooms and inactive records are deleted on bounded schedules described by the running service. Deleting an account removes its email, profile, login history, progress, and sessions; past room seats are anonymized where a room must remain briefly for the opponent.

Ads and consent

The Android app may request consent and show a Google Mobile Ads interstitial only after completed frames. Ads do not change XP, physics, access, or results. Google’s SDK may process device and ad data according to the consent choices shown in the app. Browser play does not load the native ad SDK.

Your choices

You can play offline without an account, decline or change ad consent where the platform offers it, sign out, avoid importing device progress, and delete a verified account from Profile or the public account-deletion page.

Publisher contact

The publisher’s verified legal identity and support contact must be configured on the public deployment and store listing before release. This source build does not invent them.