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.

After a class a member checked in to has ended, the app may show a short “Class completed” card once. Power Zone records that the card has been shown for that member and class so it is not shown again; that record carries no attendance decision and grants nothing.

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, and a restricted server index of studio pass and membership records supports in-app booking eligibility as described below; Arketa remains the system of record for studio bookings, purchases and attendance.

Profile photo

A member may add a profile photo, either from their device's photo library or by taking one with the camera. The app crops it to a square and re-encodes it before it is sent; Power Zone's server then rebuilds the image again without embedded metadata and stores it in a private location under a random file name. The app is given only short-lived links to an image, never a file path, and no member can reach another member's image file.

A photo is optional, and it is used for showing the member on the app screens described under “What other members can see” below. Hide my photo in the app stops it being shown to other members from the next read onward, and Remove photo deletes the stored image. Authorized studio staff can review short-lived previews of reported photos and a current replacement for context, remove the reported photo, or dismiss a report. An old report cannot remove a replacement photo.

Before adding a photo a member agrees to the app's photo policy, and the version agreed to is recorded with the photo record. A member can report another member's photo from the leaderboard or a class attendee list; the report records who reported whom, the reason chosen, an optional note and which photo was on file at the time, is reviewed by studio staff, and is not disclosed to the member reported. A member can also choose not to see a particular member's photo; that choice is recorded and is not disclosed to the other member. Reports and these choices are deleted with either account.

What other members can see

Parts of the app show one member to another. Nothing in them reveals an email address, phone number, booking history, purchase, Power Points balance, or any studio identifier.

• The challenge leaderboard. Every linked member takes part in the studio's current race automatically; there is no joining or leaving it. A row shows a member's first name and last initial as held in the studio's client record, their initials or their profile photo where they have one and show it, their position, and how many recorded classes they have toward the target. Any linked member can see the board.
• The attendee list for a class. On a class a member is booked into, from the day before it starts until the end of that class's day at the studio, the app lists the seats taken in it: first name and last initial from the studio's own booking record, a photo where an app member has one and shows it, and whether the studio has checked that person in. Only a member holding a seat in that class, or recorded as having attended it, can see the list; anyone else is refused and learns nothing about the class.

Names shown to other members come from the studio's own client and booking records, and are the same details the studio's check-in screen shows at the door. A member who prefers not to appear with a picture can hide it or not add one.

Daily tasks

The Daily Tasks card on the app's home screen offers a short list of habits chosen by the studio. Which habits a member ticks stays on their own device and is not sent to Power Zone.

When every task for a day has been ticked, the app records that the day was completed: the date only, never which tasks or in what order, at most once per member per day at the studio's local date. It is recorded so the studio can recognize members who keep it up. Nothing about it is returned to the app, it affects no attendance record, class credit, challenge, streak, or Power Points, and only studio operators can see it.

Booking and cancellation requests

Where native booking or cancellation is available, Power Zone sends the requested reservation instruction to Arketa through its authenticated server integration. The server uses the linked studio client, class, reservation, and class-pack purchase identifiers needed for that request. Availability depends on the supported class and purchase; this policy does not mean every booking or cancellation can be made in the app.

Restricted server records include operator-reviewed class applicability and expected credit-effect metadata, account generation, review revisions and expiry, and a minimal operation record of the request, dispatch, acknowledgement, and independently checked outcome. These records support accurate status, recovery after interruptions, and prevention of duplicate external requests. They do not contain card credentials or copies of payment receipts.

Studio pass and membership index

To offer in-app booking with a pass or membership already held at the studio, Power Zone's server keeps a restricted index of Arketa purchase records. Because Arketa's integration does not allow looking up one member's purchases directly, the server synchronizes studio purchase records in bounded batches and then matches only the records belonging to the linked studio client of the member making a request.

The index is minimized to what entitlement checks need: the Arketa purchase, client and offering identifiers, the reported purchase type and status, an explicitly reported remaining-use count, start, end and renewal dates, subscription state indicators such as pause, scheduled-cancellation and whether a payment method is on file, and the provider update time. It does not store member names, email addresses, phone numbers, addresses, card or bank details, prices, invoices, payment receipts, or copies of Arketa responses.

The index is not visible to members or to ordinary studio staff, and the mobile app never receives Arketa purchase, client or offering identifiers. Before any booking is sent, the server re-checks the specific purchase directly with Arketa rather than relying on the stored copy. Arketa remains the system of record; deleting the Power Zone app account does not delete Arketa purchases, though the account's links to indexed purchases are removed.

Hosted Arketa booking and account screens

The app can display Power Zone's booking website and Arketa's hosted calendar or account pages inside an embedded browser. Arketa handles its own sign-in, memberships, pass selection, booking, cancellation options and checkout. Hosted pages and their payment providers may use cookies and browser storage to operate these services. Power Zone does not inspect or store hosted passwords, payment form entries, card numbers, security codes, bank details or payment tokens.

Arketa sign-in is separate from Power Zone app sign-in. Its embedded-browser session may remain signed in between visits and after Power Zone sign-out or app-account deletion. Sign out in Arketa before sharing your phone. Power Zone app authentication tokens are not passed into hosted pages. A browser handoff may be needed for a payment or authentication step; returning to the app does not prove booking or payment success. The app checks its trusted reservation service before showing a booking as confirmed.

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, the installation's app language, notification preferences, notification intent, and delivery ticket or receipt state. The app language lets Power Zone deliver notifications in the selected language. 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, or device timezone as part of push registration.

Language preferences

The app stores your app-language choice on your device. You can also choose a separate account email language for sign-in and email-change messages; that preference is stored with your authentication account. These preferences do not collect your device timezone or precise location.

QR camera and check-in information

Camera access for scanning is requested only after a member chooses to scan a studio class QR code. The scanner takes no pictures: the camera decodes the QR code on the device, and Power Zone does not record video or audio, upload camera frames, or keep camera images or frames from it. The decoded QR payload exists only long enough to submit the check-in or show a safe retry state, then is cleared. Adding a profile photo is a separate action a member chooses on purpose, and is described under “Profile photo” above.

The server records a limited QR check-in 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.

A scan can check a member in with the studio. While the studio has a check-in code in use, an accepted scan sends a check-in for that member's own reservation to Arketa — the same check-in the front desk would make — for a class the member already holds a seat in, and only within the short window around that class's start time. The studio can undo it exactly as it would undo a check-in made at the desk, and can stop the code working at any time. A check-in is still not attendance: recorded classes, class credits, challenge progress, streaks, milestones and Power Points continue to come only from Arketa's own records after the class, which remains 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. A profile photo is kept until the member removes it, or the account is deleted, or studio staff remove it. QR class sessions and member check-in 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; the profile photo record and the stored image file itself; the record of which days the member completed their daily tasks; the record of which class-completion cards have been shown; 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

When an app account leaves active status, unsubmitted reservation previews and member-associated purchase and cancellation reviews are removed. Operations that may already have been sent retain a pseudonymous target digest, generation, dispatch and outcome facts, and limited diagnostic and recovery state. Readable member, purchase and reservation bindings, display details, and member request identifiers are removed from those operation records. The retained replay protection is permanent in the current system so a new app account cannot repeat an earlier external request; no automatic purge period is promised.

Account deletion can stop an instruction that has not reached the dispatch boundary. An instruction already committed for possible transmission may still complete at Arketa. Deletion does not undo that instruction, cancel a studio reservation, return a class credit, or issue a refund. An unresolved detached operation requires restricted studio review; it is not resent automatically.

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.