Privacy Policy

Who we are

INSTRAT360 provides governed AI software and services for enterprises. We are registered in Denmark (CVR 36912758) at Sønderbakken 8, 2820 Gentofte, Denmark, and operate within the European Union. This policy explains how we handle personal data across our website and, where applicable, our products.

For our products, the customer organisation is typically the data controller and INSTRAT360 acts as a data processor under a written data processing agreement. For our website and direct marketing, INSTRAT360 acts as the controller.

What we collect

Website: contact details you submit (such as name, email, and message), and standard technical data needed to operate and secure the site.

Products: the content and account data your organisation chooses to process, governed by your agreement with us. AI interactions and approvals are logged with their author and rationale as part of the audit trail.

How we use it

To respond to enquiries, provide and secure our services, meet legal obligations, and improve the product. We do not sell personal data.

AI-assisted outputs are identified as such and kept distinct from verified facts. Consequential actions follow the approvals and limits your organisation sets: first messages and answers to replies wait for a person, and follow-ups run only in the send mode your organisation chooses.

Legal basis

We rely on legitimate interest for operating and securing our website, consent where required for marketing, contract performance for delivering services, and legal obligation where the law requires retention.

Sharing and subprocessors

We share personal data only with vetted subprocessors needed to run the service, under contract and appropriate safeguards. A current subprocessor list is available to customers on request through the Trust Center.

Where data leaves the EU/EEA, we apply recognised transfer mechanisms and additional safeguards.

Google user data

When you connect a Google account, My AI CCO accesses only the data needed for the features you turn on: your email address (to show which account is connected); sending emails you have approved from your Gmail (gmail.send; we do not read your mailbox); your calendar events (calendar.events, to show and book meetings you approve); and files you select or create through My AI CCO in Google Drive (drive.file). My AI CCO's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We do not use Google user data to train AI models, we do not sell it, and we do not use it for advertising. No person reads it, except with your consent, for security purposes, or where the law requires it. You can disconnect Google at any time in Settings, Connections, or at https://myaccount.google.com/permissions; we then delete the stored access tokens.

CCO browser extension (co-pilot for LinkedIn)

The optional CCO co-pilot extension for Chrome runs only on linkedin.com pages and talks only to My AI CCO (www.my-ai-cco.com), signed in as you. It handles: the public profile details of a person you choose to save (name, headline, company, profile link); the text of a LinkedIn conversation when you choose to capture it into My AI CCO; messages you have approved in My AI CCO, which it places in LinkedIn's message box and, only if you turn on auto-send, sends from your own LinkedIn within your daily limits and working hours; a log of each send (time, recipient, result); and the extension's version and when it was last active. It never reads or stores your LinkedIn password, never runs on other websites by itself (see Web capture below), and stops at once on any LinkedIn security check. This data is processed only to provide the features you use, is not sold, is not used for advertising, and is not used to train AI models. You can pause auto-send in Settings, Connections, or remove the extension at any time in Chrome; saved records can be deleted in My AI CCO. My AI CCO is not affiliated with or endorsed by LinkedIn.

The CCO Chrome extension works beside LinkedIn in your own signed-in browser. It reads only the LinkedIn page you are on, and only when you ask (the one exception is the page address described below): the address and title of a profile or company page when you press "Read this page", the text of the one conversation you have open when you choose to capture it, and the approved message it fills into LinkedIn's own message box. It does not read your feed, your search results, your inbox list or your browsing history. Web capture (optional, off unless your organization turns it on): when you press "Capture this page" on a page that is not LinkedIn, the extension reads only that one page, the one you are on (its title, address, description, visible text and any emails or phone numbers shown, or the visible results of a Google results page you are on), only on your click, and sends only what you choose to save to your CCO organization with the page address as its source; it never runs in the background and never visits pages for you.

Profile capture (CCO extension). When you click "Read this page" or "Save to CRM" on a LinkedIn profile, or the recapture button on a contact in CCO, the extension reads the profile details that are already visible on that page and sends them to your CCO organization: name, headline, current role and company, location, profile URL, the About text (up to fifteen hundred characters), up to five experience roles, up to three schools, up to five skills, up to three recent posts or comments, the line about mutual connections, and the profile photo shown on the page, where the photo is kept as that person's photo and deleted with them. The photo is read from the page you have open; CCO never downloads it from LinkedIn. Nothing is read in the background or without your click, apart from the page address described in the next paragraph. A recapture never overwrites the contact's details: CCO shows what differs and you accept each change yourself. Research on the person and the work email finder run only on your press, and each is metered. CCO may then look up the person's company and a work email through its research sources; guessed emails are marked as unverified.

Live link between CCO and the extension. The extension learns which CCO record (lead, contact or company) you have open in the CCO web app, so its side panel can show the same record, and it learns the address of the LinkedIn profile you visit (the URL only: no page content, no search text, no fragment) so CCO can match it to your own CCO record by that address and offer to open it. The address is sent to your CCO organisation to find the record and is not stored by the extension; nothing else is read in the background. You can switch this off with "Follow CCO" in the side panel. The extension still runs only on linkedin.com pages.

It never asks for, reads, stores or sends your LinkedIn password, cookies or other credentials. It talks only to your own CCO workspace, using your existing CCO sign-in, and what it sends there (the page address and title, a captured conversation, and a log of each action) is used only to show your CRM context, fill your approved message and record sends and replies.

Auto-send is off until you turn it on for your own LinkedIn account. A message is filled only after it has been approved, or, with auto-send on, after CCO's governance checks have passed. Invitations, messages to existing connections and InMail each have their own limits, which you set to fit your own LinkedIn account; LinkedIn's own allowances vary by account and policy.

When you ask for it, the extension can also test a message with the Simulator (how this buyer is likely to read it, scored against a bar, with suggested rewrites) and show a Lens (a reading of the person's likely priorities from their role and your CRM data). Both run in your CCO workspace on your click, use only the public profile details and CRM data already described, are a supplement to your judgement and never a label on the person, and are never used as evidence or to decide anything automatically. A rewritten message goes back to approval before it can be sent.

Each action is checked by CCO right before it happens (your working hours, the recipient's contact permissions and the limits you set), CCO keeps a pause between actions, and it stops on any LinkedIn check or sign-in page and waits for you. You can pause or stop it at any time.

In your browser it keeps only small working state in Chrome's local storage: the CCO address and organisation you chose, today's send counters, the items you set aside for today, and the one message you are about to send. This is replaced as you work and removed when you uninstall the extension. What it sends to your workspace is kept with your workspace's records under the retention described below, in the EU, and is deleted with the workspace. We do not sell this data or use it for advertising or AI training. Use of information received from LinkedIn pages is limited to providing the extension's single purpose and complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Data residency and retention

Personal data is held in the EU with tenant isolation and role-scoped access. Retention for chats, files, memory, and outputs is explicit and, for products, configurable by the customer.

You can request export, correction, or deletion of personal data, and customers can delete a workspace with confirmation.

Your rights

Under the GDPR you have the right to access, rectify, erase, restrict, and port your personal data, and to object to certain processing. You also have the right to lodge a complaint with your supervisory authority (in Denmark, Datatilsynet).

To exercise any of these rights, contact us through the channel below and we will respond within the timeframes required by law.

Security

We apply a NIS2-aligned security baseline: encryption in transit and at rest, strong authentication, dependency and vulnerability management, protected audit logs, and tested backup, restore, and incident-response processes, including a tested 72-hour breach-notification process.

Contact

For any privacy question or data subject request, use the contact option below and mark it for the attention of our data protection function. We will route it to the right team.