Privacy policy

This policy covers ensight.team and Ensight, the service at app.ensight.team and its command line, made by elim.io. For the data below we decide why and how it is used. The ad data an organization connects to Ensight is processed on that organization's instructions.

What we collect

• Demo form: your name, work email, and the company, company size and message you choose to add, with your IP address and browser, to answer you and keep spam out.
• Sign-in: access is by invitation. Google sign-in gives us your email, name and Google account ID, through the openid, email and profile scopes only; we never see your Google password. We also keep your organization and role, and a record of who did what. One cookie, ensight_session, keeps you signed in for 30 days.
• Connected accounts: the tokens that let Ensight read a Meta, Google Ads, Adjust or AppsFlyer account, and the aggregated data it reads: campaigns, ads, settings and daily statistics such as spend, installs and events. Ensight holds no data about individual end users.

This site sets no cookies, runs no analytics or advertising and loads nothing from third parties.

How we use it

To answer demo requests, let invited people sign in, read the accounts an organization connects and show the data to that organization, and keep the service secure. Our legal bases under the GDPR are steps before a contract and its performance, our legitimate interests in replying to enquiries and keeping the service secure, and legal obligations.

Google user data

Ensight receives your Google sign-in profile and, when an organization connects Google Ads, the Google Ads data of its accounts. Today Ensight only reads Google Ads data.

• We use it only to provide the features you see in Ensight: signing in, and reading and showing the connected accounts' data.
• We do not transfer it, except to provide those features, to comply with the law, or in a merger or sale with notice to you.
• We do not use it for advertising, including retargeting and interest-based ads.
• We do not let people read it, unless you consent, it is needed for security or abuse, the law requires it, or it is aggregated for internal operations.
• We do not use it to train generalized AI or machine-learning models.

Who we share it with

• Google Cloud (Belgium, EU) hosts Ensight and this site.
• Google Sign-In confirms who you are when you sign in.
• Cloudflare runs our DNS records only; no traffic passes through it.
• The ad platforms you connect (Meta, Google Ads, Adjust, AppsFlyer) are the sources of the data, not our processors.
• Demo requests reach our team through our internal tools.

We may also share data with our advisers, with authorities when the law requires it, and with a successor if the business is sold. Where a provider sits outside the EU or the UK, the transfer rests on the EU-US Data Privacy Framework or the European Commission's Standard Contractual Clauses.

Where it is stored and for how long

In the EU: Google Cloud, Belgium.

• Account details: while you have access. Demo requests: up to 24 months after our last exchange.
• Ad data: while the organization uses Ensight, or until it is deleted.
• Raw copies of ad platform responses: 25 months. Database backups roll off after 7 days.
• Command-line tokens stop working after 90 days without use.

Deleting your data

• Disconnect a source. An administrator or owner can disconnect it in Ensight. Its stored token is deleted at once and nothing more is read; data already read stays until the organization is deleted.
• Delete an organization, or your own data. Ask us, as described under Your rights. We delete it everywhere, including its encryption key.
• Through Meta. Remove Ensight from your apps in Meta's settings. If you ask Meta to delete the data Ensight holds, Meta calls our deletion address, https://app.ensight.team/meta/data-deletion. We then delete that user's Meta connections and everything read through them. Meta gives you a confirmation code to check the status.

Security

• Everything is served over HTTPS.
• Tokens are encrypted before they are stored, with a key of the organization they belong to (XChaCha20-Poly1305), wrapped by a Google Cloud KMS key.
• The database isolates each organization's data from every other's (row-level security).
• Sign-in is by invitation, with roles. Today Ensight reads from ad platforms and changes nothing in them.

Your rights

Under the GDPR you can ask us for access to your data, correction, deletion, restriction, to object to our use of it, and to receive it in a portable form. Write to hi@elim.io; we answer within one month. You can also complain to your data protection authority. We make no decisions about you by automated means alone, and Ensight is not meant for anyone under 16.

Changes

A new version is published here with a new date. If a change matters to data you already gave us, we will tell you by email.