FRAME
Privacy Policy
Updated 3 October 2026
Data FRAME uses
Offline play stores settings, match progress, achievements, and a display name on your device. FRAME Run saves its unfinished run, recent layouts and personal best per player on this device; these scores are not uploaded or added to online rankings. Online guests receive a random account identifier and expiring session token. Google sign-in accounts store the Google account identifier, verified email address, FRAME display name, login times and device labels, synced progress, and server-verified online results. Google verifies your identity; it does not provide FRAME a verified age through sign-in. FRAME does not import your Google real name or profile photo into the game. A neutral age screen assigns the saved age group; the date of birth is not retained. Existing linked accounts restore their own saved age group. When email signup is available, you can also create an account with an email address and password. Email signup and password reset are hidden when email delivery is not configured; Google sign-in and guest play remain available. We verify control of the email address before creating an email account. FRAME stores the verified email address and a salted, slow password hash, never a readable password. Existing accounts keep their player identity, progress and saved age group when a verified email is used to reset or add a password. Older email-account data is retained until recovered or deleted. Google processes sign-in requests under its own privacy policy.
Age groups and remembered players
For online age screening, the app sends the entered date of birth to the FRAME service, which processes it transiently to determine an age group; FRAME does not retain the full date. The group is stored with the player identity. Under-13 players cannot enter online play. Teen players receive protected names and avatars and cannot use text chat or custom shared profiles. Chat and custom match profiles require both participants to be adults. A remembered guest uses a random device credential; the service stores its hash, associated guest identity and age group. Remembered access expires after 365 days of inactivity. Returning to a remembered guest renews this period. Losing device data can lose access to that guest. Age is self-declared, and signing into someone else's account does not establish the current user's age.
Beat My Shot and voluntary sharing
All five shot challenges are playable offline. Your best result is stored on this device and the most recent shot replay stays in memory during the session. Creating or exporting a shared challenge requires an authenticated player recorded as an adult. For a completed run, FRAME sends the challenge identifier and up to three shot settings to its own service, which replays the physics to calculate the result. Raw shot settings are not retained in the share record.
The service stores a random challenge code, fixed challenge identifier, result, attempt count, creation and expiry times, a deduplication hash and the owning player identifier. Public invitations disclose only the fixed game board, result, attempt count, expiry and code. They contain no player name, photo, chat, email or Instagram account. Anyone with the link can view the invitation. Links expire after seven days; periodic maintenance removes expired records. The owner can remove active links in Beat My Shot → My shared links. Account deletion or a more restrictive recorded age makes associated invitations unavailable. Creation timestamps used for share limits are retained for up to 24 hours; security records and recovery copies follow the retention terms below. Aggregate counts of shared runs and successful shared runs may remain without player identifiers; these are not counts of unique people or Instagram shares.
Share card opens your device's sharing menu. Save card opens a document location chosen by you. Copy challenge link writes only the public invitation URL to the clipboard. FRAME does not sign into Instagram, read followers or contacts, or post automatically. You choose whether and where to send the exported image or link. The selected app or storage provider receives the image or link and applies its own privacy terms. Copies already saved, posted or forwarded cannot be recalled by removing a FRAME link. Native temporary card files become inaccessible through FRAME's image provider after 24 hours and are cleaned during later exports or device cache cleanup. The feature does not reward follows, shares, ad views or ad clicks.
Shot collection, coaching and private crews
Shot Coach and mirrored practice use the game's physics locally. Cosmetic styles and original-board bests are saved per player on this device and do not change physics. Anonymous browser practice does not require sign-in or submit results. Resolving an invitation makes a request to the FRAME service; ordinary server access logs may record that request.
Crews require age-screened online access. Each private crew has up to four players from the same age group (teen or adult), shown with preset player labels. Members see weekly board status and points. There are no crew names, photos, free-text messages or public listings. The server stores membership identifiers, age group, invite and expiry, weekly run identifiers, deadlines, verified results and input hashes. Raw shot inputs are replayed transiently; the device may retain up to three current run inputs for recovery. Crew results are kept for the current and previous UTC week; crews expire after 30 days without creation, membership, invite or scored-run activity. Server maintenance removes expired records. Leaving removes you and your points from that crew; used runs remain tied to your player for the week. Account deletion removes associated memberships and runs. Private recovery copies follow the Recovery backups section below.
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. Private recovery copies follow the Recovery backups section below.
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. Private recovery copies follow the Recovery backups section below. 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
Google sign-in uses a short-lived, one-use server nonce and server verification of Google tokens. A pending account-setup ticket expires after five minutes. Google ID tokens are not persisted by FRAME. Session tokens are stored as hashes on the server. Email verification and password-reset codes expire after ten minutes, are limited to five guesses, and are accepted only once. Pending code checks and account-setup tickets are kept in server memory and removed on expiry or server restart; they are not written to database recovery snapshots. Password hashes remain until replaced or the account is deleted. A password reset revokes all existing account sessions. FRAME does not store passwords or verification codes in device storage. Finished rooms are removed after seven days, and no more than the 100 most recent finished rooms are retained. Abandoned waiting rooms are removed after 24 hours. Periodic maintenance removes expired records. Persistent login-attempt rate-limit entries expire after their 15-minute window; session hashes expire after 30 days or earlier revocation. Account data, including up to 50 recent login records, remains until the account is deleted. Guest age memory has the inactivity period described above. Deleting an account removes its email, password hash, pending email requests, profile, login history, progress, and sessions; past room seats are anonymized where a room must remain briefly for the opponent.
Recovery backups
FRAME keeps private copies of its account and game database for recovery after a failed update. Managed database snapshots on the FRAME server expire 30 days after their snapshot timestamp. A daily cleanup removes expired copies, normally within a further 24 hours while the server is running. This can retain a pre-deletion copy for up to 31 days. These copies are restricted to server administrators and are not used for advertising or routine gameplay. Interrupted cleanup is resumed when the server is available.
This schedule covers FRAME-managed database recovery files. It does not control copies a player has exported, Google's records, or independently created hosting snapshots and administrator exports. Contact support about any additional recovery copies or a deletion request. Security or legal records are retained only for the relevant investigation or obligation; support will explain any applicable exception.
Email delivery
When email signup and recovery are enabled, FRAME uses Resend to send verification and password-reset emails. These options are unavailable when email delivery has not been configured. The provider receives the destination email address, sender address, message and one-time code to deliver the requested email. Passwords are never sent to the email provider. Resend processes delivery and security records under its privacy policy. Delivery-provider records are separate from FRAME database backups; contact the publisher about deletion requests.
Ads, service providers and diagnostics
The Android release includes Google Mobile Ads and Google's consent SDK. When enabled, the ads SDK can collect and share IP addresses (which may indicate approximate location), interactions with the app and ads, diagnostic/performance information, and device or account identifiers such as the advertising ID and app set ID. Google uses this information to deliver and measure ads, analyse performance and prevent fraud. Consent controls affect applicable ad processing. Declining personalised ads does not necessarily stop all SDK data collection. Google applies its own privacy policy and advertising information.
FRAME does not request GPS or precise device location. Its server receives network IP addresses for connection handling and abuse prevention. Hosting services process requests and operational logs to run and secure FRAME. Network data is sent over HTTPS. FRAME's own Android crash report is stored locally on the device; it is not automatically uploaded by FRAME. SDK diagnostics are separate.
App-initiated ad requests require an eligible adult session and the consent SDK allowing ads. Interstitials are requested after completed frames, not during a shot. Browser play does not load the native ads SDK. Beat My Shot gameplay, share-card export and FRAME Run rounds do not trigger interstitials. Ads do not change physics, XP or results.
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
This policy applies to FRAME: 8 Ball Pool (Android package com.permal.framepool). For privacy questions, support, corrections or deletion requests, contact the FRAME publisher at bhupesh1897@gmail.com.