Privacy

Effective from 30 October 2026

This page explains which personal data Oddlynew GmbH processes when you visit oddlynew.com, write to us or use Oddlynew: for what purpose, on what legal basis, who receives it, how long we keep it and what your rights are. Questions go to office@oddlynew.com.

1. Controller

Oddlynew GmbH, Vorgartenstraße 210/2/54, 1020 Vienna, Austria, office@oddlynew.com

Full company details are in the imprint.

Organizations keep their own content in Oddlynew and fetch content through connected accounts and tools. Where that content contains personal data about other people, the organization is responsible for it and we process it on the organization's behalf. Please raise questions about such content with the organization first.

2. Visiting the website

Oddlynew runs on Cloudflare's infrastructure. To answer a request, Cloudflare and our code process the connection data every server sees: IP address, requested address, time, browser and device, and the page you came from if your browser sends it.

Every request is logged, including the requested address and everything in it. We use these logs for operations, debugging and abuse prevention. Cloudflare keeps them for at most seven days.

At sign-in and sign-up, Cloudflare Turnstile checks that a person is making the request. Your browser loads a check from challenges.cloudflare.com for this.

The legal basis is our legitimate interest in a secure, working service, Art. 6(1)(f) GDPR.

3. Contact

When you write to us, we receive your email address, your name if you give it, and the content of your message. We use them to reply and to run the business relationship.

The legal basis is Art. 6(1)(b) GDPR where a contract or its preparation is concerned, and otherwise our legitimate interest in orderly communication, Art. 6(1)(f) GDPR.

4. Account and sign-in

For your account we process your email address, your name and profile picture if you provide them, your language, your organizations and roles, and your sign-in methods. You sign in with a one-time code sent by email. For specially protected actions you can also set up an authenticator app.

For every sign-in session we store a shortened IP address, the browser and operating system and the approximate location. We record security events such as denied access, new keys, invitations and access by our team to an account with the IP address and browser identifier, to protect your account and detect abuse.

The legal basis is the performance of the user agreement, Art. 6(1)(b) GDPR, and for the security records our legitimate interest, Art. 6(1)(f) GDPR.

5. Documents, organizations and agents

We store and process what you, your organization and your AI agents create in Oddlynew: documents, versions, comments, uploaded files, memberships and invitations, and the connections of your agents and applications. We also record on which days an account was active, to measure usage.

We use AI language processing to make content searchable and to prepare it for agents. Data fetched through a connection is processed this way only when it is saved as a document or a file (section 6).

When your organization connects external services or has Oddlynew fetch addresses, we send the data this requires to those services on your instruction. Their processing is governed by each provider's own terms. Section 6 explains connected accounts and tools, including your organization's own MCP servers and APIs.

When you connect an agent or an application, we store its name and address, your grants and keys. Each organization keeps an activity log: who changed which document and what was searched for. The log serves to improve the documents and our service; its entries are deleted after 90 days. What your agent reads goes to the AI service you chose for it; its processing is governed by that service's terms.

For signatures we record who requested, opened, signed or declined and when, with the IP address and browser identifier. These details are in the signature record the participants receive with the signed document.

When an organization makes itself public, anyone can read its documents; the directory shows the organization's name, logo and summary. When an organization publishes content, the authors' names and pictures appear with it.

The legal basis is the performance of the user agreement, Art. 6(1)(b) GDPR.

6. Connected accounts and tools

Administrators of an organization can connect accounts and tools to it, such as a YouTube channel, a mailbox or their own MCP server. A connection belongs to the organization. Members with the Writer or Admin role use it through their AI agents; Readers cannot.

Section 6.1 applies to every connection, whatever the service. Sections 6.2 to 6.5 add what applies only to YouTube, Instagram, Google Search Console and your organization's own MCP servers and APIs. For the other services Oddlynew can connect, such as Gmail, Google Ads, Meta Ads, sevDesk or Cloudflare, section 6.1 applies.

6.1 What applies to every connection

Which data: For each connection we store its access tokens or keys in encrypted form, the id and name of the connected account, who connected it and when, the consent text shown at the time, a label and a note an administrator can add, and the connection's settings, such as its access level and which changes need confirmation. Our hosting and database providers also encrypt this stored data at rest.

