DRAFT • NOVEMBER 14, 2026PHANTOM Privacy Policy
Version 2026-11-14-phantom-draft-1
Draft status & operator
DRAFT — development access only; not reviewed by counsel or approved for commercial launch. Operated by ISAAC MCCANE, Kentucky, United States. Contact isaacmccane2@gmail.com for privacy questions or requests. A business mailing address remains to be supplied.
What PHANTOM processes
Supabase processes your email, account identifier, password authentication, and sessions. PHANTOM stores your username, profile text and images, membership status, policy acceptance, posts, uploaded media, likes, comments, video views, messages, raid participation, activity events, badges, XP, notification subscriptions, settings, blocks, reports, and moderation logs. Foreground activity uses interaction checks and bounded server timestamps, not GPS, contacts, screen recording, or game telemetry.
Why & where
We use data to authenticate, maintain the private clan, deliver requested community features, prevent abuse, enforce permissions, and respond to requests. Cloudflare hosts the web app. Supabase provides authentication, database, realtime delivery, and private media storage. Push delivery uses browser and operating-system push providers. Provider infrastructure may process IP addresses and technical/security metadata. No advertising, payment processing, sale of personal data, or model training is implemented.
Who can see content
Approved members can see clan profiles, posts, videos, public chat, raid information, and activity rankings. Online and last-active visibility follow your settings. Private messages and their media are available through ordinary app tools only to participants. Turning off private messages prevents new incoming messages while retaining history. The Founder can moderate public content and membership, but cannot browse other members’ private conversations. A report deliberately shares the explanation you enter. Provider administrators may have operational access; this is not end-to-end encryption.
Notifications & device storage
Push requires your explicit device permission. You control categories in Settings and permissions in the operating system. Subscriptions include an endpoint and encryption keys; notifications avoid private message text but may identify the clan or sender. The browser stores your authentication session. The service worker caches public branding and an offline notice; it does not cache private community data. Sign out on shared devices. On supported iPhones, add the app to your Home Screen before enabling push.
Retention & requests
Clan records and uploads remain until deleted by their author, moderation, or an account request, except minimal records justified for security or legal reasons. Messages are retained for participants, including archived raid chats. There is no automatic expiration promise for community content. Failed push subscriptions are removed when identified; notification delivery queue entries are kept for operational diagnosis. Provider logs and backups follow configured retention and are not erased instantly. Contact the operator for verified access, export, correction, or deletion requests.
The FarmCommand transition
Existing Supabase accounts and passwords remain valid. PHANTOM clan records use separate database tables and a separate media bucket. FarmCommand game files, companion data, and older cloud records are not imported into clan feeds or deleted by this transition. Old product permissions do not confer clan Founder status. Any legacy-data request is handled separately through the operator.
Your controls
Edit your profile, hide online or last-active indicators, disable incoming private messages, block members, change notification categories, revoke device notification permission, manage sessions, or log out. Rights depend on applicable law. This draft does not claim all legal obligations are satisfied. Material collection/use changes require an updated notice and consent where appropriate.