Onboarding Hub Privacy Policy
How Ever Studios Onboarding Hub accesses, uses, shares and protects client and Google account information.
Effective September 22, 2026
This policy explains how Ever Studios (“we,” “us,” or “our”) handles information in Ever Studios Onboarding Hub, including the client workspace at clients.theeverstudios.com, private onboarding links, Google account connections and staff email sending. Learn about the app on our Onboarding Hub page.
This policy supplements our general Privacy Policy. For Google user data handled by the Hub, the specific limits in this policy apply over any broader descriptions of advertising, marketing or AI use in the general policy.
1. Information we access and collect
- Client and onboarding records: business names, contact names and email addresses, website details, assigned services, onboarding responses and notes, team assignments, billing-record references and access status. Information may come from you, your authorized contact, our team or our connected invoicing system.
- Google sign-in: account identifiers, verified email address and available basic profile information used to identify the account. Staff sign-in also checks the work domain and portal permissions.
- Google Analytics connections: account and property names and identifiers, and existing user access bindings, including email addresses and roles. The requested Analytics read permission can permit access to Analytics data; the current onboarding flow uses it to locate account/property information, alongside user-management permission to grant and verify teammate access.
- Site Verification / Search Console ownership: verified site or domain identifiers and ownership records, including owner email addresses, used to display eligible properties and add the teammates you approve as owners.
- Staff email sending: the sender, recipients, subject and message content needed to send an authorized email through Gmail. The portal records sending history such as recipients, subjects, timestamps, message identifiers and delivery outcomes. This feature requests sending access, not access to read inbox messages or replies.
- Operational information: session identifiers, authorization state, access and change records, and technical logs used to operate and protect the service.
Google authorization takes place on Google’s pages. Do not enter Google passwords into onboarding notes or send them to our team.
2. How we use this information
We use information to identify authorized users, organize your client record and onboarding, show the appropriate Google properties, carry out and verify the access grants you approve, support your requested services, send authorized staff communications, troubleshoot problems and maintain security and accountability.
We use Google user data only for these user-facing features and their support. We do not sell Google user data, use it for targeted advertising or data brokerage, or use it to determine creditworthiness. We do not use data obtained through Google Workspace APIs to develop, improve or train generalized or non-personalized AI or machine-learning models.
3. People and services that receive information
Authorized Ever Studios personnel may access client records as needed for their work. The employees or contractors shown on the Google access confirmation screen receive the platform access you approve; a teammate may use a Google account outside the Ever Studios domain. Those native platform permissions let the teammate access the selected property directly through their own account.
We transmit the relevant property identifiers, team email addresses and access requests to Google to perform the connection. Staff email recipients receive the messages addressed to them. Google processes sign-in, platform access and Gmail sending. Our hosting provider, SiteGround, and technical service providers may process stored data to operate and secure the service. Client details may be matched with our invoicing system for client administration; Google authorization tokens are not used as billing credentials.
Human access to Google user data is limited to authorized service delivery, user-authorized support, security or abuse investigations, legal obligations, or other uses permitted by Google’s policies. We do not transfer Google user data for unrelated advertising or AI model training.
4. Storage and protection
The Hub uses HTTPS for connections. Client records, access records and server-side sessions are stored in private server locations with restricted file access. Staff authentication, portal permissions and checks on client onboarding links control access. Security measures reduce risk but cannot guarantee that every incident will be prevented.
The client Google grant flow holds a short-lived access token in a server-side session to complete the operation. It does not retain a client refresh token for continuing background access. The access token is removed from that session after a successful grant; an unfinished connection session becomes unusable after its expiry. Session files and operational backups may persist until server cleanup or backup rotation.
5. Retention and deletion
We retain client profiles, onboarding records, access-grant confirmations and communication history for as long as reasonably necessary to provide the requested services, support the client relationship, maintain security and accountability, resolve disputes or meet legal obligations. Grant confirmations can include the selected property, the authorizing email address, assigned teammates, granted roles and timestamps. Retention varies by record type and purpose; these records are not all automatically erased when an onboarding link expires.
To request access, correction or deletion of Hub records, email chad@theeverstudios.com and identify your business and the records involved. Do not include passwords or access tokens. We may verify your authority before acting. We will delete information that is no longer needed, subject to applicable legal obligations and necessary security or dispute records. Copies in backups may remain until those backups rotate out. Deleting a Hub record does not by itself delete messages in Gmail or records held independently by Google or your invoicing provider.
6. Revoking access and stopping connections
You can decline Google’s consent request or remove the app’s connection through your Google Account’s third-party connections. You can ask us to revoke an onboarding link or assist with access removal.
App authorization and teammate permissions are separate. Revoking this app, deleting a Hub record, or changing a portal assignment does not automatically revoke permissions previously granted to individual teammates. Remove those people through Google Analytics access management or the applicable site ownership / Search Console settings. Search Console Owner access includes permission-management capabilities. Contact us if you need help reviewing existing grants.
Staff email sending can be disabled through portal sending permissions. Google Workspace administrators also control the separate Workspace authorization for that feature.
7. Google API policy commitments
Our use and disclosure of information received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. The restrictions described above apply specifically to Google user data regardless of any broader permission described in our general website policy.
8. Updates and contact
We will update this page and its effective date when these practices change, and provide additional notice when required. This page is available without signing in.
Ever Studios
Email: chad@theeverstudios.com
Mailing address: 4444 2nd Ave, STE 38660, Detroit, MI 48201
About Ever Studios Onboarding Hub · Open the client workspace