Privacy Policy

Effective date: 20 October 2026

This policy explains how Newbuilds collects, uses, stores, shares and protects personal data, including data we receive from Google, and the choices you have about it.

Newbuilds is operated by Marketer 360 AS (part of Vergence AS), organisation number 936073433, Tjuvholmen allé 1, 0252 Oslo, Norway (“Newbuilds”, “we”, “us”). For questions about this policy, write to post@newbuilds.com.

Who this policy covers

  • Visitors to newbuilds.com.

  • Users of the Newbuilds app: people who sign in to manage projects, campaigns and leads for their company. We are the controller of their account data.

  • People who visit pages our customers publish with Newbuilds (landing pages, property explorers, news and lead forms), or who are in a customer’s lead and contact lists. For that data our customer is the controller and we process it on their behalf under our agreement with them. Questions about it are best sent to that company first; its privacy policy is linked from its pages.

Information we collect

Account and contact data

When you sign up or sign in: your name, email address and, if you give it, your phone number. When you sign in with Google we receive your name, email address, Google account ID and profile picture.

Usage data

Information about how the website and app are used: IP address, browser type and version, pages visited, time and date of a visit, time spent on pages, device identifiers and diagnostic data. We use cookies and similar technologies for sign-in and, where you agree, analytics.

Google user data

If you connect a Google Ads account to Newbuilds, you authorise us through Google’s OAuth consent screen. We then access:

  • OAuth tokens that let us call the Google Ads API on your behalf.

  • Your Google account’s email address and ID, to show which Google account is connected.

  • The Google Ads accounts you can reach, including manager accounts, so you can choose which to connect.

  • Campaign structure of the accounts you choose: campaigns, budgets, ad groups, ads, asset groups, keywords, locations, ad text and image links.

  • Performance reports: daily impressions, clicks, cost, conversions and similar metrics.

  • Account settings we need: whether auto-tagging is on, and the conversion actions in the account.

At your request we also make changes in the accounts you connect: we create campaigns (always paused, so nothing spends until you activate them), edit or remove campaigns, ad groups, ads, asset groups and keywords, and create a conversion action named “Newbuilds lead”. That conversion action is secondary, so it does not change how any existing campaign bids.

Data about your customers’ visitors and leads

On pages our customers publish, we collect what visitors submit in forms (such as name, email, phone and message) and, only when the visitor consents, ad click identifiers (such as Google’s gclid) and how they use the page. We process this on our customer’s behalf.

How we use information

We use the information above to provide, secure and improve Newbuilds: to sign you in, run the features you use, answer support requests, keep the service secure and meet legal obligations.

Legal basis

We rely on these legal bases under the GDPR:

  • Contract: to run your account and the features you and your company use, including Google Ads.

  • Legitimate interest: to keep the service secure, handle support requests and error reports, and improve the service.

  • Consent: for analytics where we ask for it. You can withdraw consent at any time.

  • Legal obligation: to keep accounting records and answer lawful requests from public authorities.

How we use Google user data

We use Google user data only to provide the features you use in Newbuilds:

  • show your Google Ads campaigns and their results next to your projects, leads and other channels;

  • create, edit, pause and remove campaigns when you ask us to;

  • report leads from your landing pages to your Google Ads account as conversions. We send only the ad click ID (gclid, gbraid or wbraid), the time of the conversion and the conversion action, and only for visitors who agreed to advertising measurement. We never send names, email addresses or phone numbers;

  • answer questions about your campaigns in the Newbuilds assistant, when you ask it to.

We do not use Google user data for advertising, retargeting or interest-based ads, do not sell it, do not use it to judge creditworthiness, and do not use it to develop, improve or train generalised or non-personalised AI or machine-learning models.

Limited Use. Newbuilds’ 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.

Sharing and service providers

We do not sell personal data or Google user data, and we do not share it with third parties for their own purposes. We share it only with the service providers below, which process it on our instructions, under data processing agreements, to run Newbuilds, with services you choose to connect, and where the law requires it.

  • Railway: Hosts the app and its database. Google user data: Stored.

  • ClickHouse Cloud: Stores campaign performance reports (Frankfurt, Germany). Google user data: Stored.

  • Cloudflare: Network, security and file storage (R2). Google user data: Ad images stored.

  • Inngest: Runs background jobs such as campaign syncs. Google user data: Passes through.

  • Sentry: Error reports. Google user data: No (tokens are removed from reports).

  • Anthropic: Powers the Newbuilds assistant. Google user data: Only campaign figures you ask the assistant about.

  • Brevo: Sends email and SMS. Google user data: No.

  • PostHog (EU): Product analytics. Google user data: No.

Services you connect. If you connect your own AI assistant (such as Claude or ChatGPT) to Newbuilds, it can read the analytics you have access to, including Google Ads campaign figures, and we send them to it at your request. Data you send to Meta, Snapchat, OpenAI ads or a CRM (Vitec, Visma Core) through Newbuilds is governed by your agreement with them; no Google user data is sent to them.