We fetch data from a connected service only when a member or their agent asks for it. The exceptions are what a connection needs to be set up and to keep working, such as the account's id and name when it is connected and, for some services, a regular check that access is still granted or a renewal of the access token; sections 6.2 to 6.5 name them for their services. We fetch data over encrypted connections and pass it to the agent that asked. What an agent fetches or creates through a connection stays in Oddlynew only if it is saved as a document or a file: by a member, by their agent, or by a tool that saves its output there when the agent asks. Such a document or file is your organization's own content and is kept like any other (section 5). Otherwise we keep no copy of it and do not make it searchable. What we keep about changes is described below, and section 6.5 names what we keep about your own MCP servers and APIs. Connecting in the browser uses a short-lived cookie (section 13).

An agent can also make changes through a connection, as far as the access level allows. Oddlynew sorts every kind of change into one of four levels by how far it can be undone (for your own MCP servers and APIs, see section 6.5). By default, changes at the two higher levels, such as posting a comment or sending an email, wait for an administrator's confirmation. Changes at the two lower levels, such as hiding a comment or labelling an email, run at once. Administrators can change this for each connection; a few changes always wait. While a change waits, we store it with its text and the purpose the agent gave for it. It waits until an administrator confirms or rejects it or the agent withdraws it, unless an administrator has set a time after which waiting changes expire. For a change that waited, we also store its result. For a change that runs at once, we store at most its result.

Why: We use this data only for the organization that made the connection, and only to do what its members ask their agents to do with it. We never sell it or pass it to data brokers. We never use it to train AI models or for credit decisions. We never use it for advertising. A connection to an advertising service, such as Google Ads or Meta Ads, serves only the ads your own organization runs there. Our team does not fetch data from your connected accounts. It sees their names and the changes made through them only when your organization asks us for help or you send us a request, for security, or where the law requires it.

Legal basis: The performance of the user agreement, Art. 6(1)(b) GDPR. For the proof of consent, the log of the changes and security, our legitimate interest, Art. 6(1)(f) GDPR. Personal data of other people that an agent fetches, such as names and comments, is processed on your organization's behalf (section 1).

Who receives the data: What an agent fetches goes to the AI service the member chose for it; its processing is governed by that service's terms. Each connected service receives the requests made through its connection, and its provider processes data on its side under its own terms. Cloudflare and PlanetScale process the stored data for us (section 14). No one else receives the data, except authorities where the law requires it.

How long: An administrator can disconnect a connection at any time under Integrations. We then delete its access tokens, keys and other secrets at once, and Oddlynew no longer uses the connection. If the same sign-in still serves another connection of your organization, such as a second Google Ads account, the sign-in's access tokens stay until that connection is disconnected too. Within seven days of the disconnect we delete everything else we stored about the connection: the account's id and name, the label and note, and all changes made through it with their text and results, also those still waiting. We keep only a record as proof of consent: who connected the account, when, the consent text shown, and the connection's access level and settings, without the account's id or name. We keep the record for at most three years after the disconnect. When an organization is removed for good (section 15), its connections are disconnected and their data goes the same way. We then ask no provider to revoke access.

Until a connection is disconnected, we delete the results of changes that run at once after 30 days. Changes that waited for confirmation stay stored with their text and result, also after they are confirmed, rejected, withdrawn or expired, until the connection is disconnected or we delete them on a request under your rights (section 16).

A connection's data is deleted in one of two ways. The first is a disconnect by an administrator, as described above. For YouTube and Google Search Console, a revocation at Google leads there too: if the account holder revokes Oddlynew's access at Google and nobody reconnects the account, we disconnect the connection and delete its data at most 30 days later. Sections 6.2 and 6.4 explain this. The second is a request under your rights (section 16): write to us at office@oddlynew.com. We then delete the data you ask us to delete. Unless you limit your request to certain data, that is everything we hold about you, including the connected accounts that belong to you, such as your own YouTube channel, mailbox or Instagram account, and the other connections you made, unless their account belongs to the organization. If an account of yours is not the one you sign in to Oddlynew with, you show us that it is yours, for example by putting a short code we send you into the YouTube channel's description or the Instagram account's bio; oddlynew.com/data-deletion explains how. We delete the data of these connections within seven days after we have verified your request. We delete everything else within one month of your request, apart from what we keep longer for the periods in section 15, such as invoices and security records. If a connection is still active, we disconnect it first. Of these connections we keep only the record as proof of consent. Changes already made at the other service stay there. If you cannot disconnect a connection yourself, for example because you are not a member of the organization, use this request.

