Privacy policy
We collect as little as we can. No advertising cookies, no analytics, no tracking pixels, no selling of data. This page explains the little we do process and why.
Last updated 19 November 2026
1. Who we are
Architect AS ("Architect", "we", "us") is the controller for the personal data described here. This policy covers our website architect.media and our web application Architect Terminal at terminal.architect.media (the "Terminal").
- Architect AS, organisation number 937 528 876, Morenen 48, 1519 Moss, Norway
- Email: [email protected]
Where we process data on behalf of a customer under a separate agreement (for example channel lists a customer uploads to the Terminal), that agreement and any data processing agreement take precedence for that data.
2. What we collect and why
| When | What | Why (legal basis) |
|---|---|---|
| You visit the website | Technical request data our hosting provider processes to deliver pages and protect against abuse: IP address, browser user agent, requested URL, time. | Delivering and securing the site (legitimate interest, GDPR art. 6(1)(f)). |
| You send the pilot request form | Name, company, work email, role, annual media budget range and your message. | Replying to your request and scoping a pilot (steps before a contract, art. 6(1)(b), and legitimate interest, art. 6(1)(f)). |
| You email us | Your email address and whatever you include in the message. | Answering you (legitimate interest, art. 6(1)(f)). |
| You have a Terminal account | Name, email address, password (stored only as a one-way hash), the organisation you belong to, your permissions, and the work you do in the Terminal (lists, imports, settings and a history of changes). | Providing the service you or your organisation signed up for (contract, art. 6(1)(b)). |
| You sign in with Google | From Google: your name, email address, Google account ID and profile picture URL. We do not receive your Google password. | Letting you sign in (contract, art. 6(1)(b)). |
| You connect Google Ads or Display & Video 360 | An OAuth refresh token (stored encrypted), the permissions you granted, and the account, campaign, ad group and ad data needed to deliver lists. Section 4 lists exactly what. | Delivering channel lists to the ad accounts you choose (contract, art. 6(1)(b)). |
| Something breaks in the Terminal | Error and performance reports: the error, the page or request involved, browser and device type, and your user ID. | Finding and fixing bugs, keeping the service reliable (legitimate interest, art. 6(1)(f)). |
| We email you from the Terminal | Your email address and the message (for example email verification and password reset). | Running your account (contract, art. 6(1)(b)). |
We do not use your data for advertising, we do not build profiles of you, we do not sell or rent it, and we make no automated decisions about you that have legal or similarly significant effects.
The channel data in the Terminal is about YouTube channels and their public content, not about Terminal users.
3. Cookies
The website sets no cookies and uses no analytics, advertising or tracking tools. It does not load fonts, scripts or other content from third parties.
The Terminal sets only cookies that are strictly necessary for it to work, so no consent banner is needed:
| Cookie | Purpose | Lifetime |
|---|---|---|
adonis-session | Keeps you signed in. | 2 hours of inactivity |
XSRF-TOKEN | Protects forms against cross-site request forgery. | Session |
4. Google user data
This section explains how Architect Terminal accesses, uses, shares, protects, keeps and deletes data it receives from Google APIs ("Google user data"). It covers Sign in with Google and the Google Ads and Display & Video 360 (DV360) connections. You choose whether to use any of them, and you can disconnect at any time.
Data we access
- Sign in with Google (scopes
openid,email,profile): your name, email address, Google account ID and profile picture URL. - Google Ads (scope
https://www.googleapis.com/auth/adwords), only after you connect an account:- the Google Ads accounts you can access: customer IDs, account names, manager account structure, account status and your access role;
- for the campaigns you pick in the Terminal: campaign IDs, names, status and type; their ad groups with settings and targeting; the ads in those ad groups, including ad content and the YouTube video IDs they use;
- the account's YouTube channel exclusions.
- Display & Video 360 (scope
https://www.googleapis.com/auth/display-video), only after you connect an account:- the partners and advertisers you can access: IDs and names;
- for the advertisers you pick: line items and ad groups with their settings, and their YouTube channel targeting;
- the advertiser's YouTube channel exclusions.
We do not access performance metrics, costs, budgets, billing or payment information, or audience and customer data you have uploaded to Google. We do not create aggregated or anonymised datasets from Google user data.
How we use it
We use Google user data only to provide the features you use in the Terminal:
- signing you in;
- showing you the accounts, advertisers, campaigns and ad groups you can deliver channel lists to;
- delivering your channel lists: adding, updating and removing YouTube channel exclusions, and creating and updating copies of a template ad group you choose, with the YouTube channel targeting from your list;
- reading back what is live in your account to confirm delivery and show you its status;
- fixing problems with these features.
We do not use Google user data, raw or aggregated, for advertising, profiling, credit or lending decisions, selling, or any purpose other than these user-facing features. We do not use it to develop, improve or train AI or machine learning models, and we do not send it to AI or machine learning services.
Who we share it with
We do not sell, rent or transfer Google user data, raw or aggregated, to advertisers, data brokers, information resellers or any other third party. It is transferred only:
- to Google, when the Terminal acts on your Google Ads or DV360 accounts at your request;
- to the service providers that run the Terminal for us under contract and may not use it for anything else: DigitalOcean (servers and database, Frankfurt, Germany) and Sentry (error reports, EU), where an error report can contain technical identifiers such as an account or ad group ID, never your token;
- where the law requires it, or with your explicit consent;
- to a successor in a merger, acquisition or sale of Architect, which must keep the same protections, and we will tell you before it happens.
How we protect it
- All traffic to and from the Terminal and Google is encrypted with TLS.
- OAuth refresh tokens are encrypted at rest with application-level encryption, used only on our servers, and never sent to your browser or shown in the Terminal.
- The Terminal runs on servers in the EU. Access to production systems is limited to the few staff who need it to run the service.
- A Google connection belongs to your organisation. Only signed-in members of that organisation with the right permissions can use it.
- Our staff do not read Google user data, except with your permission, when needed for security or to investigate abuse, or where the law requires it.
Retention and deletion
- Refresh token and the cached list of your accounts and advertisers: kept until you disconnect in the Terminal (Integrations), revoke access at myaccount.google.com/permissions, or your organisation's account is closed. Disconnecting deletes them immediately. If Google revokes a token, we stop using it.
- IDs of the accounts, ad groups and ads we deliver to, and the delivery history: kept with the channel list they belong to, and deleted when you delete that list or delivery, or within 90 days after your account is closed.
- Sign-in profile data: kept while your account is active, and deleted within 90 days after it is closed.
- Error reports: deleted automatically after 90 days.
- You can ask us to delete any Google user data we hold by emailing [email protected]. We will do so within 30 days.
Limited Use
Architect Terminal's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Who we share data with
We use a small number of service providers that process data for us under data processing agreements. They may only use it to provide their service to us.
| Provider | What for | Where |
|---|---|---|
| Cloudflare, Inc. | Hosting and delivering the website, receiving the pilot form. | Global network, USA |
| DigitalOcean, LLC | Servers and database for the Terminal. | EU (Frankfurt, Germany) |
| Functional Software, Inc. (Sentry) | Error and performance monitoring for the Terminal. | EU (Germany) |
| Mailgun Technologies, Inc. | Sending Terminal emails. | USA |
| Google LLC | Sign in with Google, and reading from and delivering lists to Google Ads and Display & Video 360 at your request. See section 4. | USA |
Where data is transferred outside the EU/EEA, we rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses.
We may also disclose data where the law requires it, or to a buyer or successor if Architect is reorganised, merged or sold, in which case this policy continues to apply.
6. How long we keep it
- Pilot requests and emails: up to 24 months after our last contact, unless they lead to a customer relationship.
- Terminal account data: while the account is active, and deleted or anonymised within 90 days after it is closed, unless we must keep it longer by law (for example accounting records).
- Google user data: see section 4.
- Error reports: up to 90 days.
- Hosting request logs: as set by our hosting providers, normally a few days to weeks.
7. Your rights
Under the GDPR you can ask for access to your data, a copy in a portable format, correction, deletion, or restriction of processing, and you can object to processing based on our legitimate interests. Email [email protected] and we will answer within one month.
If you think we handle your data wrongly, you can complain to the Norwegian Data Protection Authority, Datatilsynet, or the data protection authority where you live. We would appreciate the chance to fix it first.
8. Security
Data is encrypted in transit, Google tokens are encrypted at rest, passwords are hashed, and access to production systems is limited to the people who need it.
9. Children
Our services are for businesses and are not directed at anyone under 18. We do not knowingly collect data from children.
10. Changes
We will update this page when what we do changes and change the date at the top. If a change materially affects Terminal users, we will tell them by email or in the Terminal before it takes effect.