In short
- Updated on 12 November 2026 to say that the estimate assistant asks you to confirm your email with a code before it answers, that temporary inboxes and addresses that cannot receive email are not accepted and how we tell (a public DNS question about the part after the @), and that the site’s music plays only in the browser that opened the page (the ax_music cookie), on 9 November 2026 to say how long we keep what you give us (7 years, nothing is deleted by itself, and the log of every change is kept for good), on 7 November 2026 to say that the Arxeon team can read an estimate conversation left part-way, what the assistant’s AI provider is sent, and how sign-in waits after wrong passwords, on 6 November 2026 to describe your company on Arxeon, on 1 November 2026 to describe the notifications in your client record, and on 31 October 2026 to describe Google’s advertising tag, invoices through Stripe, what sign-in and your client record keep, and the copy we keep of each email we send.
- One script comes from another company: Google’s advertising tag, so we can tell whether our ads bring enquiries. It is not on your client record, the team’s pages, or any page a link in our emails opens. No analytics service, no session recording, no social-media widgets.
- We never sell, rent or trade personal information, and we never use it to train an AI model.
- Read the site and you are anonymous to us beyond ordinary server logs. Everything else here happens only if you type something in.
- The estimate assistant sends what you type to our AI provider to answer it. Do not put confidential, medical or financial details in it.
- We keep what you give us for 7 years, as business records, and delete nothing by itself; the log of who changed what is kept for good. Ask us what we hold about you, to correct it, or to close your account, at info@arxeon.ca.
01
Who we are, and what this covers
#
Arxeon Inc. (“Arxeon”, “we”, “us”) is a software
company at 225 11 Ave SE, Calgary, Alberta, Canada. This policy covers
arxeon.ca and every page served from it, including the
estimate assistant, the dispatch sign-up and the account pages.
It does not cover work we do under a signed agreement. If Arxeon builds or
runs something for your organisation — a platform, a model, a clinical
system — the handling of that data is governed by that agreement and
not by this page. Qlynic, and any other Arxeon product with its own account,
has its own terms and its own privacy notice.
We follow Alberta’s Personal Information Protection Act (PIPA),
Canada’s Personal Information Protection and Electronic Documents
Act (PIPEDA) where it applies, and Canada’s anti-spam legislation
(CASL) for anything we email you.
02
What we collect
#
Nothing on this site asks for personal information in order to read it. Each
item below happens only because you did something — typed, subscribed,
registered or signed in.
Reading the site
Our host records the ordinary details of a web request: the IP address it
came from, the browser’s user-agent string, the page asked for, the
page you came from, the time, and the response. That is the standard log
every web server keeps, and we use it for security and to find faults. We do
not build a profile from it. There is no analytics service, session recorder
or social-media widget on this site; the one advertising tag is described
next.
Google’s advertising tag
The site’s pages load Google’s advertising tag (Google Ads), except
your client record, the team’s pages, and any page that a link in one of
our emails opens: those links carry a key, and the tag passes on the whole
address of the page it runs on.
Where it runs, your browser sends Google the page’s address and title,
your screen size, details of your browser and operating system, and an
identifier kept in a cookie (_gcl_au, see
section 03). Google uses this to tell us whether a
visit that came from one of our ads led to an enquiry, and may use it to show
our ads to people who have visited this site. When an enquiry from the
estimate assistant reaches us, the page tells Google that one did, with a
random receipt number: our code sends Google nothing you typed — no
name, email address, conversation or price.
Google uses what it receives under its own policy:
How Google uses information from sites that use its services.
You can turn off personalised ads in
Google’s ad settings, or
block the tag or third-party cookies in your browser; every page here works
without it.
The estimate assistant
The assistant on the home page (“the open channel”) is a
conversation with an AI model. While it is open we hold the conversation in
your server session, and we record in our database: the messages on both
sides, which track you chose, how many turns it ran, whether a message was
refused and why, the size and cost of the model calls, the resulting brief
— and, to keep the endpoint from being abused, a one-way salted hash
of your IP address, your user-agent string and the page that referred you.
Your IP address itself is never written to that record. The
limiter has to recognise a repeat visitor, not identify one, so what is
stored is an irreversible hash and nothing that can be turned back into an
address.
Before the assistant answers your first message, it asks for your email
address and emails it a 6-digit code, which works for ten minutes; the
conversation starts only once you type the code back. If you are signed in
to your client account with a confirmed address, that address is used and
no code is sent. We hold the address you confirm in your server session.
Our activity log notes each address a code is sent to, and the confirmed
one with its conversation. Temporary inboxes, and addresses whose domain
cannot receive email, are not accepted (section 06
says how we tell), and one we refuse is noted in that log too.
If you then ask for the brief to be sent, we also take the name and company
you type, store them with that conversation and the address you confirmed,
email the brief to our office, and email a copy to that address, never to
another. We record the conversation as
it runs, whether or not you send it, so the Arxeon team can read one that
was left part-way. It is kept as How long we keep it
says.
The dispatch (our monthly letter)
Type an address into the footer and we record nothing. We mail that
address a signed confirmation link, which expires after 72 hours. Only when
you click it does a subscription exist, and at that moment we email
ourselves your address, the IP address the click came from and the time
— that is the evidence of express consent CASL requires us to hold, and
our outbox keeps a copy of that email (see Emails we send, below). We do not
keep a marketing database beyond that, and there is no profiling, scoring or
open-tracking behind the letter.
An Arxeon account
If you create an account we store your email address, a cryptographic hash
of your password (never the password), and the security stamp and sign-in
counters ASP.NET Identity keeps. If you turn on two-step sign-in, we keep
your authenticator app’s secret encrypted with a key the database never
sees, and only hashes of your recovery codes and of any code we email you.
Sign-ins and failed attempts are recorded to stop password guessing, and
each change you make while signed in is recorded with the time and the IP
address it came from, so the history of an account can be checked (the
audit log: section 08 says how long it is kept).
If you sign in with Microsoft, Google or LinkedIn instead,
we ask that provider only for the basic profile scopes — your name,
your email address and the identifier that provider uses for you. We receive
those three things and store the identifier so we recognise you next time.
We never see your password with that provider, we cannot read your mail,
files, contacts or connections, and we never post anything on your behalf.
What the provider records about the sign-in is covered by that
provider’s own privacy policy, not this one.
Quotes, agreements and payments
Once we quote for you, the quote, its messages and the files you share with
us are kept with your account, in your client record. If you sign an
agreement on the site, we record the name, title and company you type, your
email address, the time, and the IP address and browser it was signed from,
as evidence of the signature. Invoices are issued through Stripe and paid on
Stripe’s own pages: we keep each invoice’s number, amount, dates and
status, and Stripe’s links to it.
Your company
Your quotes and projects belong to a company on Arxeon, made for you once your
address is confirmed and named from your profile or your briefs (your
organisation’s name, else your name). We keep the company’s name, who is in it, each person’s
role there (admin, signer, approver or viewer) and when they joined or left. Among
clients, only the people in a company see its quotes and projects.
Writing to us
Email us, or send a brief, and we keep the message and your address so we
can answer it and so we have a record of what was agreed.
Emails we send
We keep a copy of every email this site sends: who it went to, its subject,
its words and any file with it, when it went, and what our mail service
answered, so we can tell that it went and send it again if it did not. An
email that carries a sign-in code, or a link with a key in it (confirming
your address, choosing a new password, joining the team), is kept only as
who it went to, its subject and when, never its words. The dispatch’s
confirmation link is not recorded at all.
Notifications
When there is news about your quote or your project, your client record shows
it under the bell at the top of each page, and we keep that notice with your
quote: what it says, the page it opens, and when you read it. Which kinds of
news reach you there is your choice on Your details, and so is whether
reminders and the weekly status also come by email; we keep those choices with
your account. The other emails about your quotes, your projects and your
invoices can’t be turned off there: we send them when the work or your
agreement needs them.
What we never collect here
- Payment card or bank details — invoices are paid on Stripe’s own pages, so those go to Stripe and never reach this site.
- Health information. Please do not type any into the assistant; it is a sales conversation, not a clinical one.
- Precise location, contacts, device identifiers, or anything from your other tabs.
- Personal information bought or scraped from anywhere else.
03
Cookies and browser storage
#
Every cookie this site sets for itself is one it needs to work. The one
exception is _gcl_au, set by Google’s
advertising tag on the pages that load it (section 02);
Google may also read or set cookies of its own, on its own domains.
- ASP.NET_SessionId
- Holds your side of an assistant conversation together. Expires when you close the browser.
- __AntiXsrfToken
- Proves a form was submitted from our page and not from someone else’s. Expires when you close the browser.
- .AspNet.ApplicationCookie
- Set only once you sign in; it is what keeps you signed in. It lasts the session unless you tick Remember me.
- .AspNet.ExternalCookie
- Set only during a Microsoft, Google or LinkedIn sign-in, for the few seconds between leaving that provider and landing back here.
- .AspNet.TwoFactorCookie
- Set only half way through a sign-in: after your password, or after Google, Microsoft or LinkedIn, while the code two-step sign-in asks for is still to come, or while you set two-step up when your account must have it. It lasts ten minutes (twenty to set two-step up) and goes when you close the browser.
- .ArxeonTwoStep
- Set only if you tick Don’t ask again on this browser for 30 days at the code. It skips the code on this browser for 30 days, or until the account’s password or sign-in details change. While it lasts, this browser keeps its own count of wrong passwords, so wrong passwords typed elsewhere do not keep it out.
- .AspNet.Correlation.Google, .AspNet.Correlation.Microsoft, __Host-ArxeonLinkedIn
- Set only while you are away at Google, Microsoft or LinkedIn to sign in, so their answer is taken only by the browser that asked for it.
- __Host-StudioToken
- Set on your client record and the team’s pages once you are signed in. It proves a change was asked for from our own page, and only this site, over a secure connection, can set it. Expires when you close the browser. It used to be called __StudioToken; a browser that still holds that one has it removed the next time it opens one of these pages.
- ax_music
- A random value, set when a page with the site’s music opens. The music plays only through links that work in the browser holding it, for 12 hours at most, so the songs play on these pages and nowhere else. Expires when you close the browser.
- ax_rows
- Set only if you change how many rows a list shows on your client record or the team’s pages (25, 50 or 100), so the next list opens the same way. Lasts a year.
- ARRAffinity set by our host, not by us
- Keeps you on the same server instance so a conversation in progress is not handed to a machine that has never heard of it.
- _gcl_au set by Google’s advertising tag
- Lets Google connect a visit that came from one of our ads with a later enquiry. Lasts 90 days. The tag also keeps _gcl_ls in your browser’s local storage.
The site also uses your browser’s session storage,
which your browser clears when the tab closes: whether you switched the
audio on, which track was playing and how far it had got
(ax-sig-on, ax-sig-i,
ax-sig-at), so moving between pages does not
restart it; what you typed into the answer box on the AI, Health technology
or Engineering page, until the assistant on the home page takes it as your
first message (ax-open-carry); and a note that an
enquiry has already been counted, so Google is not told twice
(ax-ads-quote). None of these is sent anywhere
by itself. Your client record and the team’s pages also keep layout
choices, such as a folded side bar, in local storage.
You can clear or block all of this in your browser’s settings. Block
the cookies above and you can still read every page; you will not be able to
stay signed in, finish a conversation with the assistant or hear the
site’s music.
The site does not read Do Not Track or Global Privacy
Control signals. To stop Google’s advertising tag, use
Google’s ad settings or block the tag in your browser, as
section 02 says.
04
Why we use it
#
Those are the only purposes, and we will not quietly add another:
- To answer you. A brief, an email, a support request — we need the message and a way to reply.
- To run the site. Sessions, sign-in, forms, and the record of what the assistant was asked so a person can pick the thread up.
- To keep it standing. Rate limits, abuse prevention, lockouts, fault diagnosis and security investigation.
- To send the dispatch, to the people who confirmed they want it.
- To improve the work. Reading back real conversations shows where the assistant misunderstands a question and where our own estimates are wrong. That review is done by people here, on our own records.
- To see whether our advertising works. Google’s advertising tag tells us whether a visit that came from one of our ads led to an enquiry (section 02).
- To meet our obligations — tax, corporate and legal records, and responding to a lawful request we are actually required to answer.
Under PIPA we rely on your consent: giving us the information is the
consent, and you can withdraw it (see
your choices and rights). Where the law lets an
organisation collect without consent — investigating a security
incident, for instance — we rely on that instead, and only as far as
it goes. Google’s advertising tag runs without asking first;
section 02 says what it sends and how to turn it off.
05
The assistant, and AI
#
Arxeon builds AI systems for a living, so it is worth being exact about the
one on this site.
When you write to the assistant, your message is first checked on its own
by a smaller model, then sent with the conversation so far (your first
message and the most recent ones) over an encrypted connection to
Anthropic, whose model writes the reply; both models are
Anthropic’s. A message the check turns away stays on our record with
that verdict, and is never sent with the conversation. Anthropic acts as our
service provider for those calls. Under the terms we contract on, they do not
use what passes through them to train their models.
We do not use your conversations, your brief, your email or anything
else from this site to train an AI model — not ours, not
anyone else’s — and we do not licence or sell it to anyone who
would.
Two things follow from how it works, and they are worth knowing before you
type:
- A language model can be wrong. The number it puts on a brief is an indication from a conversation, not a quote, and nothing it says binds Arxeon to a price, a date or a scope. The Terms of Use say so in the formal way.
- Whatever you type is read by a person here afterwards, and stored as described above. Do not paste confidential material, patient information, credentials or anything under an NDA into it. If you need to discuss something sensitive, email us and we will sign what needs signing first.
The assistant makes no decision about you. It cannot approve, decline, price
or profile anything — a person reads every brief that reaches us.
06
Who else touches it
#
This is the whole list. Each one works for us, under contract, for the
purpose beside its name, but the last: two public DNS services we only
ask a question of. Stripe and the sign-in providers also keep what
they handle under their own privacy policies, and Google’s advertising
tag serves Google’s own purposes as well as ours.
- Microsoft Azure
- Hosts the site and the database it writes to.
- Anthropic
- Answers the estimate assistant. Receives the conversation; receives nothing else from this site.
- Twilio SendGrid
- Delivers the mail this site sends — confirmations, briefs, the copy of your brief, the dispatch, and the emails about your quotes and projects. Receives the address it is delivering to and the message itself.
- Stripe only if we invoice you
- Issues our invoices and takes payment on its own pages. Receives the email address the invoice goes to, the client’s company or the signer’s name, and what the invoice is for; your card or bank details go to Stripe alone.
- Microsoft, Google, LinkedIn only if you choose that sign-in
- Authenticate you and tell us your name, email and their identifier for you. Nothing is sent to them unless you click their button.
- Google advertising tag
- Receives what section 02 describes from the pages that load its tag, and uses it under its own policy as well as to report to us.
- Cloudflare and Google public DNS, only the part of an address after the @
- When you give us a new email address (to the estimate assistant, for a new account, for the dispatch, as a new sign-in address, to attach your quotes, or in an invitation), we first check its domain against a list of temporary-inbox services. For a domain the list does not know, we ask Cloudflare’s public DNS service, or Google’s when Cloudflare does not answer, where that domain’s email is delivered, so that a temporary inbox or a domain that cannot receive email is refused. They receive the domain alone, never the address, and nothing is asked about the most common mailbox domains, such as gmail.com, outlook.com and hotmail.com. They are public services, not under contract with us, and keep what they receive under their own policies.
Beyond that, we disclose personal information only where the law requires it
— a court order, a warrant, a binding demand we have checked —
or where it is needed to protect someone’s safety or our legal rights.
If Arxeon is ever sold or merged, records may pass to the buyer, who would
be bound by this policy until you are told otherwise.
We have never sold personal information and we do not intend to
start.
07
Storage and access outside Canada
#
Alberta’s PIPA requires us to tell you plainly when a service provider
outside Canada may hold or access your information, and why. So: the
suppliers above operate in Canada and the United States.
Your information may be stored in, or accessed from, either country for the
purposes described in this policy. Google says in its own policy that what
its advertising tag receives may be processed on servers outside the country
you live in. The two public DNS services in section 06 answer
from whichever of their servers is nearest, which may be in another country;
they receive only the part of an address after the @.
While information is in another country it is subject to that
country’s laws, including lawful access by its courts and authorities.
We choose suppliers with that in mind, we keep the amount of personal
information that leaves Canada as small as the job allows, and we use no
supplier outside Canada or the United States.
Questions about that — where a particular record sits, or what a
supplier can see — go to our Privacy Officer at
info@arxeon.ca, and you will get a
straight answer.
08
How long we keep it
#
- An assistant conversation
- 7 years from your last message, so an enquiry that comes back to life still has its history, and because it is part of our business records.
- A brief you sent us, and everything that follows it
- 7 years from the last time anything on it was written or read. A quote, an agreement, a project and its files, invoices and the emails about them are business records, and 7 years is the period Canadian tax and corporate rules expect of records about business dealings.
- Dispatch subscription
- Until you unsubscribe. We keep the record of your consent for 7 years after that, like every record; CASL requires us to be able to prove it was given.
- Account
- 7 years from its last use. Ask us to close it and we do within 30 days: you can no longer sign in with it, and what it holds is kept only as a record for those 7 years.
- The audit log
- Every change to our records — who made it, when, from where, and what the record held before and after — is written to a log, so the history of every record can be checked. The log is kept for good: no line in it is ever changed or deleted, even after the record it describes is deleted.
- Server and platform logs
- Kept by our host for a short period — days to a few weeks — for security and fault-finding, then rotated away.
Nothing is deleted automatically. Removing a record on this site — a
message, a file, a note, a person — hides it rather than deleting it; a
few settings are replaced when you change them, such as two-step sign-in or a
linked Google, Microsoft or LinkedIn sign-in, and the audit log records the
change. Once a record’s 7 years have passed, we look at it and either
delete it or strip it of anything that identifies a person; its history in the
audit log stays. Two kinds of record we delete by hand, without waiting:
records we made ourselves to test the site, and anything a child sent us
(section 12). Backups age out on their own cycle, so a
deleted record can sit in a backup for a short time after it has gone from the
live system.
09
How it is protected
#
- Every page and every API call is served over HTTPS.
- Passwords are stored as salted one-way hashes. Nobody at Arxeon can read yours, and we will never ask you for it.
- Five wrong passwords for one address make it wait 15 minutes, and twenty wrong tries from one connection make that connection wait 15 minutes, which makes guessing impractical. Signing in with Google, Microsoft or LinkedIn, the code after your password (wrong codes have their own count of five), and a browser that keeps you from being asked for the code never wait because of wrong passwords typed elsewhere. If you are asked to wait and the tries were not yours, reset your password from your inbox: that ends the waits on your address and on your codes.
- Confirmation links are signed with HMAC-SHA256 and expire, so one cannot be forged, edited to point at another address, or replayed later.
- The assistant’s limiter stores a salted hash of an IP address rather than the address.
- Access to the database and the mailboxes is limited to the people at Arxeon who need it, on accounts with multi-factor authentication.
- This site never sees or holds a card or bank number: invoices are paid on Stripe’s own pages.
No system is perfectly secure, and anyone who tells you otherwise is selling
something. If a breach ever creates a real risk of significant harm to you,
we will report it to the Commissioner and notify you, as PIPA and PIPEDA
require — without waiting to be asked.
10
Your choices and rights
#
You can ask us to:
- Show you what personal information we hold about you, how we have used it, and who we gave it to.
- Correct anything that is wrong or out of date.
- Close your account or end a subscription. What was recorded is then kept only as How long we keep it says.
- Stop — withdraw your consent to any use described here, at any time, subject to legal or contractual records we must keep.
Write to info@arxeon.ca and we will
answer within 45 days, the period PIPA sets. We may need to
confirm who you are before handing over a record — usually by replying
from the address the record belongs to — and we may have to redact
another person’s information from what we send. There is no charge for
a straightforward request.
Every dispatch letter carries a one-click unsubscribe. It takes effect at
once; you do not have to write to anyone.
If we get it wrong, tell us first — we would rather fix it. You can
also complain to the Office of the Information and Privacy
Commissioner of Alberta (oipc.ab.ca) or, where PIPEDA applies, the
Office of the Privacy Commissioner of Canada (priv.gc.ca).
11
If you are a client
#
When Arxeon builds, hosts, trains or maintains something for your
organisation, any personal information inside that system belongs to you and
we handle it as your service provider, under the agreement we signed —
which sets out what we may do with it, where it lives, who may see it, and
what happens to it when the engagement ends.
Two commitments we make in every such agreement, and are glad to repeat
here: we do not use a client’s data to train models for
anyone else, and we do not reuse it beyond the work it was given to
us for. Where the work involves health information in Alberta, the
Health Information Act and the custodian’s own obligations
govern it, and our agreement is written to sit inside those.
12
Children
#
This is a business site and it is not directed at children. Accounts are for
people aged 18 or over. We do not knowingly collect personal information
from a child; if you believe a child has sent us something, write to
info@arxeon.ca and we will delete it.
Only its history in the audit log stays (section 08).
13
Changes to this policy
#
The site will keep changing, and so will this page. The date at the top is
the one that counts. If a change materially affects what we collect or who
we give it to, we will say so on the site — and, where the law
requires consent for the new use, we will ask for it rather than assume it.