A connection you made to an account that belongs to the organization, such as a company mailbox or the organization's YouTube channel, stays with the organization. We only remove you from it. The organization's administrators confirm to us which accounts belong to it. Within seven days after we have verified your request, the connection no longer names you as the person who connected it. Its proof of consent then keeps when the account was connected and the consent text shown, but no longer who connected it. If the connection is still active, it shows “Needs reconnect” until an administrator connects the account again.

6.2 YouTube (Google)

Oddlynew uses YouTube API Services. Using YouTube through Oddlynew is subject to the YouTube Terms of Service at www.youtube.com/t/terms. When an administrator connects a channel, the connect page links this notice, the YouTube Terms of Service and the Google Privacy Policy. How we store, use, share and delete YouTube data is set out in section 6.1; this section adds what applies only to YouTube.

What an agent can read and do depends on the access level the administrator chooses:

Insights only: the channel's details, its videos with their statistics, and YouTube Analytics reports, without comments
Community management: in addition, the comments and replies on the channel's videos with each author's name, posting comments and replies as the channel, and editing or deleting the channel's own comments

When a channel is connected, we receive access tokens from Google and store the channel's id and name. Posting, editing and deleting comments wait for an administrator's confirmation by default.

While a connection works, we check at least every 30 days that access is still granted. If access is revoked at Google and nobody reconnects the channel, we disconnect it and delete its data as on a disconnect, at most 30 days after the revocation. If a connection shows “Needs reconnect”, for example because the member who connected it left the organization, and nobody reconnects it within 30 days, we disconnect it and delete its data as on a disconnect.

When an administrator disconnects a channel, we also ask Google to revoke Oddlynew's access. We do not do this while the same channel is still connected in another organization in Oddlynew, or for an older connection made through the Google sign-in that Oddlynew also uses for other Google services, because that would end those connections too. You can always revoke Oddlynew's access yourself in your Google account's security settings at security.google.com/settings/security/permissions.

Google processes the data on its side as an independent controller, under the Google Privacy Policy at www.google.com/policies/privacy. Oddlynew's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

To have YouTube data deleted in Oddlynew, an administrator disconnects the channel, or the channel's owner revokes Oddlynew's access at Google, as described above. If you made the connection or the channel is yours, and you cannot disconnect it, for example because you are not a member of the organization, ask us to erase your data under your rights (sections 6.1 and 16). We then delete the channel's data within seven days after we have verified your request. If you made the connection but the channel belongs to the organization, we instead only remove you from the connection, as section 6.1 explains. For questions and complaints, write to us at office@oddlynew.com. Deleting data in Oddlynew does not delete anything on YouTube. To delete data on YouTube, use YouTube itself.

6.3 Instagram (Meta)

This section covers Instagram professional accounts. When an administrator connects an account, we receive an access token from Meta together with the account's id and username. The connect page links this notice, the Instagram Terms of Use at help.instagram.com/581066165581870 and the Meta Privacy Policy at www.facebook.com/privacy/policy. Meta processes the data on its side as an independent controller. How we store, use, share and delete Instagram data is set out in section 6.1; this section adds what applies only to Instagram.

What an agent can read and do depends on the access level: the account's profile and follower numbers, its posts with captions and statistics, insights with audience breakdowns, and at higher levels the comments and replies on its posts with each author's username. At the highest level it can also post comments and replies as the account, and hide or delete comments on its posts. It never publishes posts or changes captions.

Posting comments and replies and deleting comments wait for an administrator's confirmation by default. Hiding or unhiding a comment runs at once by default.

While a connection works, we renew its access token at Meta at least every 30 days, which also checks that access is still granted.

We do not revoke Oddlynew's access at Instagram when an administrator disconnects the account. You can remove Oddlynew in your Instagram settings, which stops our access but deletes nothing in Oddlynew. The account's data stays until an administrator disconnects the account or we delete it on a request under your rights (sections 6.1 and 16).

