Privacy,
plainly explained.

Adult audience

The Power Zone app is intended for adults aged 18 and older. It is not directed to children.

Account, authentication, and studio linking

Supabase Auth processes the email address used to request a six-digit sign-in code, authentication identifiers, session information, and sign-in timestamps. The Power Zone app profile stores first and last name, app-account status, and studio-link status. App authentication sessions are stored on the device using operating-system secure storage.

Server-side linking associates an eligible app account with its Arketa studio client record. Private linking data may include an Arketa client identifier and a keyed, versioned digest of a normalized email address. A digest is pseudonymous, not anonymous: Power Zone's restricted systems may use it to recognize the same underlying member for linking and replay prevention even though it is not stored as readable email text in the app database.

Attendance, activity, and app features

The app processes a Power Zone copy of recorded attendance derived from Arketa, including the relevant class occurrence and confirmation state. It derives member-facing totals, streaks, milestones, attendance insights, weekly-goal progress, and challenge progress from that information.

Depending on the features used, app data also includes challenge enrollment, favorite instructors, a weekly attendance goal, referral codes and attribution, Power Points ledger entries and displayed balance, reward-redemption requests and outcomes, and notification preferences. Current class schedules and member booking information are requested through Power Zone's server integration with Arketa; Arketa remains the system of record for studio bookings and attendance.

Installation and push-notification information

If notifications are enabled, the app uses a randomly generated installation identifier, platform type, Expo push token, token-registration timestamps and status, notification preferences, notification intent, and delivery ticket or receipt state. The installation identifier is not derived from an email, hardware serial, advertising identifier, or device fingerprint. The current app implementation does not store device name or model, operating-system version, advertising identifiers, precise or coarse location, contacts, locale, or device timezone as part of push registration.

QR camera and check-in information

Camera access is requested only after a member chooses to scan a studio class QR code. The camera decodes QR data locally. Power Zone does not take photographs, record video or audio, upload camera frames, or persist camera images or frames. The decoded QR payload exists only long enough to submit the check-in or show a safe retry state, then is cleared.

The server records a limited QR presence receipt, trusted receive time, and private class binding. It stores a digest rather than the raw rotating QR token. QR check-in does not collect GPS, Wi-Fi, or Bluetooth information and does not replace Arketa as the attendance authority.

App-account deletion web service

The secure deletion page processes the account email and six-digit verification code through same-origin POST requests. After successful verification, it uses a short-lived authentication cookie and a separate recovery cookie. Both are unavailable to browser scripts, use strict same-site handling, and are limited to the deletion API path. The authentication cookie lasts no more than nine minutes; the recovery cookie lasts for the browser session unless the flow clears it sooner.

A non-credential browser-session marker records only that a deletion request was submitted so a reload can return to status checking. Emails, verification codes, authentication sessions, and recovery credentials are not placed in URLs, chatbot messages, or deletion-flow analytics. The deletion route does not load the site chatbot.

Support communications

If a person contacts app support, Power Zone processes the contact details, message, and troubleshooting information that person chooses to provide. This may include the affected screen, device type or model, operating-system version, app version, approximate incident time, short error text, and a cropped or redacted screenshot.

Do not send passwords, email verification codes, authentication or recovery tokens, or full screenshots containing sensitive personal or payment information.

While the app account is active

Power Zone keeps account and app-feature information while it supports the active app account and the features described above. QR class sessions and member presence receipts are subject to implemented housekeeping through 30 days after the class starts; deleting an app account removes its member QR receipt earlier. Push routing identifiers remain only while useful for an eligible installation and are disabled or removed through permission, sign-out, stale-device, provider-error, and account-deletion handling.

Support communications are kept as needed to handle and follow up on the inquiry. This policy does not represent a fixed automatic deletion schedule for support mail.

What app-account deletion removes

A completed request hard-deletes the Supabase Auth user, identities, and refresh sessions; the app profile and name; the current app-to-Arketa link; the Power Zone attendance copy; challenge enrollment; favorite instructors; weekly goal; notification preferences; push devices and unsent notification work; member QR receipts; referral code; and ordinary member rate-limit rows. The app clears its local authenticated resources and session.

Deletion does not cancel or erase Arketa-managed studio services or records. Shared class, instructor, catalog, and aggregate operational records that do not identify the member are not app-account data and remain.

Limited records retained after deletion

Power Zone retains a narrow Power Points ledger, reward-redemption records, referral attribution and closure records, an already-frozen challenge-reward decision until its existing batch settles, a durable member identity, the closed app-account identifier and state, and deletion-request/recovery records. These records support current product accounting, fulfillment or cancellation, recovery from an interrupted deletion, and prevention of duplicate claims, awards, redemptions, refunds, or other one-time outcomes.

Retained durable identifiers may include a random private identifier, an Arketa client identifier when known, or a versioned keyed email digest while a pre-link fact still depends on it. They are pseudonymous, not anonymous, because restricted server processes can recognize the same underlying member. They do not restore the deleted profile, app history, preferences, or sign-in.

An already-frozen challenge decision remains only until its finalization batch settles or is invalidated. A pending redemption may still be fulfilled or cancelled after account deletion. Recording that outcome ends its pending status; it does not automatically delete the redemption or associated ledger records. Those records remain subject to the retention purposes and conditions described below. Other retained business, anti-replay, closed-account, and terminal deletion-request records currently use the documented purpose and related-record conditions rather than a fixed number of years. The current system does not apply an automatic terminal purge schedule to those record classes, so this policy does not promise one.

Power Points, redemptions, and re-registration

Any unused Power Points will no longer be available and will not return if a member creates a new app account. Power Points are non-cash loyalty units and cannot be cashed out. The historical ledger remains detached for accounting and duplicate-outcome integrity and is not displayed or spendable by a new account.

A pending reward request is not canceled by deleting the app account. Power Zone may still complete or cancel it using limited retained fulfillment records. Any outcome remains attached to the closed account and does not create usable points in a new account.

Re-registering with the same verified email creates a fresh app-account generation, not a restoration. The new account begins with no restored app preferences or history and zero usable prior Power Points. Normal studio linking may associate it with the same Arketa client, while the durable identity continues to prevent duplicate one-time outcomes.

Notifications already in delivery

Account deletion immediately fences new notification handoffs and suppresses unsent work. A notification already handed to Expo, the device-platform provider, or the device cannot be recalled. It may settle once, but it is not eligible for a new or retry delivery after the deletion fence.