Privacy policy
Last updated 21 August 2026
Lakeside CMS is the internal operations platform of Lakeside Marketing (“we”, “us”). It is used by our staff to manage the marketing work we perform for our clients. It is not offered to the public and has no public sign-up.
Who this policy covers
Two groups of people, with different relationships to us:
- Our staff, who hold accounts in the application.
- Our clients, who authorise us to connect their own marketing accounts so that we can report on their performance.
The application is not used to collect information from members of the public, and it does not host any public-facing website or form on a client’s behalf.
What we hold
Staff accounts
An email address, a name, a role, and a password stored only as a cryptographic hash. We never see or store a staff password in readable form.
Client business records
Business information about our clients — company name, website, service area, the services they sell, commercial terms, and notes made by our staff. This is business information, not personal information about consumers.
Data from connected Google accounts
When a client authorises it, we connect their Google accounts and read reporting data from them. We only ever read. Two of the four permissions we request are nonetheless broader than that, because Google publishes no read-only scope for those APIs — noted below where it applies:
- Google Analytics
- Sessions, traffic sources, conversions and related aggregate metrics.
- Search Console
- Impressions, clicks, positions and search queries for the client’s verified site.
- Google Ads
- Spend, conversions and campaign performance for the client’s account. The granted permission also permits changes; we make none.
- Business Profile
- The client’s listing details, used to confirm their local presence. The granted permission also permits changes; we make none.
We store the aggregate figures those APIs return so a report can be produced and compared over time. We do not download or retain individual end-user records, visitor identifiers, or advertising identifiers.
Research on prospective clients
We also produce marketing research for businesses that are not yet our clients. This research never uses data from anyone’s Google account. It draws only on publicly available information:
- the business’s own public website, as any visitor would see it;
- search-volume and search-results data licensed from third-party providers;
- public business listings and publicly published reviews.
Data obtained from a Google account is used to report to the account holder. We do not disclose one client’s data to another business, and no report we produce for one business identifies another’s account, spend, or performance.
Where we describe industry norms, those figures are either taken from a published source we name, or aggregated and anonymised so that no individual account is identifiable.
Limited Use. Lakeside CMS’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we use the data only to provide reporting to the client it came from; we do not transfer it except as necessary to provide that service, to comply with applicable law, or as part of a merger or acquisition; we do not use it for advertising; and we do not allow humans to read it except with the client’s consent, for security purposes, to comply with applicable law, or where the data has been aggregated and anonymised.
How credentials are protected
When a client authorises a connection, Google issues us a token. That token is placed directly into an encrypted secrets vault. The application’s own database identity has permission to write a credential and no permission to read one back— only the separate background process that fetches reporting data can decrypt it.
No credential is stored in an ordinary database field, displayed in the interface, or written to a log. This is enforced by database privilege rather than by application code, so a fault in the application cannot expose a token.
Who we share it with
We do not sell data and we do not share it for advertising. Data is shared only with the infrastructure providers required to run the service — hosting, database and search-data providers — each acting on our instructions, and with the client the data belongs to. We may also disclose information where the law requires it.
How long we keep it
Reporting data is retained while a client relationship is active, so that performance can be compared over time. When a connection is disconnected its stored credential is destroyed. When a client relationship ends, their records are deleted on request and otherwise within a reasonable period.
Revoking access
A client can revoke our access at any time, either by asking us to disconnect the connection or directly at myaccount.google.com/permissions. Revoking stops all further access immediately.
Your rights
You may ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to pete@madebylakeside.com and we will respond.
Contact
Lakeside Marketing
pete@madebylakeside.com
madebylakeside.com