Privacy policy
Campaign Lab Beta (“Campaign Lab”) is operated by Tencaro Services LTD. This policy describes our public website at campaignlab-ai.com and our hosted beta service. For privacy questions or requests, contact maria@tencaro.com.
Our website and beta service
Campaign Lab is Tencaro Services LTD’s internal agency operations platform. External account owners may register, verify their email, sign in and authorize their own Google account. New registrations receive the Guest role. Guests can view their own connection status, reconnect and disconnect; they cannot use campaign tools, AI generation, reports, conversion management or administration. Operational roles are reserved for Tencaro employees and assigned by administrators. Employees and the background tasks they configure carry out supported Google Ads operations. We will update this policy when data handling changes.
Information we collect
- Website requests: Google Firebase Hosting and Cloudflare, our website delivery and protection providers, process information such as IP addresses, request times, requested pages, and browser information to deliver and protect the website and application. We have not added advertising trackers or analytics cookies to this public site.
- Contact messages: if you email us, we receive your email address, name if supplied, and the information you include in your message.
- Beta workspace information: your name, email address, agency name, session information, campaign drafts and revisions, and records of actions taken in the workspace. Google Firebase Authentication handles account credentials, verification, and password recovery. Campaign Lab’s application database does not store your password.
- Google connection information: when you choose to connect Google, we receive your Google identity and email address, granted permissions, and authorization tokens. We use Google Ads access to discover available accounts, including their IDs, names, manager relationships, currencies, time zones, status, and conversion settings. At an authorized employee’s request, we retrieve campaign performance such as impressions, clicks, cost, conversions, and conversion value.
- Conversion information: saved Purchase and Subscribe action settings and Google resource IDs. Configured conversion imports also process event times, click identifiers, event types, source URLs, destination account IDs, upload results, and deduplication records. These support conversion delivery configured by authorized Tencaro employees.
How we use information
We use this information to maintain account access, manage Google authorization, provide Tencaro’s agency services, respond to questions and protect the service. Authorized employees use connected accounts to prepare and publish campaigns, read reports and configure conversion workflows. Google Ads permissions may allow account management, but authorizing a connection does not grant the Guest operational access in Campaign Lab. Server-side checks block Guest management requests. Employees must explicitly select campaigns for publication; saving a draft does not publish it.
When an authorized employee chooses Generate with AI, we send the supplied topic or public-page content, optional notes, ad-group name and chosen output language to Google Cloud Vertex AI to suggest keywords or ad copy. Guests do not have access to this feature. Do not include personal or confidential information in those fields. Scraped text is cached in server memory for up to ten minutes; the application does not persist that cache in its database. Suggestions are saved in a draft only when you apply them. We do not send Google account credentials, account inventory, reports, or conversion records to this AI feature, and we do not use Google user data to train generalized AI or machine-learning models.
Google user data and Limited Use
Campaign Lab’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We do not sell Google user data, use it to serve advertising, or transfer it to data brokers. We use it to provide the features you authorize. Human access to Google user data is limited to circumstances permitted by Google’s Limited Use requirements, such as your affirmative agreement to review specific information for support, security needs, or legal requirements.
Sharing and service providers
Google receives the information needed for operations performed by authorized Tencaro employees, including published campaign content and settings, conversion configurations, and conversion events enabled for delivery. Google Cloud Vertex AI processes the landing-page suggestion requests described above through its global endpoint, which may process outside Belgium. Google Firebase Hosting and Cloud Run deliver the website and application; Firebase Authentication manages identity and transactional account email; Firestore stores workspace records and backups; Secret Manager protects server credentials. Cloudflare provides domain-name resolution, HTTPS proxying, content delivery, and traffic protection. Website and application requests pass through Cloudflare; private API responses and signed-in workspace routes are excluded from its cache. Our email provider processes messages you send to our support address. The hosted beta uses Google Cloud infrastructure, with the workspace database and application service located in Belgium (europe-west1). Local development data and local Google connections are not automatically copied into hosted workspaces. Authorized Tencaro personnel may access information as needed to provide the agency service, subject to the Google data restrictions above. External Guest users can access only their own Google authorization status and controls.
We may disclose information when required by law or to address fraud, abuse, or security incidents. Providers may process information in countries outside your own. Google’s and Cloudflare’s own privacy terms apply to their independent processing.
Storage and security
Google Firebase Authentication handles passwords. Google refresh tokens are encrypted by the application using a key held in Secret Manager. Session tokens are stored as hashes and sent in a Secure, HTTP-only cookie. Drafts and templates are scoped to their creator, with cross-user access for authorized administrators. Account inventory and operational data are protected by workspace and role checks; designated internal roles can access connected accounts across the system. Guests receive only their own authorization controls. Data is stored in Firestore; direct browser access to that database is disabled. The service uses HTTPS, managed access controls, backups, and request limits. No security measure provides an absolute guarantee.
Retention and deletion
Current drafts, account metadata, reports, and conversion configurations are retained while your workspace remains active. Draft revision records expire after 90 days. Sessions expire after seven days and Google connection attempts after ten minutes; expired records are cleaned up automatically. Reports may be reused for ten minutes before a fresh request.
Employees with the required permissions can export workspace records and delete their workspace/account in Settings. Guest users can request account or data export and deletion by contacting us at the address below; their authorization-only screen does not provide workspace management tools. Deletion removes active workspace records and stored Google credentials; daily backups and point-in-time recovery copies expire within seven days. A minimal deletion marker is retained for up to 30 days to prevent interrupted operations from restoring a deleted workspace. For assistance or a fuller data-access request, contact maria@tencaro.com. Information may be retained when required by law or necessary to resolve a security issue.
Disconnecting Google in the beta removes the stored connection credentials. It does not by itself delete saved workspace records or undo changes already made in Google Ads. You can also revoke access through your Google account’s third-party connections. Deleting data from Campaign Lab does not automatically delete data already transmitted to Google; those records are subject to Google’s controls and retention policies.
Your choices and rights
You choose whether to authorize your Google account and can disconnect it from Campaign Lab or revoke the grant in your Google account. Our employees choose advertiser accounts for agency work within the access granted by Google and their Campaign Lab permissions. Contact us to request access, correction, export, or deletion of your personal information, or to raise a privacy concern. Depending on your location, you may have additional rights, including the right to complain to a data-protection authority. The service is intended for business users and is not directed at children.
Policy changes and contact
We will post changes here with an updated date and notify beta participants of material changes to how their data is used. Operator: Tencaro Services LTD. Privacy and support: maria@tencaro.com.