© 2026 Vital Dash LLC·Real ROAS™, Real RISK™, and Real WIN™ are trademarks of Vital Dash LLC.·v-df94abf·Trust & Security·Privacy·Terms·Built 21Nov2026 00:39
TVS Dash
TVS Dash

Trust & Security

Sign in

TVS Dash

Trust & Security

TVS Dash uses customer, member, lead, workforce, financial, and wellness-related information to provide dashboards and reports. Viewing studio and lead data requires Google sign-in. Account roles and database safeguards limit which information each person can access. Details about AI features, outside services, data handling, and retention are below.

Last reviewed October 18, 2026

  • Assurance status
  • AI features
  • Authentication
  • Roles and data access
  • Administrator access and impersonation
  • Audit and activity logging
  • Database security
  • Backups and availability
  • Application and network protections
  • Change management
  • Incident response
  • Development environment
  • Franchisee offboarding
  • Hosting and infrastructure
  • Data use and lifecycle
  • Outbound data and payments
  • Privacy and data requests
  • Reporting a vulnerability
  • Third-party services

Assurance status

This page describes selected TVS Dash practices and is not an independent assurance report.

Independent assurance
This page is not a SOC 2 report, certification, or independent audit opinion. It describes selected controls and service practices and does not establish that every control has been independently tested.

AI features

Some pages use AI to create summaries or answer questions through the Dash Agent.

Provider
Google Gemini is the only AI provider. Requests and responses are processed through The Vital Stretch's paid Google account. They are not public or visible to other Google customers.
Model training
Google does not use prompts or responses sent through the paid Gemini API to train or improve its models.
Data retention
Google has approved a zero-retention setting for the TVS Gemini project. Google does not keep prompts or responses after returning a response.
Data sent
AI features generally use combined totals rather than information about individual members. If a user asks Dash Agent about specific members, it sends information about those members. AI Profile Summaries send a member's SOAP notes to create the summary. Executive Report insights use combined totals and are created only when a user opens the insights panel.
Access scope
AI features use the signed-in user's access permissions. Dash Agent only returns information that user is allowed to see.
Dash Agent conversations
Only the person who starts a Dash Agent conversation can see it.
Controls
Each AI feature can be turned off by an administrator.

Authentication

A signed-in account is required to view studio, lead, or network data. Software integrations use separate API keys.

Google sign-in
Google OAuth is required in both production and development. There is no username and password sign-in and no separate local account.
Information requested at sign-in
Google sign-in requests only your basic account details: name, email address, and profile information.
Approved accounts
Only approved accounts can sign in. Other Google accounts are rejected at sign-in.
Disabled accounts
A disabled account loses access to data promptly, without waiting for its session to expire.
Sessions
Sessions expire automatically. Session tokens are encrypted and stored in a browser cookie that scripts on the page cannot read.
Service integration keys
Software integrations use issued API keys instead of a person signing in. TVS Dash stores a protected hash of each key, not the full key, so the original cannot be recovered from storage. Each request checks that the key is active, allowed to use that feature, and within its request limits.

Roles and data access

Each account has one role. Its role and assigned studios and ad campaigns determine which information it can see.

Administrator
Platform administration, including user management, integrations, and impersonation. The Administrator role is separate from the Franchisor role.
Franchisor
Access to data across all franchisees and studios.
Franchisee and Studio
Access only to the studios and ad campaigns assigned to the account. An account with no assignments has no studio or campaign data.
Server-side enforcement
The server checks permissions for every request. The database also limits results to assigned studios, so an account cannot get data for a studio it was not assigned.
Access changes
Changes to roles, assignments, or account access are recorded in an audit log, along with the administrator who made each change.

Administrator access and impersonation

Impersonation lets an administrator view TVS Dash with another user's access.

Who can impersonate
Only administrators, and only accounts that are enabled.
Permissions applied
During this session, the administrator sees only the data and features available to that user, based on their role and assignments.
Franchisee view mode
Administrators can limit their view to the studios and campaigns assigned to their own account. This narrows the data they can see but does not change their role.

