Skip to content
aYOUne

Privacy and permissions

Privacy and permissions

This page lists the permissions the Companion requests in Chrome, why it needs them and where data goes. The full text is in the privacy policy.

Where data goes

  • The Companion only talks to aYOUne services and to pages you open yourself or have it open for an import you started (Amazon and AliExpress pages and their product images). All requests to aYOUne use your sign-in and end up in your own organization.
  • Translating and summarising first use the AI features Chrome provides on your computer and only fall back to aYOUne when those are missing.
  • Phone-number validation and the SEO check run on your computer.
  • On its own, the Companion matches only four things against your aYOUne, each only with the feature switched on: the search term on a Google results page, the name on a LinkedIn profile, the product identifiers on Amazon and AliExpress product pages (for your own stock) and – only if you switch on the contact card – the e-mail address, phone number or LinkedIn profile you hover over.
  • The CRM sidebar in Gmail and Outlook (off by default) looks up the sender address in your own account when you open an e-mail; it reads the text of the e-mail only when you click File in CRM.
  • The company badge sends a website's domain only when you click Company in your CRM?. Let AI call and Create as prospect only send after your explicit confirmation.
  • The password vault sends a login only when you click Save, and only end-to-end encrypted. Your master password never leaves your device. The Companion generates new passwords only in your browser.
  • The start page in the new tab reads appointments, key figures, notifications, bookmarks and the state of your AI employees from your own account. Interventions such as approving, answering or pausing go to aYOUne only when you click.
  • Any other content from other sites is only sent when you trigger a feature, such as an import, a screenshot or a question to the Copilot.

Permissions

PermissionWhy
Active tabread the current page when you trigger an action
Scriptingshow buttons, messages and pickers on pages; read page content for imports
Storagesign-in, settings and caches
Tabsrecognise the page type, complete sign-in, take screenshots
Context menusthe aYOUne right-click menu
Notificationsoperating-system notifications
Alarmsfetch new notifications regularly
Side panelthe AI Copilot next to the page
Identitythe secure sign-in window
Debuggerclicks and typing when the Copilot controls the browser (off by default, you approve every session)
Access to all websitesaction bar, phone numbers including the AI call, contact card and company badge on every site, imports from Amazon and AliExpress. The CRM sidebar only runs on Gmail and Outlook on the web and needs no additional permission.

Privacy settings

Under Settings → Data & privacy you can

  • Clear cached data (cached wallboards, key figures, customer lists and notifications on this computer),
  • under Back up settings export your settings to a file and import them again (without sign-in data),
  • use Reset to factory defaults to reset the action bar settings.

Under Settings → Features switch each feature on or off, for all sites or only for some. Off by default are browser control, the contact card, contact enrichment and the CRM sidebar in Gmail and Outlook.

Sign-in log

So that sign-in problems can be sorted out, the Companion keeps the last 25 sign-in steps. The log stays on this computer, contains no keys and is never transmitted; you find it under Settings → Account & organization.

Feedback page when removing

If you remove the Companion, Chrome opens a voluntary feedback page. If you fill it in, only your answers plus language, version, browser and – solely to prevent abuse – the IP address are stored. If you close the page, nothing is stored.

Signing out

Sign out in the popup or in the side panel deletes your sign-in and the Companion's locally cached data. Your settings and the sign-in log are kept.

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain what I need this for What it is good for — and when it is worth it.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Explain to me what I need this for.

1. Which problem does it solve? In one sentence, from my point of view.
2. Three typical situations in which it genuinely helps me.
3. When I do NOT need it — that saves me time.
4. What I can do instead if it is not a fit.

Stick to what the source says. Where it gives nothing, say so openly instead
of guessing.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me set this up Step by step, asking me as you go.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me with a problem Narrow down the cause instead of guessing.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain it in plain words No jargon, from the ground up.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
A checklist to tick off To follow along while you do it.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-permissions.md
The complete collection: https://ayoune.com/en/docs/companion.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)
Leave a comment