In short
- On this website: your contact details and your form answers.
- In the product: what is in the tools you connect.
- We never write back to those tools.
- Nobody trains a model on any of it.
- You can export or destroy it at any time.
Who we are
Apex is operated by 1573638 B.C. Ltd., doing business as Apex, a company incorporated in British Columbia, Canada, with its registered office at 306-460 Doyle Avenue, Kelowna, British Columbia, V1Y 0C2, Canada.
For anything in this notice, write to privacy@apex.host. That address reaches the person accountable for privacy at Apex. We answer within the period the applicable law allows.
This notice covers apex.cloud, apex.host, the Apex application and everything we do around them. It does not cover the tools you connect to Apex, which remain governed by your own agreements with those providers.
Our two roles, and why the difference matters
Apex handles personal data in two capacities, and your rights differ between them.
We are the controller of our own business data
Visits to this website, the waitlist form, sales conversations, your account and billing records, support tickets and security logs. We decide what to collect and why, so we are the controller and this notice is the full account of it.
We are a processor of what is inside your brain
Once you connect a tool, everything Apex reads from it belongs to your organization. Your organization decides what to connect and what to do with the result; we only act on its instructions. For that data we are a processor, your organization is the controller, and the terms are in our Data Processing Agreement rather than here.
If you are an employee at a company using Apex and you want to know what is held about you or have it removed, ask your own organization first. We will help them act on it, and we will forward any request that comes to us directly.
What we collect as controller
When you use the website
Pages you visit and roughly where in the world you are, collected as aggregate analytics with no cookie and no cross-site identifier. We do not build a profile of you and we do not sell personal information.
When you visit our ad landing pages
Two pages, apex.host/join and apex.host/start, are where our ads send people. They show the same page, and apex.host/meta redirects to apex.host/join. If you accept cookies on one of them, it may load Meta's pixel (for Facebook and Instagram ads) and Google's tag (for Google ads). They set their own cookies and tell Meta and Google that you viewed the page, that you reached the calendar and, if you book, that you booked. Meta is also told when you first start filling in the form. Our server sends Meta its own copy of each of these events (Meta's Conversions API) with your IP address and browser type, under the same event identifier, so Meta counts each one once. If you book, the copy of the booking event can include your email address, phone number and name; our server scrambles them (hashes them with SHA-256) before anything is sent, so Meta can match the booking to an ad you saw without receiving them in readable form. If you later buy from us, a purchase event may be sent to Meta in the same way once the payment is confirmed, with the amount, the currency and an order reference, and with your email address, phone number and name hashed first. When you accept, we also keep the campaign tags on the link you came from (its utm_ parameters) and Meta's click identifier (fbclid) in your browser tab until you close it, and set Meta's two cookies on this website: _fbc, which records the ad click that brought you, and _fbp, which identifies your browser to Meta, each for 90 days. These go with the events above. Meta and Google use this to measure and improve our ads, and may also use it for ad targeting and remarketing, including custom and lookalike audiences, as described under “Advertising audiences”. If you decline, or do not choose, none of this happens: no tag, no Meta cookie and nothing sent to Meta or Google. No other page on this website loads either tag.
When you play the video on those pages
The video is hosted by Vimeo. Nothing is loaded from Vimeo until you press play. We load Vimeo's player with its “do not track” setting on, so Vimeo does not set its own viewing cookies. Vimeo's network provider, Cloudflare, still sets short-lived security cookies (__cf_bm, cf_clearance and __cf_ob) on vimeo.com to protect the service from automated traffic. We measure whether the video was played and how much of it was watched (a quarter, half, three quarters, all of it), without a cookie.
When you fill in the waitlist form
Your name, work email address and phone number, and four answers: roughly what the business turns over, which kinds of tool hold its information, what you lose track of, and what you want out of it.
If you arrive from a tagged link we also store the campaign tags on that link, the page you landed on and the site that referred you. If you start the form, enter your contact details and leave part way through, those details are kept so we can still reach you. To count how far people get we use a random identifier that lives in your browser tab and is deleted when you close it; it is never joined to your email and it does not follow you between visits or across sites.
When you book a call
Your name, email address, phone number if you give it, the time you picked, and the notes we take on the call. If you book from one of our ad landing pages, the answers you gave there travel with the booking: the hours you estimated, your role, roughly what the business turns over, whether you have tried building a brain, how many AI tools you use, and the campaign tags on the link you came from.
When you have an account
Your name, work email address, profile picture if your identity provider supplies one, which organization you belong to, your role in it, and when you last signed in. If you sign in with Google or Microsoft we receive only your identity, never access to your mail, files or calendar through that sign-in. If you use a password we store a hash of it and never the password.
When you pay
Billing contact details and invoice history. Card numbers go to Stripe directly and never reach our systems.
While you use the product
Operational records that are about use rather than content: when the app was opened, which AI client connected, how many records a request returned, how long it took, and whether it failed. These never contain your content, your search terms or the titles of your records.
What the product reads, as processor
Once your organization connects a tool, Apex reads from it to build the brain: the people, companies, meetings, messages, documents, deals and commitments in the business. The practical rule is that everything in a connected tool is used, so the control you have is which tools you connect, and you can disconnect any of them at any time.
Three limits apply to that reading:
- It is read-only, enforced in code. Apex requests a fixed list of read actions per tool and nothing else executes, whichever code path asks. There is no scope and no code path that writes to, sends from, or deletes anything in your tools.
- Slack is never copied. It is searched live at the moment your AI asks a question, and no copy is kept, because Slack's own API terms forbid one.
- We hold no keys to your tools. The authorization you grant lives with our integration partner, Composio, who makes the calls on our behalf. Apex never stores a password or a refresh token for a tool you connect.
Apex may read special categories of personal data if your tools contain them, because it reads what is there. We do not seek it out and we apply no special processing to it. If your organization needs it kept out, do not connect the tool that holds it.
Why we use it, and on what legal basis
For readers under the GDPR or UK GDPR, our bases are these. For readers under Canadian law, the equivalent is implied or express consent plus the business purposes described.
- To provide the product, including reading connected tools and answering your AI. Performance of our contract with your organization. For the content itself we act on your organization's instructions as its processor.
- To respond to an inquiry and run a sales conversation. Our legitimate interest in selling to businesses that asked us to, and your consent where you gave it on the form.
- To keep the service secure, including rate limiting, abuse prevention and the access trail. Our legitimate interest in a service that is not broken into, and our legal obligation to keep it secure.
- To bill you and keep records. Performance of the contract, and a legal obligation under Canadian tax law.
- To improve the product using aggregate, non-identifying usage counts. Our legitimate interest in knowing what works. Never using your content.
Where we rely on legitimate interests we have weighed them against your rights and you can object at any time at privacy@apex.host. Where we rely on consent you can withdraw it at any time, without affecting what we did before you did.
We do not sell personal information, we share it for advertising as described under “Advertising audiences” (that is “sharing” under the CCPA), and we do not use it to train any model. Those statements hold for every category above, and for the content in your brain.
Who else sees it
Only the service providers that make the product work, each under a written contract that binds them to the same protections we owe you. They are all named, with what each one does and where it runs, on our subprocessor page. A change is published there, with a dated change log and an Atom feed you can subscribe to, at least 30 days before it takes effect; that publication is the notice.
Beyond those, there are three situations:
- The AI you connect. It sees the parts of your brain it asks for, because that is the point of connecting it. Which AI, and what you let it do, is your decision.
- Legal compulsion. If we receive a binding order we will tell you before we act on it, unless we are legally prohibited from telling you, and in that case we will challenge the prohibition and tell you as soon as we are allowed. We disclose the minimum the order actually requires.
- A sale of the business. If Apex is acquired or merges, your data moves with it under this notice, and we will tell you before it does.
Advertising audiences
If you accept cookies on our ad landing pages, we may use the events described under “When you visit our ad landing pages” to measure and improve our ads, to remarket to you, and to build custom and lookalike audiences with Meta and Google. We may also upload a list of customer or waitlist email addresses, hashed first, for the same purpose. You can opt out at any time by writing to privacy@apex.host, by declining cookies on those pages, or through Meta's and Google's ad settings. Asking us to stop also means we will remove you from those lists the next time they are refreshed.
Where your data is stored, and transfers
Apex runs on Amazon Web Services in the US West (Oregon) region. The website and the waitlist run on Vercel and Supabase, also in the United States. Our company is Canadian, so data reaching us is subject to Canadian federal privacy law, and from there it is processed in the United States by the providers on our subprocessor list.
We do not offer regional data residency. There is no EU region, and neither model provider offers a Canadian inference region we can use.
For customers in the European Economic Area, the United Kingdom and Switzerland, transfers are covered by the mechanisms set out in the international transfers section of our Data Processing Agreement and its annexes: the European Commission's adequacy decision for Canada, with the 2021 Standard Contractual Clauses, the UK Addendum and the Swiss amendments applying automatically underneath it. We have documented a transfer impact assessment for the onward leg into the United States and will share it with a customer or a supervisory authority who asks.
How long we keep it
Every category has a stated ceiling, published as a schedule on our retention page. In outline: your brain lives as long as your account does; raw copies of what we read are deleted after 180 days; logs run 30 days to 12 months; database backups are kept 35 days; billing records are kept seven years because Canadian tax law requires it.
Waitlist and sales records are kept for 24 months from our last contact with you, then deleted. Ask sooner and we will delete them sooner.
When your organization deletes its brain we remove every row inside 30 days and destroy the encryption key belonging to that organization, so any copy surviving in a backup is ciphertext that nobody, including us, can open.
Your rights
Wherever you live, you can ask us for a copy of what we hold about you, a correction, deletion, or a machine-readable export, and you can object to a use or ask us to restrict it. Write to privacy@apex.host. We do not charge, we do not require an account, and we will never treat you differently for asking.
We will ask you to verify your identity first. If the data sits inside a customer's brain, we route the request to that customer as controller and help them answer it.
If you are in the EEA or the UK
You have the rights of access, rectification, erasure, restriction, portability and objection, including to profiling, under Articles 15 to 22 of the GDPR or UK GDPR. You can also complain to your national supervisory authority, or in the UK to the Information Commissioner's Office.
If you are in Canada
You have the right to access and correct your personal information under PIPEDA and under the provincial statutes of British Columbia, Alberta and Quebec. Under Quebec's Law 25 you also have the right to data portability, the right to be informed of and contest a decision made solely by automated means, and the right to ask that information be de-indexed. Apex does not make decisions about individuals by automated means.
If we use a service provider outside Canada, as we do, you can ask us for written information about those providers, which countries they operate in and what they are authorized to do. That information is the subprocessor page, and the person who can answer questions about it is our privacy contact above, who is also our designated person in charge of the protection of personal information for the purposes of Law 25. You can complain to the Office of the Privacy Commissioner of Canada, or to the Commission d'accès à l'information du Québec, the Office of the Information and Privacy Commissioner of Alberta, or the Office of the Information and Privacy Commissioner for British Columbia.
If you are in California or another US state with a privacy statute
You can request access, correction, deletion and portability, and you can appeal a refusal. We do not sell personal information. We do share it for advertising as described under “Advertising audiences”. On our ad landing pages, and only if you accept cookies there, Meta's pixel, Google's tag and our server's copies of those events send Meta and Google the information described under “When you visit our ad landing pages”; you can stop it by declining cookies on those pages, and you can ask us to stop at any time. We do not process sensitive personal information to infer characteristics.
Cookies and tracking
The website sets no advertising cookies and no cross-site trackers, with one exception: on our ad landing pages, apex.host/join and apex.host/start, accepting cookies may load Meta's pixel and Google's tag, which set their own cookies, and sets Meta's _fbc and _fbp cookies (see “When you visit our ad landing pages”). Declining keeps them all off. Analytics are aggregate and cookieless. The waitlist form uses a single identifier that lives in your browser tab and dies with it.
The application sets one cookie, which holds your signed-in session. It is host-only, HttpOnly, Secure, SameSite=Lax, and lasts 30 days. It is strictly necessary: without it you cannot stay signed in.
How we protect it
Everything is encrypted at rest with AES-256 and in transit with TLS 1.2 or better. Your organization's content carries a second layer of encryption under a key belonging to that organization alone. Every organization is fenced off inside the database itself rather than only in application code, and the application runs under a restricted database role so the fence applies to Apex too. Interactive server access is disabled, secrets live in a managed secret store and never in code, the database is configured never to log your content, and every read of customer content is recorded.
The full list, including what we have not yet achieved, is on the security page. If you believe you have found a vulnerability, write to security@apex.host.
Where a breach creates a real risk of significant harm and the law requires notification, we will notify the relevant regulators and affected individuals without undue delay. For customers we notify the controller as set out in the DPA.
Children, changes, and how to complain
Apex is sold to businesses and is not directed at anyone under 16. We do not knowingly collect their personal data, and if we learn we have, we delete it.
When this notice changes we update the date at the top. If a change materially affects your rights we will say so on this page before it takes effect, and we may also email account holders.
Complain to us first at privacy@apex.host. If we do not put it right, you can go to the regulator for where you live, listed above.