To have Instagram data deleted in Oddlynew, an administrator disconnects the account. If you made the connection or the account is yours, and you cannot disconnect it, for example because you are not a member of the organization, ask us to erase your data under your rights (sections 6.1 and 16). We then delete the account's data within seven days after we have verified your request. If you made the connection but the account belongs to the organization, we instead only remove you from the connection, as section 6.1 explains. How you show that the account is yours is explained at oddlynew.com/data-deletion.

6.4 Google Search Console

With a Google Search Console connection, an agent can read the Search Console data of every property the connected Google account can see:

the list of properties, with the account's permission for each
search performance: clicks, impressions, click-through rate and position, by date, search query, page, country, device and search appearance
submitted sitemaps with their status
URL inspection results, such as index status, canonical address, crawl details, mobile usability and rich results

The search queries are words people typed into Google Search. The connection can only read: it never adds or removes a property or a sitemap and never verifies a property, so nothing waits for confirmation. When the account is connected, we receive access tokens from Google and store the Google account's id and email address; the email address is the connection's name.

Oddlynew uses the Google Search Console API for this. The connection signs in through the Google app that Oddlynew also uses for other Google services, such as Gmail and Google Ads.

While a connection works, we check at least every 30 days that access is still granted. If access is revoked at Google and nobody reconnects the account, we disconnect it and delete its data as on a disconnect, at most 30 days after the revocation. If a connection shows “Needs reconnect” and nobody reconnects it within 30 days, we disconnect it and delete its data as on a disconnect.

When an administrator disconnects the account, we delete its access tokens at once. We do not ask Google to revoke Oddlynew's access, because on this shared Google app that could also end other connections of the same Google account. You can always revoke Oddlynew's access yourself in your Google account's security settings at security.google.com/settings/security/permissions.

6.5 Your own MCP servers and APIs

Administrators can connect any MCP server or API to their organization by its address, such as a server your organization runs itself or one a provider offers. The address must use https and point to a public server. An agent can prepare such a connection, but it starts only when an administrator completes it in Oddlynew.

Credentials: Depending on how the server signs in, an administrator enters a key that we send in a header or in the address, adds further fixed headers, or signs in at the provider. For a sign-in we store the access tokens we receive and, if the organization registered its own app at the provider, the app's client id and client secret. If an agent proposes an API connection with a key, we store the key until an administrator confirms the connection, and delete it when the proposal ends. We never return the key to the agent.

How we protect them: We encrypt every key, token, client secret and secret header we store (AES-256-GCM). A master key, kept as a secret on our servers, protects the data keys we encrypt them with. Each value is bound to its organization and to the connection or sign-in it belongs to, or, for a key an agent proposed, to that proposal, so a copy in another place cannot be decrypted. Only our servers decrypt a value, and only when they need it to reach the server or its sign-in service. Oddlynew never shows a stored value again in full, to you, your agents or our team. For a client secret of at least 20 characters, we show only its last four characters. Our records name who set or changed a credential and when, never its value. If a server's error message contains the credential, we remove it before we pass the message on, or we do not pass the message on.

What goes where: When an agent calls a tool or an operation, we send the server the tool's name and the arguments the agent gave, together with the credential. We send them only to the server's own address; for an API, only below its base address. The server's operator processes what it receives under its own terms. The server sees one account for the whole organization: the one the administrator connected. Apart from calls and signing in, Oddlynew contacts an API only when it is connected and when an administrator tests the connection, and an MCP server only to read its list of tools and its icon: when it is connected, when an administrator refreshes the list, and when an agent calls a tool that is not on the list yet. While the connection exists, we keep its address, the list of tools with their descriptions and the server's instructions, for an MCP server a copy of its icon, and for an API the description it was connected with. Apart from the results of changes that section 6.1 describes, we keep no copy of what a call returns.

Changes: Tools the server marks as read-only, and API operations that only read (GET and HEAD), run as reads. Every other tool or operation counts as a change and waits for an administrator's confirmation by default. The exception is an MCP tool the server marks as not destructive and as acting only inside its own system: it runs at once by default. Administrators can change this for each connection and each tool.

Disconnecting: On a disconnect we delete the keys, tokens, client secret and headers at once, and everything else within seven days, including the list of tools, the icon, the API description and the app registration, as section 6.1 explains. If Oddlynew registered itself with an MCP server's sign-in service when signing in, and no other connection uses that registration, we also ask the sign-in service to revoke the token, if it offers a way to do so. For an API connected through a sign-in, an administrator can instead choose “Revoke at the provider” on the connection's page, where the provider offers it. Otherwise, you revoke the access in the provider's own settings.

