Privacy Policy – aYOUne Companion

aYOUne Companion – Chrome extension by tolinax UG (haftungsbeschränkt) · Last updated: October 4, 2026

Summary: The aYOUne Companion extension does not sell personal data or share it with third parties. Data the extension transmits goes exclusively to the aYOUne servers (*.ayoune.app) under your existing aYOUne account and is subject to the aYOUne Platform Privacy Policy.

1. Who We Are

The aYOUne Companion Chrome extension is developed and published by:

tolinax UG (haftungsbeschränkt), Oberhof 4, 83700 Oberhof, Germany

Represented by: Maximilian Hanrieder

Email: privacy@tolinax.com

Website: https://ayoune.app

2. What Data We Process

2.1 Sign-in Data

When you sign in via login.ayoune.app, the extension receives a key for your session and a key for renewing the session. The session key is held in the browser's memory only; it is never written to disk, never synced to your Google account, and is cleared when the browser closes. The renewal key is stored on this device only and is not synced. These keys authenticate your requests to aYOUne. They are never sent to any third-party server. The extension never sees or stores your password.

2.2 Settings

Your settings (for example position and key figures of the action bar, selected wallboard, features switched on or off, hidden websites) are stored by Chrome and synced across your Chrome installations via your Google account. The extension does not send these settings to aYOUne.

2.3 AI Copilot and Side Panel

The side panel shows the communication area from your aYOUne account as an embedded page from pwa.ayoune.app. Conversations and Copilot requests take place inside that embedded page under your existing aYOUne session and are governed by the aYOUne Platform Privacy Policy. The extension itself does not store conversation history.

Separately, the right-click action "AI Copilot fragen" (ask AI Copilot) sends the text you explicitly select, together with the page address and title, to ai.ayoune.app. "Mit AI übersetzen" (translate) and "Auswahl zusammenfassen" (summarise) first use the AI features Chrome provides on your computer; only if those are not available is the selected text sent to ai.ayoune.app.

2.4 Page Content (Right-click Actions)

When you explicitly trigger a right-click action (e.g. save page as journal entry, ask AI Copilot), the extension reads the current page's address, title and/or selected text and sends it to the matching aYOUne service. Page content is not transmitted to aYOUne without an explicit action by you – the only exceptions are the two lookups described in 2.9, which send a single search term or name to your own aYOUne account and can be switched off.

2.5 Product and Order Data (Marketplace Imports)

When you start an import on Amazon or AliExpress (import product, import orders), the extension reads the product or order data of your pages and transfers it to your aYOUne account. For this, on AliExpress it briefly opens the individual orders in a background tab, and it downloads product images from the marketplace's image servers. When you start "Fill in now" for product backfill, the extension opens the related Amazon product pages in the background. The data is then stored in your aYOUne organization and subject to your organization's data retention rules.

2.6 Phone Number Detection

Phone number detection scans visible text on web pages for phone numbers. All processing is done locally in your browser. Neither page content nor detected numbers are sent to any server. Only when you click the call button next to a number does aYOUne open with that number.

2.7 Notifications

The extension keeps an authenticated live connection to notifier.ayoune.app to receive new notifications immediately, and as a fallback checks crm-api.ayoune.app about once a minute. Only details of your own notifications (title, time, link, urgency) are received, to show desktop alerts and the notification bell. No page content is sent over this connection.

2.8 Lead Import from Connected Sites (Explicit Consent Required)

A small set of allow-listed sites (LinkedIn, Amazon, AliExpress) may suggest a lead to the extension. The extension never creates a record in your aYOUne CRM from such a suggestion silently. It shows you the proposed details in a confirmation window on the page; the lead is sent to crm-api.ayoune.app only after you explicitly click "Lead anlegen" (create lead). If you cancel or close the window, nothing is saved. The suggesting site never receives your sign-in or the result.

2.9 Automatic Lookups on Google and LinkedIn (can be switched off)

On a Google search results page the extension sends the search term to monitoring-api.ayoune.app to show whether and at which position your organization tracks this term. On a LinkedIn profile it sends the person's name to crm-api.ayoune.app to show whether the person already exists in your CRM. Both lookups go exclusively to your own aYOUne account, store nothing, and can each be switched off in the extension settings under "Features".

2.10 Feedback with Screenshot and Dictation

When you start feedback from the side panel, the extension takes a screenshot of the visible tab and lets you annotate it locally. Only if you allow microphone access is your dictation transcribed live via ai.ayoune.app; the audio is transmitted for this purpose but not stored by the extension. Image, text and page address are sent to your aYOUne account only when you click "Absenden" (send).

2.11 Browser Control by the AI Copilot (off by default)

On your request the aYOUne Copilot can operate a browser tab (open a page, read it, click, type). This feature is switched off by default and only becomes available after you enable "Allow the Copilot to control this browser" in the settings. Even then:

