FiterationPrivacy policy
This policy explains what information Beacon holds, why it holds it, and who helps us process it. Beacon is made by Fiteration LLC ("we").
Who is responsible
Your studio decides what information goes into Beacon and why. The studio is the controller of its members' information. We process that information on the studio's behalf, and only to run the service for that studio.
What we hold
- Contact details, such as name, email address and phone number.
- Membership, attendance and billing records from the studio's booking system.
- Coach notes, which can include health-related information such as injuries and limitations.
- Nutrition logs and meal photos.
- Exercise data, such as lifts and training history.
- Sign-in details for studio staff.
Who processes it with us
- Amazon Web Services hosts the service and stores its data.
- WorkOS handles sign-in.
- MindBody is the studio's booking system. We read membership, class, attendance and billing records from it. For the studio, we also write bookings, check-outs and one-off changes to it, such as cancelling or moving an appointment.
- Anthropic provides the AI features.
- PostHog provides product analytics for the studio dashboard, the coaches' floor app and the member app: which screens and tools people use, where they click and how far they scroll, and recordings of sessions in the apps. We send PostHog no personal information. A recording shows how each screen is laid out and where people tap. Every word on the screen and everything typed is hidden, and a tap is recorded without the words of what was tapped. Web addresses are sent without their search terms or other details. Injuries, InBody results, the member app's nutrition screen, private health details and the coaches' PIN pad are never recorded. PostHog knows staff and members only by an internal id, never by name or email. PostHog does not keep IP addresses. It runs in PostHog's US cloud. In the member phone app, PostHog receives only crash and error reports: what kind of error, where in the app, and the app's version. A report's message is left out unless it comes from the app's own code checks, and email addresses, phone numbers and web-address details are taken out first. A report is linked to the member's internal id once they are signed in. The phone app's demo sends nothing.
- GoHighLevel is the studio's own CRM, when the studio connects it. We read the studio's contacts and conversations from it to show them to the studio. We also write a few updates to it. These are appointment results, our own tags, two custom fields, opportunities, and partner introduction contacts and emails.
- Slack is the studio's own team chat, when the studio connects it. We post studio notices, coach shift posts and milestone posts into the studio's own Slack workspace, using the studio's token. These posts can name members and coaches.
- Snowflake holds the franchisor's data lake, in AWS us-west-2. Members appear in it only under a pseudonym, and it holds no health information. Staff appear by name. Snowflake Cortex Analyst answers the franchisor's questions over it.
AI features
Member information is processed by Anthropic for the AI features: a coach's note, a meal photo or similar member information is sent to Anthropic to produce a written note or an analysis. The studio decides whether AI features are on for its members. Snowflake Cortex Analyst answers the franchisor's questions over the pseudonymized data lake described above.
Using Beacon from Claude
A studio can let its owners and managers connect Beacon to their own Claude account. It is off until the studio turns it on. When it is on, a person who connects asks Claude questions, and Beacon answers with the same information that person can already see in Beacon — for example members' names, membership status, attendance and schedules. Those answers go to that person's own Claude account and are handled under their agreement with Anthropic. Injury, limitation and other care notes are left out unless the studio separately turns them on. Beacon records each question asked (who asked and when, not the answer). The connector can only read; it cannot change anything in Beacon.
How long we keep it
We keep a studio's information for as long as the studio uses the service, and delete it after the studio leaves unless the law requires us to keep it longer.
Seeing or deleting your information
You can ask to see the information held about you, or ask for it to be deleted. Write to your studio, or to us, and we will work with your studio to answer.
Where we are
Fiteration LLC is based in Arizona. This policy is governed by the laws of the State of Arizona. If we change it, we will post the new version on this page.