7. Payments

Paid plans are handled by Stripe. You enter payment details directly with Stripe. We receive and store name, email address, billing address, your VAT id if you give one, plan, payment status and payment method details such as a card identifier and the card type, but never the full card number. Stripe calculates the tax for us. We also use a card check to prevent abuse of free allowances.

The legal basis is Art. 6(1)(b) GDPR, statutory retention duties under Art. 6(1)(c) GDPR, and for abuse prevention our legitimate interest, Art. 6(1)(f) GDPR.

8. Emails

We send you emails that belong to the service: sign-in codes, security notices, invitations, welcome messages and notifications, for example about comments, signatures, reports, billing and expiring keys. We use an email delivery service that processes the recipient address and the message content. The legal basis is Art. 6(1)(b) GDPR.

9. Reports about content

When you report content through oddlynew.com/report, by email or through an AI agent, we process your data as the controller.

Which data: your name and email address (optional for notices about child sexual abuse material); whether you report as an individual, for an organization, as a rights holder or on their behalf, or as an authority; the addresses (URLs) of the reported content; your explanation; your statement that, to the best of your knowledge, the information is accurate and complete; the IP address the notice came from. If you report through an AI agent, we take the name and email address from the signed-in account. For each notice we also store the reference number, the time and our decision.

Why: to confirm, review and decide on your notice, to inform you and the people affected, and to show authorities and courts what we did; to detect and stop misuse of the reporting channel, such as automated mass reports.

Legal basis: For handling the notice, Art. 6(1)(c) GDPR together with Arts. 16 and 17 of the Digital Services Act (Regulation (EU) 2022/2065). For the IP address, Art. 6(1)(f) GDPR; our legitimate interest is to protect the reporting channel from misuse and overload without blocking genuine notices. We need the details in the form for your notice to be complete. Without an email address, we cannot send you a receipt or our decision.

Who receives the data: the people whose content we restrict learn your name only when that is strictly necessary, typically for notices about intellectual property; otherwise they only learn that there was a notice. Authorities and courts, when the law requires it, for example for a threat to life or safety, for terrorist content, or on an order from an authority or a court. Service providers who process data for us (section 14), in particular for hosting and email delivery. Our public log of removed content never contains data about notifiers.

How long: case records three years after the case is closed; after that, we delete the personal data and keep only anonymous counts. IP addresses 30 days.

10. Product analytics

To see where pages and actions fail, are slow or get stuck, we also measure the use of Oddlynew ourselves: which page is opened, how long it stays open and how far it is scrolled, which control is clicked, including repeated clicks and clicks without effect, which form is submitted and which error is shown, plus load times and steps such as sign-up, invitation, comment or search. For an agent connected through MCP we record which kind of application it is connected through, such as Claude or ChatGPT, which tool it calls, how long the call takes and whether it succeeds.

If you are signed in, we record your role, the identifier of your active organization and, instead of your account, a pseudonymous identifier our server derives from your account with a secret key; your account itself or your email address is not in the data. Both serve only our internal product analytics, never to monitor behaviour or performance. We do not record document content, comments, input, names, email addresses, search terms, page titles or an agent's code; a page is recorded only as a template (such as “document”), never with its address or a code in it. We set no cookie for this and store nothing in your browser.

If you are not signed in, we link consecutive requests through a key our server derives from IP address and browser identifier with a random daily value. The daily value is deleted after 48 hours; the IP address itself is not stored. The data stays with Cloudflare, is not passed on and is not linked across websites.

The legal basis is our legitimate interest in a working, improving product, Art. 6(1)(f) GDPR. If your browser sends Global Privacy Control or “Do Not Track”, we record nothing. You can also object at any time by emailing our privacy address.

11. Error reporting

When an error occurs, the website and servers send an error report to Sentry, in its EU data region. The report contains the technical circumstances of the error, the browser and the requested address. We remove sign-in and invitation keys from addresses before sending. The legal basis is our legitimate interest in a working service, Art. 6(1)(f) GDPR.

12. Audience measurement with Google Analytics

