Privacy Policy
Neurork Inc., a US corporation, owned by Neurkern
What we collect
- Account: email address, name (first, middle, last or a display name), @username, password (stored only as an Argon2id hash), sign-in methods you link (Apple, Google, Microsoft), date of birth (to check you're an adult), and your mobile number (verified with a code; required for every account).
- Security: signed-in devices, approximate location from IP address, two-factor and passkey details (public keys only), sign-in history.
- This browser: which accounts have signed in on it (shown in the account switcher by first name and @username only), which one is the default, and, if you choose "save my pages" when you sign out, the addresses of your open pages and your place on them, encrypted, for up to 30 days.
- ID checks (only when needed): if you appeal an age block, reset your password with your ID, or a free account looks like a second one, Stripe Identity checks a photo ID and a selfie. We receive only the result and keep a locked fingerprint (a keyed hash) of your name and date of birth so one person can't open several free accounts. We never receive or keep the ID or photos, and we ask Stripe to delete them once the check is done.
- Saved memory: short facts you ask the chatbot to remember. Health, sex life or sexual orientation, personal beliefs, politics, trade union membership, biometric or genetic data, criminal records and children's details are kept out of saved memory unless you say so.
- Wellbeing: minutes you spend on Axork each day, if you leave time counting on. Never what you did. Turning it off deletes the history.
- Your content: chats, files, images, email and messages. How each is kept:
- Daxolex Mail, mail attachments and standard Synaram messages are encrypted on our servers (AES-256-GCM) with a key per account or per conversation. Axork holds those keys, so our service can open them to show, search or send what you ask to a computer model.
- Chats with Corlatra, Canvas pages, a working copy of your Camrive files, and the search index of your chats and files (Locigram) are kept on our servers without that extra encryption, because the computer models that answer you and search have to read them. They sit on an encrypted disk, which protects them if a disk is lost or stolen but not from someone who can run our servers. Search for mail and Synaram uses keyed fingerprints, never the words.
- Files are encrypted on our servers before they go to our cloud storage provider, which only sees scrambled data.
- Synaram chats with end-to-end encryption switched on are readable only on the devices in the chat. We can't read, search or hand them over.
- Billing: your plan, payment status and receipts from Stripe, PayPal or app stores. We never receive your full card number. We never store payment details such as credit cards on our systems. You pay on Stripe's or PayPal's own page (cards, Apple Pay, Google Pay, Link, Cash App Pay, Alipay, WeChat Pay, PayPal and Venmo). We never see or keep a card number, expiry date, security code, bank account or wallet login. We keep only their references to your payment (customer, subscription and payment ids), the country that issued your card (for tax and sanctions checks) and a locked fingerprint (a keyed hash) of the card or wallet account, to spot one card paying for many accounts. It can't be turned back into the card. If you add a billing address, it's sealed with your own key and only shown to you on your bills. Staff can't see it unless you share a bill and tick 'Include my billing address'. It isn't used for tax or your billing country, and we don't send it to Stripe or PayPal. It goes in your data export, and erasing your data or deleting your account deletes it. Your country and region are used to create your account number, are not sold, and are not used to advertise. A street address is not required on a free account. A street address is required before you pay. If the payment company later returns an address with a street, that is the address on the bill. If it returns none, the address you entered stays. We never fill in a missing street.
- Usage: Impulses used and models chosen. The technical records we keep to run and protect the service are deleted on the schedule in How long we keep technical records.
- Your statement: your monthly statement is made from counts and times only, never what your messages, emails or files say, and never who your contacts are. The small counters behind it (sign-ins, security changes, emails sent and received, and so on, with the kind of browser and the country, never an IP address) are kept for 400 days. If you share a statement with support, billing staff see it for 24 hours with email addresses masked, and you see each time they open it.
How long we keep technical records
Each kind of record is deleted, or has its network address removed, once it reaches its age below. The audit log is kept forever (hash-chained). Payment records, invoices, statements and tax evidence are kept as long as tax law requires (ten years today). No retention class is set to forever without being named here.
| Record | Kept for |
|---|---|
| Who asked for sign-in codes, and from which network address | 30 days |
| The network address on each chat message (abuse limits) | 30 days |
| Each session's rough place, about 10 km (spotting use from two far-apart places) | 30 days |
| Calendar alerts held for a summary, after the summary went | 30 days |
| The network address behind each audit-log entry | 90 days |
| The last network address and city of each browser | 90 days |
| Chats you brought in with Sync: how many were added, skipped or couldn't be added, never a link, a file name or the chat's words | 90 days |
| Chats you imported from a share link: how far each import got and the names of what couldn't be added, never the link or the chat's words | 90 days |
| Files held after a safety or malware check | 90 days |
| Finished delivery retries for system mail | 90 days |
| Security signals, such as mass deletions or bursts of share links | 6 months |
| Steady State pacing decisions (amounts, times and model families; never message content) | 6 months |
| Calendar suggestions after you accepted or skipped them | 6 months |
| In-app notices after you have seen them | 6 months |
| Neurosemble screening notes when a person was not hired | 6 months |
| Network address and device seen at sign-up (fraud checks) | 1 year |
| Which of two drafts you picked in a chat, and the parts you liked (counts only, never text; deleted with the chat) | 1 year |
| Neurosemble CV files, CV text and answers of people not hired (the months depend on the country of the role and each application shows its own) | 1 to 24 months after the role closes |
| Closed Neurosemble job applications (the record only, with no CV or answers) | 1 year |
| Neurosemble equal-opportunity answers, kept apart from hiring decisions | 1 year |
| Idle Neurosemble candidate records | 1 year |
| Browsers you haven't used for a long time | 400 days |
| Which saved-chat files (.axchat) you restored: the file's signature and the chat it made, never the chat's words | 400 days |
| Refund checks, with locked card and network fingerprints | 400 days |
| Your statement's security and contact timeline (time, browser kind, country) | 400 days |
| Counts used to build that security and contact timeline | 400 days |
| Weather card request counts (place rounded; not who asked) | 400 days |
| Security rate counters | 400 days |
| What actually happened to each calendar event (minutes and outputs done, for better defaults) | 400 days |
| Accounts found sharing a card, browser or network | 2 years |
| Your Locigram search history, only if you turn it on (sealed with your own key; it deletes itself after 90 days unless you pick 30 or 60 days, or never; you can remove any search or clear it) | 90 days |
| Your Maps history of searches and routes, only if you turn it on (sealed with your own key; it deletes itself after 90 days unless you pick 30 or 60 days, one year, or never; you can remove any item or clear it) | 90 days |
| How much of your plan's Maps you used this billing period and today (a count only, never the places or words), so we can keep to the uses your plan includes | 2 months |
| Emails you send to a shared address such as support@ or billing@ (the ticket they open follows the ticket rule) | 2 years |
| What you wrote on support tickets (Gliaid) after they closed | 2 years |
| Closed fraud signals | 2 years |
| Solved desk tickets after they closed | 2 years |
| Closed abuse and safety reports | 2 years |
| Payment dispute packets (invoice facts only; no chats, mail or files) | 2 years |
| Closed Neurosemble HR cases | 2 years |
| Closed takedown and copyright cases | 3 years |
| Closed privacy and data requests | 3 years |
| Neurosemble ranking records (bands and model version; cited passages) | 3 years |
| Neurosemble check-in records | 3 years |
| Closed Neurosemble speak-up cases | 5 years |
| Which desk a staff account sits at on the private ticket status network, once nobody has used the seat | 400 days |
| Closed Neurosemble people cases | 6 years |
How we use it
To run Axork for you, keep it secure (spam, phishing and fraud checks), bill you, and answer support requests. We don't sell your personal information and don't use your private content to train computer models. We don't show ads. Staff tools never show your chats, mail, files, real name or IP address. What they can see is masked.
Who we share it with
- Model providers that run the Axork models: chat models run on Microsoft Azure (OpenAI's GPT models, hosted by Microsoft), with Alibaba Cloud Model Studio (Qwen) as the first backup and Google as the second. Microsoft Azure also runs the picture model (GPT Image). Video runs on Alibaba Cloud Model Studio (Wan), with Google's Veo as the backup. If you pick one of the Qwen, DeepSeek or Wan models from More models, that request goes to Alibaba Cloud Model Studio too. IBM watsonx runs Axork's other model features, such as Corlatra's helpers in Mail and Locigram, Bruno, chat summaries and the search overview, on OpenAI's open-weight gpt-oss-120b, with Neon's model gateway as the backup. When you use them, web search providers (Tavily, Brave, DuckDuckGo, Wikipedia). Locigram, our web search, sends the words you search for, without your account or address, to open search services such as Marginalia, Wikipedia, Wikidata, Stack Exchange, Hacker News, OpenAlex, arXiv, Open Library and GitHub; for images, videos, news and journals also to Openverse, Wikimedia Commons, the Internet Archive, Sepia Search, YouTube (official API), GDELT, Wikinews, the public broadcasters' news feeds we list, Crossref, PubMed, Semantic Scholar and DOAJ; to Brave on Web searches, up to a daily limit we pay for, with your country and language so the results fit where you are; to Naver and Daum (Kakao) on searches from South Korea; and to Google, Mojeek, Tavily, Exa or Firecrawl only when you switch on Premium engines (Google through its Gemini model on Google Cloud, only when you press Ask Google) or add your own key for them. We don't store the words you search for. Locigram does keep the public pages its searches find (the address, the title, a short summary and when it was seen) so later searches can answer from its own index; it never keeps who searched or what they typed with them. If you save a page to Camrive, its text is stored in your Camrive like any file. Sites you block or boost are kept with your account, sealed with your own key, until you remove them or delete your account. When you open a result we count it once for each search source that found it, without the page, your words or who you are. Locigram uses your country, never a finer place, unless you turn on Use my location in its Settings; even then your position stays in your browser. Picture thumbnails are fetched by our server and checked before they are shown. They receive only the messages, files and prompts needed to answer you. We don't use your private content to train computer models. Their business terms say they don't use them to train their models. Quick rewrites in the Daxolex Mail composer run on your own device and are never sent to anyone. Ask Corlatra in Daxolex Mail sends the email you have open, and its thread, to the chat model (on Microsoft Azure) only when you click one of its buttons and press Send. The email's words are not added to the search index.
- Amazon Web Services (email sending and receiving, storage), payment providers (Stripe, PayPal, Apple, Google, Huawei), and the inbox providers you connect (Gmail, Outlook, iCloud).
- Content safety: chat messages and images, including photos shared in Synaram and images attached to emails, are checked for child sexual abuse material on Microsoft Azure. If we switch on OpenAI's moderation service instead, the message or image goes to OpenAI for that check only. An image the check blocks is not delivered. It is kept encrypted for 90 days, or longer if the law requires it after a report to the authorities. Staff never see it.
- Amazon Web Services (End User Messaging), to text or call your verification codes and to check whether a number is a mobile, landline or internet number first, and Twilio as a backup for both. Stripe Identity, for ID checks. proxycheck.io, which receives only your IP address at sign-up to spot VPNs and proxies.
- Cloudflare, a processor of traffic to our sites because TLS ends there, and which may store files for us (R2). Sentry, only if we switch on error reports: technical error details, with personal data turned off.
- Open-Meteo (or The Weather Company, if we switch it on), only if you turn on the weather card: an approximate place rounded to about 10 km, or the city name you type. We don't store either; a short cache keeps the weather for that 10 km area, not who asked.
- Map providers, only when you use Maps: the places you search, the routes you ask for and the map area you look at go to one of TomTom, Stadia Maps, Mapbox, Microsoft (Azure Maps), Amazon (Location Service) or our own routing server, the words you search for a business go to Foursquare, and the spot you view for street photos goes to Mapillary, Google (Street View) or Panoramax. They come through our server, so none of them sees your address or account. We don't store searches, routes or the places you look at unless you turn on Maps history. Places you save as pins, and routes you save, are sealed with your own key and are yours to remove.
- People you choose: contacts, groups and the files you share with them, limited by your privacy settings.
- Organisations that manage your account, as described in the Terms.
- Authorities, only when the law requires it.
Your choices and rights
- Download everything or delete your account any time in Settings. See Legal for every way to reach us.
- Control who can message you, read receipts, what each contact sees, and whether the Group Chatbot can read a Synaram chat.
- Depending on where you live (for example under the GDPR or California law) you can ask to see, correct, delete or move your data, restrict it, and object to some uses. Ask in Settings → Your data rights or email [PRIVACY EMAIL], or write to [ADDRESS]. Each request is tracked against the legal deadline: one month in the UK and EU, 45 days in the US, and you're told when it's done.
Cookies
We use essential cookies to keep you signed in and protect your account. The first time you visit (or after you clear site data), a banner lets you choose optional preference storage and product diagnostics. No advertising cookies. Change choices any time under Settings. The full list is on the Legal page.
Keeping and deleting data
We keep your data while your account exists. When you delete your account, you have a grace period to change your mind (up to 30 days in the UK and EU, up to 45 days in the US). Then we wipe your chats, files, mail, messages and your search index; backups roll off within 35 days. We do not shred data at once. The export you download is your own data from your account. Staff cannot download that export. Payment records are kept as long as tax law requires. The audit log is kept forever.
Who looks after your data
- The data controller is [COMPANY NAME], a US corporation registered in [US STATE], United States of America (number [COMPANY NUMBER]), registered with the UK Information Commissioner's Office (ICO) as [ICO REGISTRATION NUMBER].
- Our representative in the EU (GDPR Article 27): [EU REPRESENTATIVE NAME AND ADDRESS].
- You can complain to the ICO (ico.org.uk) or your local data protection authority. We'd like the chance to fix it first: [PRIVACY EMAIL].
Where your data is processed
Much of Axork runs outside the UK and the EU. Today:
- Microsoft Azure, Sweden Central (EU): the chat models and the picture model (OpenAI's GPT models, hosted by Microsoft) and the content safety check.
- Google, United States (Gemini API on Google Cloud): the second chat backup, the picture backup and the video backup (Veo).
- Alibaba Cloud, Singapore (Model Studio): the video model (Wan), and the Qwen, DeepSeek and Wan models you pick yourself from More models.
- IBM, United States (watsonx.ai, Dallas): Corlatra's helpers, Bruno, chat summaries, the search overview and Camrive sorting, on OpenAI's open-weight gpt-oss-120b. Neon, United States (its model gateway) runs the same model as the backup.
- Amazon Web Services, United States (mainly us-east-1, North Virginia): sending and receiving email (Amazon SES), cloud file storage (Amazon S3) and verification texts. No computer model runs there.
- Stripe (payments and ID checks) and PayPal: their own data centres, mainly in the US and the EU.
- Twilio (backup texts), Cloudflare (a processor of traffic, because TLS ends there, and file storage) and Sentry (error reports, if switched on): mainly in the US.
- OpenAI, United States: only if we switch on its moderation service.
When your data goes to these countries, it's protected by the UK–US data bridge or the EU–US Data Privacy Framework where the provider is certified, and otherwise by the standard contractual clauses (with the UK addendum). You can ask us for a copy of these safeguards at [PRIVACY EMAIL].
Children
Axork is only for adults: 18, or the age of majority where you live if that's higher. We ask for your date of birth and may check ID. If you believe someone under age has an account, email Verification@support.axork.com and we'll close it.