Audit and activity logging

TVS Dash records account activity and administrative changes.

Impersonation events
Separate log entries record when an administrator starts and stops impersonating a user. These entries cannot be changed or deleted.
Page and API activity
Logs record page views and requests, including the user, role, page or feature, studio, and result. Activity during impersonation is also linked to the administrator.
Request IDs
Each request has an ID that helps administrators find its details in the application logs.
Billing changes
Changes to billing plans, invoices, and billable hours are recorded in an audit log.
Log retention
Application logs are retained for 30 days.

Database security

Studio, lead, and customer data is stored in a managed database on Google Cloud.

Database access checks
The database checks each request against the signed-in user's permissions and, when applicable, the user being impersonated. These checks prevent a request from returning information outside its allowed scope.
Encryption at rest
The database encrypts stored data, backups, and logs at rest.
Encryption in transit
Connections between the application and the database are encrypted. The application also proves its identity to the database using its Google Cloud service identity.
Secrets
Database passwords, Google sign-in secrets, and API keys are kept in a managed secrets store, not in the application code. Services receive them when deployed.
Momence credentials
Each studio connects to TVS Dash with its own Momence credential. These credentials are held in the same managed secrets store.

Backups and availability

How the production database stays available and can be recovered.

High availability
A second database in a separate zone of the same region is ready to take over if the primary database becomes unavailable. The switch happens automatically, and the connection address stays the same.
Automated backups
The production database is backed up automatically. Backups are retained for 90 days and are encrypted at rest.
Point-in-time recovery
The database can be restored to a selected time within the available recovery period.
Restore testing
Restoring from backup is tested monthly through an automated process.
Service commitments
TVS Dash does not promise a specific uptime, restoration time, or maximum amount of data loss. Automatic failover and point-in-time recovery help limit downtime and data loss, but do not guarantee how long recovery will take or how much data can be recovered.

Application and network protections

Protections for requests between your browser and TVS Dash.

HTTPS
All traffic to TVS Dash is served over HTTPS.
Browser protections
Browser security settings limit where page scripts can load from, prevent other sites from placing TVS Dash in a frame, and block access to your camera, microphone, and location.
Caching
Browsers and shared caches are instructed not to store copies of signed-in pages.
Rate limiting
TVS Dash limits how many requests a signed-in account or internet address can make in a period. This helps reduce abuse and automated traffic.

Change management

Automated checks run before code changes are released to production.

Pre-deploy checks
Before each release, automated checks look for code errors, run tests, and check that database changes match the application.
Secret scanning
The same checks scan the code for accidentally included passwords or keys. Any values found are hidden from the scan results.

Incident response

How confirmed security incidents are handled.

Investigation
TVS Dash administrators investigate confirmed security incidents.
Notification
The franchisor is notified within 4 hours after an incident is confirmed.
Franchise partners
The franchisor determines and handles communication with affected franchise partners.

Development environment

A separate environment is used to build and test changes before release.

Data included
Information from a limited number of studios is copied from production into the development database. The owners of those studios have given permission.
Refresh schedule
Development data is refreshed from production as needed, not through continuous or automatic synchronization.
Same controls
Development data is encrypted and some information is masked. The development environment uses the same Google sign-in and access controls as production.

Franchisee offboarding

Access and data handling when a franchisee leaves TVS Dash.

Account access
The franchisee's accounts are disabled the same day.
Studio data
Studio-level data is retained for 30 days after offboarding.
Franchisor reporting
Aggregated studio rollups used in franchisor network reporting are retained indefinitely. The rollups do not contain member-level data.
Call center
The studio's leads can be removed from the call center dial list, as described under Outbound data and payments.

Hosting and infrastructure

TVS Dash runs on Google Cloud in the United States.

