The short version
- No cookies of any kind, and no consent banner because there is nothing to consent to.
- No analytics, no tag manager, no tracking pixel, no advertising, no A/B testing.
- No fonts, scripts, images, maps or embeds loaded from other servers.
- No contact form, no newsletter, no account, no login, no payment on this website.
- No data of yours is uploaded by the free check — it never leaves your device.
-
The hosting provider that serves these pages records IP addresses and request metadata in
its server logs, as every web server does. That is described in full below.
-
If you write to contact@neopiq.ai or telephone us,
we process what you send in order to answer you.
-
ChatAdmin is a separate service from this website. If you sign in to it, it processes your
Microsoft sign-in identity, your conversations and records about your organisation, and it
reads your Microsoft tenant under your own sign-in — see
ChatAdmin.
Who is responsible
The controller for the processing described here — the party that decides why and how
it happens:
- Controller: Neopiq GmbH
- Address: c/o Ludwig Limbeck AG, Sinserstrasse 67, 6330 Cham, Switzerland
- UID: CHE-345.914.300
- Contact for data-protection questions: contact@neopiq.ai, or by telephone on 0041 78 223 6716
- Data protection officer: none is appointed. Swiss law makes a data protection
adviser voluntary for a private company (revFADP Art. 10), and the GDPR’s duty to
appoint one is not triggered by processing of this scale — nor, on the assessment
under which law applies, does the GDPR apply here at all.
Data-protection questions go to the contact address above and are answered by the
management directly.
- Representative in the EU under GDPR Art. 27: for this website none is needed, because on
the assessment under which law applies the GDPR does not apply to it.
A Swiss controller needs no separate Swiss representative. For now ChatAdmin accepts new
organisations from Switzerland and the United States only. Before it accepts organisations
from the European Union, the European Economic Area (including Liechtenstein, Iceland and
Norway) or the United Kingdom, we will appoint representatives under GDPR Art. 27 and UK GDPR
Art. 27 and name them here.
The same details, with the VAT position, are in the
imprint.
ChatAdmin processes data about customers’ staff and about customers’ Microsoft
tenants, and for managed service providers about the tenants of their own customers. Neopiq
processes what ChatAdmin reads from a customer's tenant, what users type and the conversation
transcripts on behalf of the customer, which decides about that processing. Neopiq itself
decides about, and is responsible for, the sign-in identities, the organisation and member
records, the plan and billing records and its own logs. Questions go to the contact address
above.
Which law applies
Neopiq GmbH is established in Switzerland, so the revised Swiss Federal Act on Data
Protection (revFADP) applies to the processing described here, and the competent
supervisory authority is the Swiss Federal Data Protection and Information Commissioner
(FDPIC) in Bern.
Whether the EU GDPR applies in addition turns on its Art. 3(2): it reaches
a company outside the EU only if that company offers goods or services to people in the EU,
or monitors their behaviour. Our assessment is that this site does neither, and that
the GDPR does not apply to it. The site is addressed to businesses that
administer Microsoft tenants, not to consumers; ChatAdmin’s trial and plans are
offered to organisations based in Switzerland and the United States. Nothing on the site
itself can be bought, ordered or signed up for; the free check runs entirely in your browser and sends us nothing; and
there is no cookie, analytics or tracking of any kind, so no behaviour is monitored. A
website being reachable from the EU does not, by itself, bring it within Art. 3(2).
This notice is nevertheless written to the fuller GDPR field list throughout: the rights
below are stated in their broadest form, and legal bases are given for each processing
operation. That is deliberate — it costs nothing, and it means nothing on this page
becomes wrong if a court or authority ever reads Art. 3(2) more broadly than we do. The
assessment covers this website only; for ChatAdmin, see the next paragraph.
The assessment above was made for this website. ChatAdmin is a separate service that
organisations sign up for themselves. For ChatAdmin we apply the Swiss Federal Act on Data
Protection and, where ChatAdmin processes personal data of people in the European Union or the
United Kingdom, the GDPR and the UK GDPR as well.
What this site does not collect
These are properties of how the site is built, not promises about how it is administered, so
you can verify them rather than trust them.
No cookies and no tracking
No cookie is set by these pages, and nothing is written to local storage. The only thing
kept in your browser is the time of the last wake request (described next), in this
tab’s session storage, which the browser clears when the tab closes. There is no analytics service, no tag manager, no tracking pixel, no
advertising network, no social plug-in and no cross-site identifier. You are not
profiled, and no automated decision-making takes place.
No tracking scripts
Every script is served from this site; no page loads a script from anywhere else. The home
page and the demo page (the demonstration) run scripts that send nothing anywhere and store
nothing.
ChatAdmin pauses when nobody uses it and takes up to half a minute to start. So that it is
ready when you open it, every page with a sign-in action sends, after it has loaded, one
request to the ChatAdmin service asking it to start: no cookie, no identifier, no content,
and its answer is not read. A tab sends it at most once every five minutes, and not at all
when your browser asks to save data. The page that opens ChatAdmin asks the service whether
it is ready, the same way, and then forwards you to it. The site’s own build check fails
the build if any other script makes a request or uses browser storage, or if these requests
go anywhere but the ChatAdmin service.
No third-party requests
The only file these pages load is one stylesheet served from this same site. There is no
content delivery network, no remote web font, no remote image, no embedded video and no
map. Because nothing is requested from another company’s server, no other company learns
your IP address from your visit here. The one request beyond this site goes to the ChatAdmin
service (the wake request above), which Neopiq runs in Microsoft Azure, Switzerland North;
like any web server it sees the IP address the request comes from.
No forms and no accounts
There is no contact form, no sign-up, no newsletter subscription, no login and no
payment on this website. Nothing on these pages submits anything anywhere, so browsing
gives us no name, e-mail address or message to receive, store or lose.
There is a published e-mail address and telephone number, but they are ordinary
contact routes, not a form: nothing is collected unless you choose to write. See
writing to us.
Signing in, plans and payment belong to ChatAdmin, a separate service that
“Open ChatAdmin” leads to; see ChatAdmin.
You can confirm all of this in about a minute: open your browser’s network tab and load
any page here, or read the page source. What you will see is the document itself and one
stylesheet.
Hosting and server logs
This site is published with GitHub Pages, so GitHub’s servers deliver these pages to
your browser. Like every web server, they process the technical data that a request
necessarily contains in order to answer it, and record it in server logs. That typically
includes:
- the IP address the request came from;
- the date and time of the request;
- the address of the page or file requested, and the response status;
- the amount of data transferred;
- the browser and operating system reported by your browser (the user-agent string);
- the referring page, if your browser sends one.
This is the only processing of personal data that actually happens when you use this site,
and it is unavoidable: a server cannot send a page to an address it does not have. It is used
to deliver the site, to keep it available, and to detect and defend against attacks and
abuse. It is not used to identify you, to build a profile, or for marketing, and it is not
combined with anything else — there is nothing else.
Legal basis
Where the GDPR applies, the legal basis is Art. 6(1)(f) — the legitimate interest in
presenting a functioning, stable and secure website. Where Swiss law applies, the same
processing is justified by the overriding private interest in the secure operation of the
site. You can object to processing based on legitimate interests; see
your rights below.
Who processes it
GitHub acts as the hosting provider for this site and, in data-protection terms, as a
processor acting for the controller named above. The logs are generated and held by GitHub as
part of operating its platform. We do not receive these logs, do not have an interface to
query them, and cannot look up individual visitors.
The processor agreement for this is GitHub’s Data Protection
Agreement, which forms part of the service terms under which this site is hosted
and which GitHub publishes on its website. It commits GitHub to process personal data only
to provide the service, to keep it confidential and secure, and to the transfer safeguards
described in the next section. We have not negotiated anything beyond it, and nothing
beyond it is needed for a site that consists of static pages.
How long the logs are kept
The logs are kept by GitHub, not by us, on GitHub’s own schedule. GitHub’s
documentation states that visitor IP addresses of Pages sites are logged and stored for
security purposes; it does not publish a fixed number of days for these logs, and its
privacy statement limits retention to what the collection purpose requires. We hold no
copy at all, so there is nothing on our side to be kept or deleted.
Transfers outside your country
GitHub is a company established in the United States and operates a global network, so the
server-log data described above may be processed outside Switzerland and outside the European
Economic Area. There is no other recipient: nothing else on this site sends anything anywhere.
The safeguard for that transfer is the EU standard contractual clauses
(Commission Implementing Decision 2021/914), which Switzerland recognises for Swiss
transfers subject to the FDPIC’s adaptations, and which are incorporated into
GitHub’s Data Protection Agreement — the same published document named under
hosting above, obtainable from GitHub’s website. GitHub is in
addition certified under the Swiss–U.S. Data Privacy Framework. It is worth being
precise about what actually travels under these safeguards: the request logs and IP
addresses described above, and nothing more. No content of yours is transferred by this
site, because none is collected — the free check uploads nothing.
ChatAdmin is different. Neopiq runs it, and keeps its records, in Microsoft Azure in the
Switzerland North region. Its language model is provided by Anthropic, which receives the
conversation as described under ChatAdmin and processes it in the
United States, under the EU standard contractual clauses with the Swiss addendum recognised by
the FDPIC, which are part of Anthropic's data processing addendum. Payments, once they open, go
through Paddle.com, whose checkout gives its address in London, United Kingdom; Switzerland
recognises the United Kingdom as providing adequate protection. A copy of these safeguards can
be requested at the contact address.
If you write to us
A contact route exists: the e-mail address and telephone number published in the
imprint. This section describes what happens if you use
one.
-
What is processed: whatever you put in your message or say on the call
— typically your name, your e-mail address or number, and the content of your
enquiry. Nothing else is collected, and nothing is required of you beyond the address we
need in order to reply.
-
Why: to read your message, answer it, and keep the thread coherent if
the exchange continues.
-
Legal basis: where the GDPR applies, Art. 6(1)(b) for enquiries that are
pre-contractual and Art. 6(1)(f) — the legitimate interest in answering people who
write to us — for everything else. Under Swiss law no separate justification is
needed to process data you send us for the purpose you sent it for.
-
What is not done with it: it is not used for marketing, not added to any
mailing list — there is none — and not passed to anyone outside the company.
Who carries it
E-mail to our contact address is carried and stored by a commercial e-mail hosting
provider acting as our processor, under its standard data-processing terms. The published
telephone number is a Swiss mobile number carried on a Swiss mobile network, and calls are
not recorded. Large e-mail providers routinely operate infrastructure outside Switzerland
and the EEA, including in the United States; for any correspondence processed there, we
use only providers whose terms include the EU standard contractual clauses, as recognised
by Switzerland with the FDPIC’s adaptations. We name the category rather than a
brand because the provider may change; the safeguard is the commitment, and it will not.
Ask at the contact address and we will tell you which provider holds your thread.
How long it is kept
Correspondence is kept while an exchange is open and then for up to 24
months after the last message, so that the thread is still there if you come back
to the same matter; after that it is deleted. The one exception is correspondence that
becomes part of a contract or matters for the books, which Swiss accounting law (OR
Art. 958f) requires us to keep for ten years.
The free check runs in your browser
Nothing is uploaded
Your CSV files never leave your device
The free planning check is a web page that reads the CSV files you choose, analyses them
and displays the findings — all inside your browser, on your own machine. It has no
network capability by construction: no upload, no background transmission, no telemetry, no
error reporting, no “optional” cloud step.
Your files are never sent to us, never sent to the hosting provider beyond the ordinary
request that fetched the page itself, and never stored by this site. Nothing is written to
cookies, local storage, session storage or any browser database. The analysis lives in the
page while the tab is open; closing the tab is the delete button.
Because your item master, vendor list and receipts are commercially sensitive, this is
deliberately verifiable rather than merely promised: open the browser’s network tab
while the check runs and nothing is requested, or disconnect from the network first and it
still works.
Because the tool never transmits your data, we are not a controller or a processor of
anything it reads. Whatever is in those exports remains entirely under your own control, on
your own equipment, and under whatever obligations already apply to you as its controller.
ChatAdmin
ChatAdmin is Neopiq’s product for administering Microsoft Entra, Microsoft 365,
Microsoft Azure and Microsoft Power Platform by conversation. It is a separate service from
this website: “Open ChatAdmin” on these pages leads to it. Organisations sign in
with Microsoft and use it in their own Microsoft tenant, and managed service providers use it
for the tenants of the customers they manage. This section says what ChatAdmin processes when
you use it, where it is kept and how long. All of ChatAdmin’s own records are kept in
Neopiq’s Microsoft Azure storage in the Switzerland North region, where ChatAdmin
also runs.
Signing in with Microsoft
-
You sign in with a Microsoft work account. ChatAdmin asks Microsoft for your identity only,
not for access to anything in your tenant, and learns your name, your sign-in name, your
tenant id and Microsoft’s internal identifier for your account. Personal Microsoft
accounts are refused.
-
The sign-in token Microsoft issues is checked once and then discarded; it is not stored.
-
ChatAdmin sets one cookie,
chatadmin_session: a random identifier with nothing
inside it, valid for at most eight hours. Behind it ChatAdmin keeps a session record (your
name, sign-in name, tenant id, internal identifier and the time you signed in), so that a
restart of the service does not sign you out. An expired session record is deleted at the
latest a day after its last use. In the browser, ChatAdmin keeps the conversation’s
identifier and the Microsoft sign-in library’s tokens in the tab’s session
storage, which the browser clears when the tab is closed.
-
Your name, sign-in name and tenant id are shown on every approval card and recorded in the
conversation’s transcript, so that every decision says who made it.
Reading your Microsoft tenant
-
ChatAdmin reads a customer’s tenant only under the signed-in person’s own
Microsoft sign-in, after an administrator of that tenant has consented to ChatAdmin’s
permissions. It never has more rights than the person using it. ChatAdmin's software only
reads in customers’ tenants; changes are not open for customers. Some Microsoft
permissions it asks for are not limited to reading: for Azure, Power Platform and Dataverse,
Microsoft offers only permissions that also allow changes within your own rights, and two
Microsoft 365 permissions (Files.Read.All, Sites.Read.All) would allow reading the content of
files you can read. ChatAdmin does not use them for changes or for file content; that limit
is in ChatAdmin's code. Some areas ask for their own consent the first time you use them.
-
The Microsoft access ChatAdmin obtains for a request is used for that request and is not
stored.
-
What is read depends on what you ask: for example users, groups, role holders, licences,
sign-in error codes, directory audit entries, Conditional Access policies, consent settings
and sensitivity-label definitions; mailbox sizes and permissions, Teams and SharePoint
membership, Teams app status and usage reports with per-user activity counts; Azure resources
and costs; Power Platform environments and Copilot Studio agents; Intune devices with their
names and primary users; and Microsoft Defender security incidents and alerts, which can name
affected users, devices and mailboxes. ChatAdmin does not read the body of messages, calendar
entries, chats or files; alert, audit and report records can contain message subjects and
file names.
-
What the reads return is shown to you in the conversation and recorded in its transcript.
The language model
-
ChatAdmin’s answers are written by Anthropic’s Claude models, called through
Anthropic’s API under Neopiq’s own company account. For every turn Anthropic
receives the conversation: what you type, ChatAdmin’s instructions, and what the reads
of your tenant return.
-
Before read results reach the model, values that look like credentials (passwords, keys,
tokens) are removed. Names, sign-in names, e-mail addresses and other directory data are not
removed, and what you type is sent as you typed it.
-
Anthropic’s commercial terms apply to this traffic; they state that Anthropic may not
train models on customer content from its services. Anthropic deletes the conversation within
30 days; content that its systems flag under its Usage Policy is kept up to 2 years. Neopiq has
requested Zero Data Retention; once Anthropic has activated it, Anthropic does not store the
conversation after returning its answer, except where needed to comply with law or to combat
misuse. Neopiq’s deletion described below does not reach Anthropic.
Conversation transcripts and logs
-
Transcripts. Each conversation is recorded: your messages, ChatAdmin’s
answers, the reads it ran and their results (shortened to a bounded length), the approval
cards shown and their outcome, and the signed-in identity. Values that look like credentials
are removed before anything is written; personal data is not. Neopiq’s staff read a
transcript only for a support request about it, to investigate a security incident or a
malfunction, or to carry out a deletion or export; nobody at Neopiq browses transcripts. You can
download a conversation from your own browser. A daily job deletes transcripts
90 days after the day of the conversation.
-
Operations logs. Microsoft Azure Log Analytics, in Switzerland North, keeps
ChatAdmin’s technical logs for 30 days: the requests the service
answered, start-up lines, for each transcript entry a line with identifiers and its size but
not its text, and the storage account’s access records (which record was read, written
or deleted, by which identity, never its content). No password, token or key is logged.
Your organisation, its plan and its activity log
-
Organisation and members. For each customer tenant: the tenant id and name,
who set the organisation up, and which ChatAdmin areas it uses. For each person who has
signed in: name, sign-in name, internal identifier, their access in ChatAdmin (Observe,
Standard or Custom, with any restrictions), whether they are a ChatAdmin administrator, their
state, and the dates of changes and of the last sign-in.
-
Activity log. Every change of access, every approval and every consent step
is one line: who, what, before and after, when. The organisation’s ChatAdmin
administrators see it under Activity.
-
Plan and billing state. The customer record (tenant, the sign-in name of the
person who started, its progress), the plan, the trial, the subscription’s status and
what the plan allows; for a managed service provider’s trial request, also the company
name, the requesting person’s sign-in name as the contact and the number of customers
it manages.
-
Waiting list. We open a limited number of free trials each week; when this week’s places are taken, join the waiting list and we write to you when a place opens. On the waiting list you
leave your company name, a contact e-mail address, the plan you are interested in and an
optional note, so that we can write to you when a place opens. We keep these details until
your trial starts (they then become part of your customer records), until you leave the
waiting list (they are deleted at once), or until you ask us to delete them; they are never
used for anything else.
-
First look. When an administrator starts the free first look, ChatAdmin records the tenant,
the administrator’s sign-in name as the contact, the company name and the start time, and for each
question the tenant id and the time, to count the day’s questions.
-
Invitations. Each organisation has one invitation link with an opaque code, which is not
derived from its tenant id. For it ChatAdmin keeps the code, the number of other organisations that started
their first look through it, and for each of them a one-way hash of its tenant id (never the id itself) with
the date. The invited organisation’s record notes, with the date, a hash of the inviting tenant. Neopiq
sends no invitation e-mail: you share the link yourself, from Outlook, Teams or LinkedIn or by copying it, and
what you send goes through those services, not through Neopiq.
-
Checking that an organisation is an IT service provider. When an organisation asks for the
MSP trial, ChatAdmin checks, with the administrator’s own Microsoft sign-in and the permissions already
granted, whether Microsoft shows partner contracts for the tenant; or it reads once the public home page of
one of the tenant’s verified domains and has the language model (Anthropic, see
the language model) analyse it once. ChatAdmin keeps only the result
(verified, pending a review, confirmed or declined), how it was reached and the kind of evidence - never the
page’s text - and, for a request a person at Neopiq reviews, the contact, the company name and the
domains. While a review is pending, the fact that a person of one of those domains connected another tenant is
noted on it as evidence.
-
How long. These records are kept while the organisation exists and are not
deleted by age. Two exceptions: the daily log of plan and billing events is deleted after
90 days, and a trial request that never became a trial is deleted
90 days after it was last changed. The first-look, invitation and verification records are
kept like the trial records. Everything of an organisation that leaves is deleted on request (below); an
inviting organisation’s count then keeps only the hash of that organisation.
Payments
-
Online payment in ChatAdmin is being prepared and is not open yet. When it is, payment is
handled by Paddle.com, which conducts the order process as reseller and merchant of record.
Card and payment details are entered on Paddle’s checkout and never reach Neopiq.
-
ChatAdmin sends Paddle only its own reference numbers, the Microsoft tenant id and the plan,
and keeps only Paddle’s reference numbers and the subscription’s state. What you
enter at the checkout is collected by Paddle under its own terms; Paddle’s checkout
states that it shares the buyer’s data with Neopiq GmbH for product fulfilment.
Managed service providers
-
A managed service provider (MSP) connects each of its customers through a single-use,
time-limited link that the customer’s own administrator opens; that administrator
consents in the customer’s tenant.
-
The MSP’s technicians work in a customer’s tenant under their own guest account
in that tenant, with the rights the customer gives that guest. One conversation works on one
customer, and every card names the customer and the tenant. Activity in a customer’s
tenant is recorded in the MSP’s activity log and in the customer’s own.
-
The MSP’s records about each customer hold: its name and the MSP’s own
reference, the tenant id and name, the state of the connection and of the consent (which
permissions, when, by whom, with which roles), the Microsoft services detected, the
connection’s health and last error, the technicians (sign-in names, first and last
use) and the MSP’s safety settings for that customer. They stay with the MSP’s
organisation, also after a customer is disconnected, as its history.
-
The MSP’s overview of its customers reads each tenant separately, with that
tenant’s own access, and holds the results in memory only.
What ChatAdmin knows about your tenant
Since 17 November 2026 ChatAdmin keeps a tenant profile: a few facts about a customer’s
tenant that it remembers between conversations. Before a profile is first stored, the
organisation is told in ChatAdmin, under Organization, where its administrators can see every
fact and delete them.
-
What it holds. Which Microsoft services the tenant has (for example
Microsoft Entra, Microsoft 365, Azure, Power Platform, Intune); its licences, by
Microsoft’s product name, with the numbers purchased, assigned and available; and
totals such as the numbers of users, guests, mailboxes, subscriptions, environments and
devices. Each fact carries the time it was read. It also keeps a short list of the last
changes to those numbers (for example a licence count going from 20 to 25), each with its
date. For very small tenants, and tenants whose size is not known yet, it holds only which
services are present.
-
What it never holds. Names, sign-in names, e-mail addresses, device or group
names, anything about an individual user, and the content of messages or files.
-
Where it comes from. Only from reads that already happen in a conversation
or in the MSP’s overview; it adds no reads and no Microsoft permission. A change is
never based on it: every change reads the tenant again.
-
What it is used for. Only to serve that customer: better answers, its
MSP’s view of it (for an MSP, also totals across that MSP’s own customers —
counts only, shown only to the MSP’s own members, a number from one or two customers shown
as “fewer than 3”), and recommendations to that customer about its own tenant.
Operational recommendations, for example unassigned licences, are shown until the
customer’s ChatAdmin administrator switches them off. A recommendation to buy a Microsoft
product is shown only after that administrator has switched such recommendations on; the
profile is never used to recommend ChatAdmin’s own plans or upgrades. It is never used
for Neopiq’s marketing, never shown to other customers, and never combined across
customers except in an MSP’s totals for its own customers. Like everything in a
conversation, facts from it reach the language model when they are part of a turn.
-
Your control. The customer’s ChatAdmin administrator sees the profile
under “What ChatAdmin knows about your tenant” and can delete it there. Creating,
changing and deleting it is recorded in the activity log.
-
How long. A profile not refreshed for 90 days is deleted by
the daily job. It is also deleted when an MSP disconnects that customer, and with the
organisation’s other records.
Deletion, and withdrawing ChatAdmin’s access
-
Deletion on request. Write to
contact@neopiq.ai. Neopiq then deletes everything of
the tenant: transcripts, organisation, member and activity records, plan and billing records
and session records. Neopiq keeps no backup copies of these records, so the deletion is
final. It does not reach what Anthropic or Paddle hold under their own terms, nor
Microsoft’s own logs in your tenant.
-
Withdrawing access at Microsoft. An administrator of your tenant can remove
ChatAdmin’s access at any time in the Microsoft Entra admin center, under Enterprise
applications, by removing the applications “ChatAdmin Sign-in” and
“ChatAdmin API” or their permissions. A user can review the applications they
use at myapps.microsoft.com. Withdrawing the access stops ChatAdmin from reading your tenant;
it does not delete Neopiq’s records, which you ask for as above.
Where Neopiq decides about the processing (sign-in, organisation and member records, plans and
billing, logs), its legal bases are the contract with your organisation and Neopiq's legitimate
interest in providing a working, secure service (GDPR Art. 6(1)(b) and (f); revFADP Art. 31),
and for accounting records a legal obligation (Code of Obligations Art. 958f). For what
ChatAdmin reads from your tenant and the conversations, Neopiq acts for your organisation, which
decides about it.
Who receives your data
For your visit to this site: nobody, apart from the hosting provider described above. Your
data is not sold, rented, shared or disclosed. There is no advertising partner, no analytics
vendor and no customer relationship system involved in this site, because there is no
mechanism by which anything could reach them.
For correspondence: the mail and telephony providers that carry it, and nobody else —
see writing to us.
For ChatAdmin, as described under ChatAdmin:
-
Microsoft — Microsoft Azure runs ChatAdmin and holds its records and
logs, in the Switzerland North region; Microsoft Entra handles the sign-in; and when ChatAdmin
reads your tenant, it asks Microsoft’s own interfaces for your tenant (such as Microsoft
Graph), where your data already is.
-
Anthropic — the language model; it receives the conversation,
including what the reads of your tenant return.
-
Paddle — payments, once online payment opens; it receives Neopiq’s
reference numbers, your tenant id and the plan, and what you enter at its checkout.
-
Your managed service provider, if your organisation has connected one: its
technicians see what they read in your tenant, and its records hold what is listed under
managed service providers.
For authorities: we disclose personal data to a court or authority only against a legally
binding order that we are required to comply with. If we receive one, we check that it is
valid and within the issuer’s powers, disclose no more than it compels, and inform
the person concerned unless the order itself lawfully prevents that. In practice such an
order would rarely have anything to reach: the only visit data that exists sits in
GitHub’s logs, which we cannot query, so an authority wanting it would have to go to
GitHub, which publishes its own guidelines for handling government requests. What we could
actually be ordered to produce is correspondence you have sent us and, for ChatAdmin, the
records described in its section.
How long anything is kept
This website stores nothing itself: there is no database, no log of our own and no back end
behind these pages. For the website and correspondence only two retention periods exist,
and both are stated in full earlier on this page:
-
Server logs — held by GitHub, not by us, on GitHub’s own
schedule. GitHub does not publish a fixed number of days for Pages logs; its privacy
statement limits retention to what the security purpose requires. We hold no copy. See
hosting and server logs.
-
Correspondence — deleted no later than 24 months after the last
message in an exchange, except where it becomes part of a contract or matters for the
books, in which case Swiss accounting law (OR Art. 958f) sets ten years. See
if you write to us.
ChatAdmin keeps its records in Neopiq’s Microsoft Azure storage in Switzerland North;
a daily job applies the periods by age. In full under ChatAdmin:
-
Conversation transcripts — 90 days after the day of the conversation.
-
Operations logs — 30 days, in Microsoft Azure Log Analytics.
-
Sign-in session records — valid for eight hours; deleted at the latest
a day after their last use.
-
Organisation, member, activity, plan and billing records — while the
organisation exists, not deleted by age; the daily log of plan and billing events after 90
days, and a trial request that never became a trial 90 days after its last change.
-
Tenant profile — deleted when not refreshed for 90
days, when the customer’s administrator deletes it, or when an MSP disconnects that
customer.
-
Everything of a tenant — deleted on request; see
deletion.
-
At Anthropic — deleted within 30 days; content that Anthropic's systems
flag under its Usage Policy is kept up to 2 years. At Paddle — under
Paddle's terms.
Your rights
In respect of personal data relating to you, you can ask to exercise the following rights.
They are stated here in their broadest form, so that the answer does not depend on which
framework finally applies.
- Access — confirmation of whether data relating to you is processed, and a copy of it.
- Rectification — correction of inaccurate data, and completion of incomplete data.
- Erasure — deletion, where there is no overriding reason to keep it.
- Restriction — that processing be limited rather than continued, in the cases the law provides for.
- Objection — to processing based on legitimate interests, including the server logging described above, on grounds relating to your situation.
- Portability — a structured, commonly used, machine-readable copy of data you provided, where that right applies.
- Withdrawal of consent — at any time, where processing ever rests on consent. Nothing on this site currently does.
- Complaint — to a data protection supervisory authority.
In practice the honest answer to most access requests about this site is that we hold nothing
about you: the only record of your visit sits in the hosting provider’s logs, keyed to
an IP address we cannot query. A request would be forwarded to the provider to the extent it
can be. If you have written to us, the correspondence itself is the exception — that we
do hold, and it is what an access request would actually return. If you have used ChatAdmin,
the records described under ChatAdmin that name you are what such
a request would return as well.
-
To exercise a right, write to contact@neopiq.ai, or
to Neopiq GmbH, c/o Ludwig Limbeck AG, Sinserstrasse 67, 6330 Cham, Switzerland.
-
Competent supervisory authority in Switzerland: the Federal Data Protection and
Information Commissioner (FDPIC), Bern.
-
Competent supervisory authority in the EU: on the assessment under
which law applies, the GDPR does not apply to this site, so no
EU authority is competent and the FDPIC is the place to complain to. If you are in the
EU and read Art. 3(2) differently, nothing here stops you from raising the matter with
the data protection authority of your own member state — whether a complaint is
admissible is that authority’s call, not ours.
Is providing data required?
No. You are not asked for any data by this site, and there is nothing to withhold. The
technical data in the server logs is created by the act of requesting a page and cannot be
separated from it, which is true of every website; if you would rather not generate it, do
not open the page. If you write to us, you decide what to put in the message — we need
only enough of an address to reply.
ChatAdmin cannot be used without a Microsoft sign-in, because it works under your own
identity; what it then records is described under ChatAdmin.
Changes to this notice
This notice describes the site as it is built today and ChatAdmin as it runs today. It will
change when either changes. For the website, it must be rewritten before anything that
collects data is added: a contact form, an account, a newsletter, a payment step, an embedded
video, or the cloud reporting step described on the pricing page
as not yet open. For ChatAdmin, the section on ChatAdmin is updated
when what ChatAdmin keeps, or for how long, changes — for example when online payment
opens. The ChatAdmin part of this notice will be completed when ChatAdmin's subscription terms
and data processing agreement are published.
The current version is always the one published on this page. There is no mailing list to
announce changes through, because there is no mailing list.
This version is effective from 19 November 2026. The parts about the website, the free check
and correspondence are unchanged from the version effective from 16 August 2026.