• every new control session must be approved by you in a confirmation window (no answer within one minute counts as a refusal);
• the Copilot only works in its own, visibly marked tab with a "Stop" button – never in your other tabs;
• the debugger permission is connected to that tab only for the duration of a single click or keystroke; Chrome shows its own notice meanwhile;
• submitting a form, ordering or paying is only carried out if it has been explicitly approved for that website;
• the content of that tab (page text, screenshots of that tab) is sent exclusively to your aYOUne account to answer your request. The extension only runs its own fixed set of commands – no program code is downloaded or executed.

An idle session ends automatically after two minutes; switching the setting off ends a running session immediately.

3. Data We Do NOT Collect

• Browsing history or visited addresses (except when you explicitly trigger an action)
• Keystrokes or form data (except what the Copilot types into its own tab during a session you approved, see 2.11)
• Personal data from third-party websites (LinkedIn, Amazon and AliExpress data is only taken over when you click an import button, and leads suggested by connected sites are only saved after you confirm, see 2.8)
• Analytics, telemetry or usage data
• Advertising identifiers or device fingerprinting data

4. Where Data Is Sent

Data	Destination	Purpose
Requests	*.ayoune.app	all business operations (CRM, tasks, products, AI, etc.)
Sign-in	login.ayoune.app, auth.ayoune.app	sign-in, session renewal, switching organization
Notifications	notifier.ayoune.app	immediate delivery of your own notifications
Files	uploads.ayoune.app	screenshots, product images

No data is sent to third-party services, advertising networks or analytics providers. Data the extension transmits goes exclusively to the aYOUne infrastructure operated by tolinax UG. For marketplace imports the extension also loads the Amazon or AliExpress pages concerned and their product images (see 2.5); it does not send data from your aYOUne account to these providers.

5. Storage in the Browser

Place	Contents	Scope
Session storage	session key	in memory only, cleared when the browser closes
Synced storage	settings, features switched on or off, hidden websites	synced across your Chrome installations via your Google account
Local storage	renewal key, cached data (wallboard, key figures, customer list, notifications), state of running imports	this device only

Cached key figures and lists are reloaded after 10 seconds to 5 minutes. Signing out deletes all sign-in keys and the entire local storage; your settings are kept.

6. Permissions Explained

Permission	Why it is needed
activeTab	address and title of the current tab when you trigger an action
scripting	elements shown on the page: messages, screenshot picker, import buttons, confirmation windows – shielded from the page's own styling
storage	sign-in, settings and cached data
tabs	completing the sign-in after the sign-in window; recognising the page type for matching actions
contextMenus	the right-click menu
notifications	desktop alerts for new notifications
alarms	regular check for new notifications
sidePanel	the embedded side panel (AI Copilot, phone, video, chat, notifications)
debugger	browser control by the Copilot (2.11): off by default, every session needs your approval, only the Copilot's own marked tab, connected only per click or keystroke
identity	secure sign-in window for your aYOUne account; the extension only receives your aYOUne session, never your Google profile
Access to all websites	the action bar and phone number detection run on all pages; messages and pickers can be triggered on any page via the right-click menu; imports from Amazon and AliExpress

7. Scripts on Web Pages

• Action bar (all pages, off by default – appears only after you switch it on and select a wallboard): shows figures of your organization; shielded from the page, does not read page content, can be disabled per website.
• aYOUne website detection (all pages): reads only the marking aYOUne writes into its own websites, to offer "Edit page"; processed locally, nothing is sent.
• Phone numbers (all pages): processed locally, no data leaves the browser; watches for new content for five minutes after a page loads.
• Google Search (results pages): shows your ranking data (lookup of the search term, see 2.9).
• LinkedIn (profiles and Sales Navigator search): lead import and showing whether the person is in your CRM (lookup of the name, see 2.9).
• Amazon / AliExpress (product and order pages): import when you click the import button.

8. Third-Party Services

The extension does not integrate any third-party analytics, advertising or tracking services. It sends data from your account exclusively to the aYOUne infrastructure (*.ayoune.app) operated by tolinax UG. The only sites outside it that the extension loads by itself are Amazon and AliExpress pages and product images for an import you started (see 2.5).

9. Data Retention

• Local: deleted when you sign out; cached key figures and lists are reloaded after 10 seconds to 5 minutes.
• Server-side: data created through the extension (leads, tasks, journal entries, products, orders) is stored in your aYOUne organization and subject to the aYOUne Platform Privacy Policy and your organization's data retention rules.

10. Your Rights (GDPR)

As an EU-based company, we comply with the General Data Protection Regulation (GDPR). You have the right to:

• Access your personal data
• Rectify inaccurate data
• Erase your data ("right to be forgotten")
• Restrict processing of your data
• Data portability — receive your data in a structured format
• Object to processing of your data

To exercise these rights, contact privacy@tolinax.com.

11. Children's Privacy

The aYOUne Companion is a business tool and is not intended for children under 16. We do not knowingly collect data from children.

12. Changes to This Policy

We may update this privacy policy from time to time; the "Last updated" date above shows the latest change. We inform you about significant changes in the extension or by email.

13. Contact

tolinax UG (haftungsbeschränkt), Oberhof 4, 83700 Oberhof, Germany

Email: privacy@tolinax.com · Website: https://ayoune.app

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/privacy-policy.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.