Privacy Policy

Last updated: 15 October 2026

Park Vitals shows the people who run a family entertainment center their own operating numbers on their phone. This policy explains what we hold, why, and what you can ask us to do about it.

What we collect

• Your name and mobile number. The number is your login: we text a six-digit code to it each time you sign in. There is no password.
• An email address for billing receipts, given when a company subscribes. It is never used to sign in.
• Your company and its parks: the business name, each park's name, its time zone, and its address or ZIP code.
• Keys to the systems you connect. The credentials you enter for your point-of-sale and scheduling platforms. They are encrypted before they are stored, are never shown again once saved, and are used only to read your own data.
• The operating figures those systems return: sales, admissions, bookings, memberships, menu sales, schedules and labor. We keep a copy so the app is fast and so long-range totals do not have to be rebuilt each day.
• Billing records: which parks a company has bought and the status of each purchase. Card details go directly to Stripe. We never see or store a card number.
• Server logs: which request was made and when. They do not contain your figures, your credentials, or the contents of any message.

What we do not collect

No advertising identifiers, no tracking across other apps or sites, no analytics profile of you, and nothing about your guests as individuals beyond the name and photo Google shows beside a public review (see Google account data). We do not sell data, and we do not use it for advertising.

How we use it

To run the service and nothing else: signing you in, showing your figures, billing your company, sending the account notices described below, and answering your support requests. Your park's data is used to serve your company. It is never pooled with other companies' data or shared with them.

Text messages

We text sign-in codes and account notices to the number on your account. Message and data rates may apply. Reply STOP to opt out; you will not be able to sign in until you opt back in, because the code is how signing in works.

Who else sees it

• Railway hosts our servers and database.
• Twilio delivers the text messages.
• Stripe takes payments and holds the card details we never see.
• Open-Meteo returns the local forecast. It receives a park's coordinates and nothing else.
• Google provides a park's Google reviews, as described under Google account data.
• Slack, if your company connects its own Slack workspace. Park Vitals then posts only the kinds of post your company switches on, each to the channel your company chooses for it, and only to your own workspace. Depending on which are on, a post can contain: the names, roles and shift times of the employees scheduled that day and the day's total scheduled hours; the name, role and shift of someone who hasn't clocked in for a shift (or, when no one has clocked in at all, a notice that names nobody); the name and weekly hours of someone nearing overtime; each party's booking name, package, guest count and balance still owed; park totals such as sales, labor as a percentage of sales, memberships sold and the number of members with a declined payment (a count only, never who); new Google reviews of the park: for a park that has connected its Google Business Profile, the star rating, the reviewer's first name, what they wrote and a link to it on Google; for any other park, only the star rating and a link to the review on Google Maps; guest survey responses at or below a rating your company picks, with the guest's comment posted as the guest wrote it, and nothing added that identifies the guest; and a notice when a connection to your point-of-sale or scheduling system stops working. Never pay rates, labor costs per person, or card details. We keep the access token Slack issues (encrypted at rest), the workspace's and each chosen channel's name and identifier, each park's choices, and a record of each post (when it went out, to which channel, and a count or figure it reported) for 90 days. Disconnecting Slack in the console, or removing the Park Vitals app from your workspace, stops the posts and deletes the token. Posts already in Slack are messages in your company's own workspace: they stay there after you disconnect, and after an underlying review or survey is deleted at its source, until someone in your workspace deletes them.
• The systems you connect to your parks, which we only ever read from.

Each receives only what it needs for its part. We may also disclose information if the law requires it.

Nothing is written back

Park Vitals only reads from the systems you connect. It never creates, changes or deletes anything in your point-of-sale, your schedule or your Google listing. The one thing it writes anywhere is its posts to Slack, when your company turns them on, and only to the channels it picked.

Google account data

A park can connect its Google Business Profile so its dashboard shows every Google review, newest first. Only someone who manages the park's Google listing can do this, by signing in with Google from the Park Vitals console. This section covers what we receive from Google when they do.

• What we ask Google for: permission to manage the Google Business Profiles the connecting Google account administers (the business.manage scope), and that account's email address.
• What we use it for: reading the park's Google reviews (the rating, the review text, the reviewer's name and photo, the dates, and any replies) to show them on that park's dashboard, to text the park's administrators when a new low rating arrives, and, only if the park's company switches on Slack review posts, to post each new review (its rating, the reviewer's first name, what they wrote and a link to it on Google) to the channel in the company's own Slack workspace that the company picked. Nothing else. We read nothing beyond the listing's reviews and its basic details, its name and address, and today Park Vitals does not post, edit or reply to anything on the account's behalf.
• What we store: the sign-in token Google issues, encrypted at rest on our servers; the reviews, so the dashboard can show them; and the connecting account's email address, to show who connected the park.
• Who sees it: people with access to that park in Park Vitals, and, if the park's company switches on Slack review posts, the members of the Slack channel it picked for them. It is transferred to Slack only at your company's direction, to provide this feature. We do not sell it, or use it for advertising or to build profiles of anyone. A review already posted to Slack stays in your company's workspace after the park disconnects Google or Slack, and after Google deletes the review, until someone in the workspace deletes the post.
• How long we keep it: until the park disconnects Google in the console, which promptly deletes the token, the stored reviews, the connecting account's email address and the chosen listing. If instead the account removes Park Vitals' access at myaccount.google.com/permissions, or that access expires, the token and the stored reviews are deleted promptly, but we keep the connecting account's email address and the chosen listing so the park can be offered a reconnect; both are removed when the park disconnects in the console. Reviews that Google no longer returns, such as ones their authors have deleted, are removed from Park Vitals within a day.

Park Vitals' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Parks that have not connected a Google Business Profile can still show Google reviews. Those come from Google's public Places API, are Google's content, and are credited to Google on the card that shows them. No Google sign-in or Google account data is involved.

How it is protected

Traffic is encrypted in transit. The credentials for your connected systems are encrypted at rest with a key held separately from the database. Sign-in codes expire in ten minutes and are deleted within a day. Access is limited to the people who need it to run and support the service.

How long we keep it

We keep your company's account and figures while the account exists, including after a subscription ends, so that nothing is lost if you come back. Ask us to delete it and we will. Sign-in codes are deleted within a day of being issued. Server logs are kept by our hosting provider for a limited period, currently about thirty days.

Your choices

• See or correct your details in the app, or ask your company's administrator.
• Delete your account: your company's administrator can remove you, which takes effect immediately, or write to us and we will do it.
• Delete the whole company: an administrator can ask us, and we will remove the company, its people and its data.
• Stop the texts by replying STOP.

Children

Park Vitals is a tool for people who work at a park. It is not directed at children and we do not knowingly collect anything from them.

Changes

If this policy changes we will update the date at the top, and tell account administrators if the change is a significant one.

Contact

Write to hello@parkvitals.com with any question about this policy or any request above.