To understand how visitors find Oddlynew and which campaigns work, we count with Google Analytics the page views of visitors who are not signed in, and the steps of a purchase: started, completed and cancelled. Pages you open while signed in are not sent to Google. Our server sends these events to Google itself, through Cloudflare. Your browser loads no Google script for this, and we place no cookie or any other entry in your browser for it.

Google receives the requested address including campaign details such as utm_source and the click id of a Google ad, only the name of the website you came from, your language setting and, for a purchase, the plan, the amount and an order number, with only our website's address instead of the page. We do not pass on your IP address or your browser identifier. We store nothing in your browser that recognizes you. We send nothing for addresses that contain a sign-in or invitation key, or for requests from search engines and other programs.

The legal basis is our legitimate interest in improving the website and our marketing, Art. 6(1)(f) GDPR. You can object at any time: if your browser sends the Global Privacy Control signal, we send nothing to Google for your requests.

13. Cookies and browser storage

Oddlynew sets cookies the service needs: for your sign-in, language, theme, time zone and the organization you used last, for returning you to the right page after sign-in, for short status messages and, only for the duration of each step, for sign-in, invitations and connecting external services. In your browser's local storage we keep technical state, for example for the document editor and forms you have started.

This storage is strictly necessary for the service you asked for and needs no consent (§ 165(3) Austrian Telecommunications Act 2021).

We load embedded content from other providers, such as videos, only after your click. The provider then receives your IP address and can set its own cookies.

14. Recipients

We use service providers that process data on our behalf. Currently these are:

Cloudflare: hosting, file storage in the EU, logs, abuse prevention, AI language processing, product analytics, embedding the audience measurement, PDF generation and image processing
PlanetScale: database, EU region (Frankfurt)
turbopuffer: search index and AI language processing for search, EU region (Frankfurt)
Stripe: payment processing
Resend: email delivery
Sentry: error reporting, EU data region
Telegram: internal operational messages to our team, for example when a new agent application registers
Google: audience measurement with Google Analytics

Beyond that, data only goes to the AI service each member chooses for their agent, to external services your organization connects itself (section 6), and to authorities where we are legally required.

Some of these providers or their group companies are located outside the European Economic Area, in particular in the USA. We base such transfers on an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework, or on standard contractual clauses.

15. Retention

We keep personal data as long as its purpose requires and review this every year. Some fixed periods:

Server logs at Cloudflare: at most seven days
Documents in the trash: 30 days, then they are deleted
Connected accounts and tools: access tokens and keys until the connection is disconnected, or, for a sign-in that serves several connections, until the last of them is disconnected; everything else at most seven days after the disconnect, for YouTube and Google Search Console also at most 30 days after access is revoked at Google (section 6); the proof of consent at most three years after the disconnect
Changes through a connection until it is disconnected: results of changes made at once 30 days; changes that waited for confirmation, with their text and result, until the connection is disconnected or we delete them on a request under your rights (section 16)
Security records: at most two years, denied access 180 days
Product analytics events: at most 27 months in pseudonymous form; after that we remove the key and the organization and shorten the time to the day, so only data without personal reference remains
Sign-in sessions: 90 days after they end
An organization's activity log: 90 days
Reports about content: three years after the case is closed, the IP address 30 days
Events in Google Analytics: at most 14 months
Invoices and accounting records: as long as the law requires, generally seven years

An organization can be deleted by its administrator; it is removed for good after 30 days. Its connections are then disconnected, and their data is deleted as section 6 explains. You request the deletion of your account by email. Billing and usage records and security records are kept for their own periods.

16. Your rights

Under the GDPR you have the right of access, rectification, erasure, restriction of processing and data portability, and the right to object to processing based on our legitimate interest. You can withdraw consent at any time with effect for the future. A request to erase your data also covers the connections you made and the connected accounts that belong to you; section 6.1 explains how we handle it, also for a connection you made to an account of the organization, and how else a connection's data is deleted.

Write to us at office@oddlynew.com. You can also lodge a complaint with a supervisory authority; in Austria that is the Datenschutzbehörde, Barichgasse 40-42, 1030 Vienna, www.dsb.gv.at.

17. Changes

We update this notice when Oddlynew, our service providers or the law change. The version published here applies. Before we use data from connected accounts in a new way or access new kinds of data, we inform administrators and ask them to agree, for example by connecting again.