Application and jobs
The web application, and the scheduled jobs that pull data from Momence, advertising platforms, and other sources, run on managed Google Cloud services.
Infrastructure access
Access to the Google Cloud console, the production database, and stored secrets is limited to the TVS Dash administrator role. 2-step verification is enforced on that access.
Logging
Structured application logs are sent to Google Cloud Logging and to an application log table for administrator review.
Monitoring and alerts
Automated monitoring alerts the TVS Dash administrator role on uptime check failures, elevated error rates, and failed data sync jobs.

Data use and lifecycle

TVS Dash uses operational, customer, member, workforce, and wellness-related information for dashboards and reports.

Sensitive information
TVS Dash may process member and lead contact details, appointments, memberships, sales, staff information, financial details, uploaded business documents, and written wellness notes. What each account can see depends on its role and assignments.
Retention
Retention varies by data type. Studio data after a franchisee leaves is described under Franchisee offboarding, and log retention under Audit and activity logging.
Copies outside TVS Dash
Email reports and downloads can create copies outside TVS Dash. Changing access in TVS Dash does not remove copies already sent to someone.
Related sections
AI use of this data is described under AI features, and the development database under Development environment.

Outbound data and payments

Information sent from TVS Dash through reports, email, the call center, and billing.

Scheduled reports
Scheduled PDF reports are emailed only to their subscribed recipients and cover only the studios selected for the subscription.
Report delivery
PDF reports are sent as email attachments, not as public links. Links in report emails open TVS Dash and require sign-in.
Customer names and emails in reports
The 2-Day Intro follow-up worklist, which contains customer names and email addresses, is excluded from every report preset and appears only when selected individually.
Data exports
Exports contain only information the user is allowed to see. Downloads created in the browser use data already returned under that user's permissions. Server-created downloads check permissions in the same way as other requests.
Call center lead removal
An administrator can remove all leads TVS Dash sent to the call center for a studio. TVS Dash stops sending new leads for that studio first and records each removal.
Payments
Stripe handles subscription payments. Card and bank details are entered directly with Stripe. TVS Dash does not receive or store card numbers.

Privacy and data requests

Published policies and the process for requests about personal information.

Privacy notice and terms
The TVS Dash privacy notice and terms of use are published on this site and can be read without signing in.Privacy noticeTerms of use
Access, correction, and deletion
People whose information is in TVS Dash can request access, a correction, or deletion using the contact address below. TVS Dash administrators verify the requester, work with the relevant studio or franchisor, and respond in writing within 30 days.
What deletion covers
Deletion removes a person's records from TVS Dash. It does not remove copies already sent in email reports or downloads. Records may also remain in database backups until those backups expire.
Service provider changes
The third-party services list is updated, with a new review date, when a service that handles member, lead, or customer information is added or removed.

Reporting a vulnerability

How suspected security issues reach TVS Dash.

Where to report
Report suspected security weaknesses using the contact address below. The same address is published in a security.txt file.security.txt
Handling
TVS Dash administrators review reports. Confirmed issues are handled under the incident response process described on this page.
Out of scope
Testing is not authorized if it accesses another user's data, disrupts the service, or uses deception or physical access.

Third-party services

TVS Dash uses these outside services for specific features and operations. Which services are used depends on the features and settings for an account. A service appearing here does not mean it is used by every account or formally engaged to process data for TVS Dash.

Third-party services

Google CloudHosting, database, scheduled jobs, secrets, and loggingAll application data
GitHubSource code hosting and code-change workflowsSource code, repository metadata, and workflow data
Google sign-inAuthenticationName and email address
Google GeminiAI summaries and the Dash AgentAs described under AI features
MomenceStudio management data sourceCustomers, appointments, memberships, sales, and staff
MetaAd performance and lead adsCampaign metrics and lead contact details
Google AdsAd performanceCampaign metrics
Microsoft AdvertisingAd performanceCampaign metrics
Google Business ProfileStudio reviewsPublic reviews and ratings
Google Maps and PlacesLocation, place, and map featuresStudio addresses or coordinates, place details, and map requests
Showing 1–10 of 21
Page 1 of 3

For security, privacy, or account access questions, email the TVS Dash team at dash@thevitalstretch.com.