Privacy Policy

Beetle (“the Service”) is a client-workspace and reporting tool operated by Gourmet Marketing. This policy describes what we collect, how we use it, and the choices you have. Questions: ops@gourmetmarketing.com.

Information we collect

• Account data — your name, email address, and profile settings, provided when your organization invites you.
• Workspace content — the clients, links, files, categories, and notes your team creates in the Service.
• Usage data — basic operational logs (sign-ins, feature usage, errors) used to run and improve the Service.

Google user data (Analytics, Search Console & Google Ads)

If an administrator of your organization chooses to connect a Google account, the Service requests the following scopes:

• analytics.readonly — read-only access to Google Analytics.
• webmasters.readonly — read-only access to Google Search Console.
• adwords — access to Google Ads. This is the onlyOAuth scope Google publishes for the Google Ads API; there is no read-only variant, which is why the consent screen describes it as “see, edit, create, and delete”. The Service uses it exclusively to read reporting data (Google Ads API searchStream queries). It never creates, edits, pauses, or deletes campaigns, ad groups, ads, budgets, keywords, or accounts, and it never spends your advertising budget.

We use this access only to:

• list the Analytics properties, Search Console sites, and Google Ads accounts you can access, so you can map them to a client workspace; and
• display performance reports (traffic, search, advertising, and revenue metrics) to authorized members of your organization inside the Service.

The Google Ads scope is optional. Declining it at the consent screen leaves the Analytics and Search Console reports fully working; only the Google Ads report stays unavailable, and it says so rather than showing estimated figures.

We store the OAuth refresh token server-side, encrypted at rest, isolated per organization, and never expose it to browsers. We do not sell Google user data, use it for advertising, or allow humans to read it except with your permission, for security purposes, or as required by law.

The Service’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can revoke the connection at any time from the Service (“Disconnect” in client settings) or at myaccount.google.com/permissions. Revoking deletes our ability to read your Google data; stored report snapshots created while connected remain in your organization’s workspace until deleted.

How we share data

We do not sell personal data. Data is shared only with the infrastructure providers that host the Service (Google Cloud / Firebase, in the United States) under their standard data processing terms, and within your own organization according to the roles and sharing rules your administrators configure.

Retention & deletion

Workspace content is retained while your organization’s account is active. Disconnecting Google removes the stored token immediately. When an organization is deleted, its data — including any Google connection — is permanently removed. You may also request deletion at the contact address above.

Security

Data is encrypted in transit (TLS) and at rest. Access is enforced server-side per organization and role; Google tokens are only ever used by our backend services.

Changes

We will post any changes to this policy on this page with an updated effective date.