Legal requirements. We may disclose personal data in the good-faith belief that it is necessary to comply with a legal obligation; protect and defend the rights or property of Newbuilds; prevent or investigate possible wrongdoing in connection with the service; protect the personal safety of users or the public; or protect against legal liability.

How we protect Google user data

We treat Google user data, including OAuth tokens and Google Ads account and campaign data, as sensitive data. Security procedures are in place to protect its confidentiality, and we use encryption to protect it in transit and at rest. We protect other personal data the same way.

  • Encryption in transit. All traffic between your browser, our servers and Google’s APIs uses HTTPS. Connections to newbuilds.com require TLS 1.3, and our connections to Google’s APIs use TLS 1.2 or higher.

  • Encryption at rest. Our database, reporting store and file storage are encrypted at rest with AES-256 by our hosting providers (Railway, ClickHouse Cloud and Cloudflare R2).

  • Credentials stay on our servers. Google OAuth tokens are stored only on our servers. They are never sent to your browser, never shown in the app, never written to logs, and are removed from error reports before those reports leave our servers.

  • Access control. Each company’s data is visible only to that company’s members. Every request is checked against the signed-in user’s membership, and only a company owner can connect or change Google Ads accounts.

  • Limited staff access. A small number of Newbuilds staff can access customer data, only to provide support you ask for, keep the service secure, or comply with the law. Staff actions through our admin tools and assistant integrations are recorded in an audit log.

  • Least privilege. We ask Google only for the access we need: openid and email for sign-in and adwords for Google Ads. We read and change only the Google Ads accounts you choose to connect.

  • Data minimisation. Conversion reports to Google contain only a click ID and a timestamp, never contact details.

  • Incidents. If a security incident affects your data, we notify affected customers without undue delay and as required by law, including the Norwegian Data Protection Authority (Datatilsynet) where required.

Retention and deletion

We keep personal data only as long as we need it to provide the service, or as the law requires, and then delete it.

  • Google OAuth tokens: Until you disconnect Google Ads, then deleted at once.

  • Google Ads campaign structure: Until you remove the account from Newbuilds or disconnect Google Ads, then deleted at once.

  • Google Ads performance reports: While your company has an account, or until you ask us to delete them.

  • Account data: While your company has an account, or until you ask us to delete it.

  • Invoices and accounting records: As long as Norwegian accounting law requires (currently 5 years).

  • Visitor activity not tied to a lead: 13 months.

  • Consent choices: Deleted once more than 13 months old and the visitor record is gone.

Deleting your data. You can disconnect Google Ads at any time under Settings, Integrations, and revoke Newbuilds’ access in your Google account at myaccount.google.com/permissions. Disconnecting deletes the OAuth tokens and the campaign structure at once. To have your account or other data deleted, including Google Ads performance reports, write to post@newbuilds.com; we delete it within 30 days of your request.

Transfer of data

We are based in Norway and process data in the EU/EEA where we can. Google Ads performance reports are stored with ClickHouse Cloud in Frankfurt, Germany. Some of our service providers are based in, or may process data in, other countries, including the United States. Where data leaves the EU/EEA we rely on the European Commission’s standard contractual clauses or an adequacy decision, and we only transfer personal data where adequate safeguards are in place.

Your rights

If you are in the EU/EEA or the UK, you can ask to access, correct, delete or receive a copy of your personal data, and object to or restrict how we use it. Where we rely on your consent, you can withdraw it at any time. Write to post@newbuilds.com. You can also complain to the Norwegian Data Protection Authority (Datatilsynet), or to your local authority, such as the UK Information Commissioner’s Office (ico.org.uk).

Business contacts and prospecting (UK and EU)

If you work at a company we think could benefit from Newbuilds, we may process your name, job title, employer and work contact details to get in touch about our services. We get these details from public sources and from business contact data providers such as Lusha.

Our lawful basis is our legitimate interest in promoting our services to businesses. We only contact people in relevant roles, at their work address. We keep these details for up to 12 months after our last contact unless you become a customer.

You can object at any time by replying to any of our emails or writing to post@newbuilds.com. We will then stop contacting you and delete your details, keeping only what we need to make sure we don’t contact you again. You can also ask to see or correct your data, and you can complain to the UK Information Commissioner’s Office (ico.org.uk).

Changes to this policy

We will update this policy when our practices change and show the new effective date at the top. If we change how we use Google user data or other personal data in a significant way, we will notify signed-in users in the app or by email before the change takes effect.

Contact

Marketer 360 AS (part of Vergence AS), organisation number 936073433, Tjuvholmen allé 1, 0252 Oslo, Norway. Email: post@newbuilds.com. Telephone: +47 971 03 616.