Privacy Policy

Last updated · September 29, 2026

This policy explains how Aurum Technology Limited ("Aurum," "we," "our," or "us") handles personal data in Aurum Life (the desktop app, the mobile app and the cloud features they use) and on this website. Aurum Technology Limited is a company incorporated in England and Wales (company no. 17127517), registered office 167-169 Great Portland Street, Fifth Floor, London, W1W 5PF, United Kingdom, and is the data controller for this processing. We are established in the United Kingdom, and our supervisory authority is the UK Information Commissioner's Office (ICO). Aurum Life is currently offered to users in the United Kingdom, Trinidad and Tobago, and the United States and is not directed to the European Economic Area.

The browser extension Save to Aurum has its own privacy policy.

The short version

Your Life OS is a folder of files on your own computer. The desktop app works without an account, and until you sign in it contacts our servers only to check for updates, to load the template catalog when you open it, and to send diagnostics if you agree to them.
Signing in turns cloud features on. By default the assistant uses cloud AI, which means your messages, and context from your Life OS that the app adds to them, go to our servers and on to Google's Gemini models. You can switch the assistant to a model on your own computer in Settings → AI.
When you choose to sync a Life OS, its pages and tasks are stored on our servers so your other devices can reach them, and the desktop app backs the folder up to our servers every day.
We don't sell your data, we don't show ads, and neither we nor Google use your content to train AI models.
You can export what we hold and delete your account at any time. Some records outlive an account, and Retention lists them.

On your device

Your pillars, areas, projects, tasks, notes and daily notes are plain files in the folder you chose, readable with any editor. The desktop app keeps its own database and search index in a hidden .aurum folder inside it, encrypted with a key held in your operating system's keychain. Other things it keeps there, such as chat history, the agent's memory, your profile, a log of what the agent did and local backups, are ordinary files protected by your computer's own security, not by us. Sign-ins for your Aurum account and for services you connect are kept in the operating system's keychain. The mobile app keeps its own copy of what it syncs, your chats and unsent captures on the phone. From the mobile app update that added a Crash reports switch under Settings → Privacy & Data, it removes them from the phone when a different account signs in there, when the app is used there without an account, or when you delete your account from the phone. It asks first when that would delete chats, unsent captures, or edits and agent memories not yet synced. Learning progress not yet synced is not counted, so it can be lost without a question.

Without an account

Even without an account, the desktop app contacts these services:

Our update server, at most once a day, with the app version, the operating system and the update channel, and no identifier. Updates themselves download from GitHub.
Hugging Face, once, shortly after you first open a Life OS, to download the model the app uses to search your notes on your own computer.
GitHub and our template catalog, when you open Templates, to list the templates and starter packs you can install, along with anything you type into the catalog search.
Ollama's model library, only if you choose to download a model to run on your computer.
Any website an image in your notes points to, when that note is shown, as with any document that embeds an image from the web.
Services you connect, directly from your computer (see Services you connect).

Each of these sees your network address, as any internet service does. Crash reports and usage counts are sent only if you agree to them (see Diagnostics).

Your account

To create an account we need your email address and a password, or a Google or Apple sign-in, or your organisation's single sign-on. Our sign-in provider stores a hash of your password, never the password itself, and keeps a security log of sign-in events with your email address and the network address they came from. If you turn on two-step verification we store the factor and hashed recovery codes. Your profile holds the name you choose, your preferred name, and the settings you save to your account, such as notification preferences, your time zone for scheduled notifications, and a GitHub username if you add one so teammates can see your activity in linked projects. Every time you save your profile in the desktop app, your preferred name is uploaded so teammates see it. The security log is kept for 90 days, and your entries in it are erased when you delete your account.

Sync across your devices

When you sign in to the desktop app with a Life OS open, it asks whether to Sync & merge that Life OS with your account or Keep separate. Choosing Sync & merge uploads, and keeps uploading as you work:

every pillar, area and project page, including its full text each time it changes, its properties, its place in your structure, and whether you or the agent made the change;
every task, with its text, dates, priority, recurrence, owner and status;
calendar events, and flashcard decks and quizzes in learning paths;
the agent's memories, and your flashcard and quiz progress;
a search fingerprint of each page, made by sending the page's title and the first 8,000 characters of its text to Google's embedding model, so the mobile app can search your pages by meaning. In desktop versions up to v0.1.53 this happens even if the assistant is set to run on your computer. From the release after v0.1.53, a computer set to Local in Settings → AI sends no page text for this; the pages it changes are indexed once it is switched back to Cloud, or by another of your devices that is set to Cloud. Until then the mobile app's search by meaning does not find a new page, and finds an edited one only by its earlier text; its keyword search finds both.

In your personal space, daily notes, notes outside your pillar, area and project folders, quick captures on the desktop, chat history and files attached to pages are not synced, although cloud backups include them. Each change is kept in a change history on our servers (see Retention). Your flashcard and quiz progress uploads whenever you are signed in, whatever you answered.

Choosing Keep separate stops syncing for that Life OS, including shared workspaces, apart from the learning progress mentioned above. Two more things are worth knowing. Shared workspaces you belong to start syncing into the folder as soon as you sign in, before you answer, and stop only if you choose Keep separate. In desktop versions up to v0.1.53, a Life OS that had synced before could start syncing again without asking, even under a different account; the release after v0.1.53 always asks.

The assistant and other cloud AI

All of Aurum's cloud AI runs through our servers on Google's Gemini models. Cloud is the default. With it, each message you send to the assistant carries, besides your message and the conversation so far:

your profile: name, preferred name, and whatever you have told the app about your roles, goals, working style, schedule, age range, health interests, values, city and country;
the agent's memories and the patterns it has noticed about how you work;
a summary of your Life OS: active projects with their goals and deadlines, the next week's events and their locations, and your pillars' purposes;
the page you have open, and its tasks if it is a project;
passages from notes anywhere in your Life OS that relate to your message, for most messages of ten characters or more: up to 6,000 characters from any one note and 28,000 in total;
the text of files you attach, and the results of tools the agent uses.

Automatic memory also sends recent conversations to the AI you chose, to pick out facts worth remembering, and saves them without asking. From the desktop release after v0.1.53, each time it saves or changes something it tells you how many memories it added, changed or let go to make room, with a button to review them. You can review, delete or turn this off in Agent → Memory.

Choosing Local in Settings → AI keeps the assistant's text on your computer. The choice is made on each computer separately. Even on Local, if you are signed in, sync and cloud backups (when they are on) still reach our servers, images you add to a chat are described by cloud AI, reports are read aloud by cloud text-to-speech unless you turn that off, the agent's web searches go through our servers, and scheduled tasks run in the cloud if you allowed them. In desktop versions up to v0.1.53, synced pages are also still indexed as described above. Voice conversations, dictation, text-to-speech, web search and deep research are always cloud features.

Google processes these requests under its paid Gemini API terms: it does not use them to train or improve its models. Google keeps prompts and responses for a limited period to detect abuse and to meet legal obligations, and may process them in any country where it operates.

Voice and dictation

A voice conversation streams your microphone audio through our servers to Gemini Live, together with your name, roles, goals, working style, city, country, local time and the names of your pillars and up to five active projects in each. Dictation in the desktop app, voice notes captured on a phone and read-aloud audio also go through Gemini. We don't record voice conversations or dictation on our servers; a voice note you attach to a capture is stored with it (see The mobile app). We keep a record of each voice session: when it started and ended, how long it lasted and how it ended. Dictation in the mobile app uses your phone's own speech recognition, which may send audio to Apple or Google when it can't recognise speech on the device.

Web search and research

When the agent searches the web, the search words it chose go to Tavily and, if Tavily has no answer, to Google Search through Gemini. A research report searches with its topic and focus only, never your notes; if you tick "Include my notes", passages from your notes go to Gemini to write the report. Deep research runs on our servers with Google Search, and the report is stored with your account for 90 days.

Scheduled tasks

Scheduled briefings, reviews and tasks you create run on our servers at the times you choose, only while both the Cloud processing and Scheduled tasks consents are on (from the desktop release after v0.1.53, the desktop app calls the first one Background cloud processing). A run reads your synced pages and tasks, sends the parts it needs to Gemini, and stores the result and a record of its steps for 90 days. Automation rules you write run on your own computer.

Services you connect

In the desktop app you can connect Google (Gmail, Calendar, Drive, Classroom and Meet), Microsoft 365 (Outlook mail and calendar, OneDrive and Teams chats), Notion, Slack, CalDAV calendars, a folder on your computer, web pages you clip, and servers you add through the Model Context Protocol (MCP), such as GitHub, Linear or Atlassian.

The desktop app signs in to each service and reads from it directly. The sign-in stays in your computer's keychain; we don't hold it on our servers.
What it reads depends on the service: email in your inbox (not promotions), calendar events, recent documents and files, class assignments and announcements, meeting records, chat previews, page text, or whatever an MCP server's tools return. Microsoft sign-ins made with desktop versions up to v0.1.53 also granted permission to read SharePoint sites, which no feature uses; later versions do not ask for it and never use it. Microsoft keeps an older grant, including that permission, until you remove Aurum at account.live.com/consent/Manage (a personal account) or myapps.microsoft.com (a work or school account).
With cloud AI, what a connector reads is sent to Gemini to sort it and turn it into proposed pages and tasks. Nothing is added to your Life OS until you approve it.
Sending an email, creating or changing a calendar event, creating a document or posting a message always waits for you to approve it. Tools on MCP servers ask first unless you allow them.
Fetching on a schedule is off until you turn it on for a service.
Disconnecting a service deletes its sign-in from your computer. For Google it also asks Google to revoke Aurum's access, and from the desktop release after v0.1.53 it does the same for Slack and Notion. From that release, none of these is revoked while another Aurum connection on the same computer uses the same sign-in (the app says so when you disconnect), and the app tells you if the service did not confirm it. For Microsoft 365, calendar app passwords and MCP servers, and for Slack and Notion in earlier versions, remove Aurum's access in that service's own account settings; from the same release the app tells you where when you disconnect.

Aurum Life's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We don't use data from Google Workspace services to develop, improve or train AI or machine learning models, and no person at Aurum reads it unless you ask us to for support, it is needed for security, or the law requires it.

Information received from Microsoft 365 through Microsoft Graph (mail, calendar, OneDrive files and Teams chats, under the permissions shown on Microsoft's consent screen) is used only to show it inside your Life OS and to answer what you ask the agent. We don't use it to develop, improve or train AI or machine learning models, we don't sell it or share it with third parties, and no person at Aurum reads it unless you ask us to for support, it is needed for security, or the law requires it. The app never deletes mail or events permanently on your behalf.

The QuickBooks Online connector is not available in current releases. When it is, it reads your company details, recent invoices and a profit-and-loss summary to show inside your Life OS, never writes to QuickBooks, and is revoked at Intuit when you disconnect. QuickBooks data is never used for advertising or model training.

If you connect an app such as Claude Desktop to your Life OS through Aurum's MCP server, what that app reads is sent to its provider under your agreement with them, not ours.

Cloud backups

If you choose Sync & merge for a Life OS, the desktop app uploads a backup of its folder to our storage once a day, and you can also back up by hand. A backup is a ZIP file of the whole folder: everything in it, including chat history, the agent's memory, your profile, the log of what the agent did, and any other folders in your Life OS, apart from the app's database and search index, its usage logs, earlier backups and any file over 100 MB. We do not encrypt the ZIP before it is uploaded; it is stored privately, readable only through your account, and encrypted at rest by our storage provider. Backups older than your retention setting (30 days unless you change it) are deleted after each new one, and the three newest are always kept. You can turn backups off, change the schedule and delete any backup in Settings → Cloud.

Shared workspaces and organisations

What you add to a shared workspace (pages, tasks, comments, files, and edits made together in real time) is stored on our servers and visible to its members. Members see your name, email address and role, and any GitHub username you added. A workspace keeps a feed of activity, and its admins can read a record of what agents did there: the time, the tool, the decision and the outcome, without the text of what was written. If you ask to join a space, its owners and admins receive your email address with the request. When you invite someone, we email them your name, the space's name and a link. An organisation's admins can see its members, their roles and their use of AI credit.

Agents you connect

An agent using an agent key sends its proposed changes to our servers, where they wait for a decision. We keep each proposal with what was approved, who decided and when, for as long as the workspace exists, and a step-by-step record of how it was handled for 90 days.

The mobile app

The mobile app works with your synced Life OS. It reads your pages and tasks from our servers and sends back the changes you make. Text captures go to our servers so the desktop app can import them. Photos and voice recordings attached to a capture are uploaded to private storage and kept while the capture exists; they are deleted about a week after you delete the capture, and an upload that never became part of a capture is deleted after 90 days. Voice notes are transcribed by Gemini. If you allow notifications, we store a push token for your phone and send reminders and the notifications you turn on through Expo, which passes them to Apple or Google. The assistant in the mobile app uses cloud AI unless you download a model to the phone; it sends your message, the conversation, your profile, a count of the projects and tasks in each pillar, and what its tools read from your synced Life OS. Your chats with it are stored on the phone, never on our servers.

Pictures in chat replies, notes and captures that are stored with your Aurum data load on their own. From the mobile app update that added the Crash reports switch, a picture hosted anywhere else shows a "Load image" button with the name of the site, and loads only when you tap it; loading it lets that site see your phone's network address. In earlier versions such pictures loaded on their own, as they do in the desktop app.

Payments

Payments are handled by Stripe on Stripe's own pages; we never see your full card number. We keep your plan, its status, your credit balance and a record of credit purchases. If you turn on automatic top-ups, Stripe keeps your card on file and we charge it within any monthly limit you set. Stripe processes payment data under its own privacy policy as well.

Email

We send account and security emails (confirmations, password resets, sign-in links), a welcome email, and workspace and organisation invitations through Resend, which delivers them through Amazon Web Services. We don't send marketing email. If you joined our waitlist in the past, your email address is held in our contact system (HubSpot); email us to be removed.

Who processes data for us

These providers process personal data on our behalf, under their data processing terms: Supabase (database, sign-in, file storage and server functions, on Amazon Web Services in the US), Cloudflare (the network in front of our servers), Google (Gemini AI, and Google Search for research), Tavily (web search), Stripe (payments), Resend (email), Sentry (crash reports), Expo (push notifications), Render (hosting this website) and HubSpot (past waitlist signups). Apps and services you connect, and the app stores, process data under their own terms, not ours. The full list, with each provider's role and location, is at aurum-life.com/sub-processors. We don't sell personal data or share it for advertising.

Diagnostics

The desktop app can send two kinds of diagnostic data, and neither contains your notes, tasks, chats or keys:

Crash reports (via Sentry): the error and the code path that led to it, the app version, your operating system and its version, your computer's model and its name on your network, and short "session started" signals that tell us how often the app runs without crashing. Your operating-system username is removed from file paths, and the app's interface also removes note file names, but folder names can remain. Reports are not linked to your account.
Install and launch count (in our own database): a random identifier for the installation, the app version, the operating system and the update channel, sent when the app is installed or updated and each time it opens. Our servers add the country your connection comes from. It is never linked to your account. Separately, if you agreed to diagnostics, installing a template or starter pack while signed in records which one against your account.

When these are sent depends on the app version, and we state the history plainly because it changed:

Up to v0.1.47: crash reports were off unless you turned them on; the install and launch count was on unless you turned it off.
v0.1.48 to v0.1.50 (September 2026): both were on by default, with switches in Settings → Privacy, and the app showed a notice after setup. An earlier version of this policy said crash reports were opt-in during this period; that was wrong.
From v0.1.51: nothing is sent until the first screen of setup asks you, and "Don't send" is a one-click answer. Existing installs were asked once on their next launch.

In every version, Settings → Privacy turns each one off, and the change takes effect immediately.

The mobile app also sends crash reports to Sentry. You can tell which kind of app you have from Settings → Privacy & Data: the update that changed this added a Crash reports switch there. The version number alone may not tell you, because the update can reach phones without changing it. Before that update the app sent crash reports, with performance samples, without asking and with no switch to stop them. Besides the error, the phone's model and operating system, the app version and short session signals, such a report could carry the label of a control you had tapped, or up to 64 characters of the text on it (a task's title, for example); on iPhone, the text of a text field you had just used; and the full addresses of requests the app had made, including anything after the "?", such as search words. Since that update, nothing is sent until you answer "Send crash reports?", and every installation is asked once. Settings → Privacy & Data → Crash reports turns it off, and new reports stop immediately; a report already being sent at that moment may still arrive. A report then holds the error and where in the code it happened, the app version, the phone's model and operating system, which kind of control was tapped (never its label or text), which server addresses were contacted (without anything after the "?" and without request contents), and whether the session crashed; for one session in ten it also holds start-up and request timings. It holds no notes, tasks, chats or captures and is not linked to your account.

This website

This site counts visits with its own tool rather than a third-party analytics service. It sets no cookies and stores nothing in your browser to count you. Each time a page loads it picks a random number, which your browser holds only in that page's memory. It sends the number to us with the page you visited, the operating system it detected, and any click on a download link, so one visit's steps can be counted together. We store the number with those events. A click on a "Start a pilot" button is sent the same way and may be stored with the number too. Your browser forgets the number when you reload or close the page, so your next visit gets a new one, and the number is not linked to an account. Our servers add the country your connection comes from. If your browser sends Global Privacy Control or Do Not Track, the site sends none of this.

Earlier versions of the site kept a random identifier in your browser's local storage so they could recognise a returning browser. The site no longer does, and every page of it deletes that identifier the next time you open one. If you sign in on this site (at aurum-life.com/account, /approvals or /capture), your session is kept in your browser so you stay signed in, and an invite link looks for that session only when you choose to claim the invite in your browser. Those pages, and the password-reset, email-change and invite-acceptance links we email you, load the sign-in library, which checks that your browser's storage works by writing and removing a test entry; the reset, email-change and invite-acceptance pages keep nothing there. No other page loads it. The download page asks GitHub for the latest release, and the installers download from GitHub, so GitHub sees your network address when you use that page. Every font on the site is served from our own site. If you email us, we keep the email to answer it.

Legal bases (UK GDPR)

Contract: to give you the account and the features you use, including sync, cloud AI, backups, shared workspaces, connectors and payments.
Consent: for desktop diagnostics from v0.1.51, mobile crash reports from the mobile app that has a Crash reports switch, notifications on your phone, and scheduled work in the cloud. You can withdraw consent at any time; it stops that processing from then on.
Legitimate interests: to keep the service secure and working (sign-in and security logs, rate limits, server logs), to understand how the website and apps are used (visit and install counts, and crash reports sent by the mobile app before it had a Crash reports switch), and to answer you. You can object to any of these by emailing us.
Legal obligation: to keep records of purchases for tax and accounting, and to respond to lawful requests.

Retention

Your account and profile: until you delete your account.
Your phones' push tokens: until you delete your account, until another account signs in on that phone and registers it for notifications, or until the notification service reports the token no longer works. From the mobile app update that added the Crash reports switch, signing out of the mobile app also removes that phone's token.
Synced pages, tasks and events: until you delete them. When you delete or archive one, its content stays on our servers for 30 days. After that we clear its text, properties, search fingerprint and title (a title stays while the item still has a live item inside it), and the same words in its change history, in a shared workspace's activity feed and in the live co-editing copy. What stays is the item's ID, kind, workspace, its place in your structure, its dates, when it was deleted, its file path within your Life OS (which usually includes the file name) and, for a task, its due date, priority, repeat, completion and owner. Those stay until you delete your account, or, in a shared workspace, for as long as the workspace exists. The clearing does not reach comments on the item, agent proposals and the shared workspace agent activity record that mention it, or notifications about it; those can keep its name, path or text for as long as each is kept below. From the desktop release after v0.1.53, restoring or unarchiving an item uploads its content again from the file on your computer; in earlier versions the cloud copy of an item restored after its content was cleared stays empty until you next edit it. Older versions in the change history are deleted after 180 days, except each live page's latest text and the records a replaying device needs to rebuild your structure.
Shared workspace content, comments, activity and agent proposals: for as long as the workspace exists, including after you leave it or delete your account. For a page or task deleted in the workspace, the 30-day clearing above reaches its content and the activity feed, not comments or proposals.
Agent memories and learning progress: until you delete them or your account. Flashcard and quiz files synced for the mobile app, and comments on a page that was deleted, stay until you delete your account.
Scheduled-task results, deep research reports and agent step records: 90 days.
The agent activity record for shared workspaces: 365 days.
Notifications: 90 days after they arrive once you have read them; unread ones until you read them or delete your account. A notification can keep a page's path and up to 280 characters of what it was about, even after that page or task is deleted.
Connector items processed in the cloud: 30 days after you apply or dismiss them; items you never act on, until you delete your account.
Cloud backups: as set in Settings → Cloud (30 days by default, always the newest three), and until you delete your account. A backup taken before you deleted a page still contains it until that backup is deleted.
Capture photos and voice recordings: while the capture exists, and deleted about a week after you delete the capture. An upload that never became part of a capture is deleted after 90 days.
Files left under an account that no longer exists (cloud backups and capture files): deleted by a nightly sweep.
Voice session records: 13 months.
Invitations, including the invited email address: an accepted invitation is deleted 30 days after it is accepted, and one that was withdrawn, expired or never answered is deleted 30 days after its expiry date. An invitation that can still be accepted is kept.
Records of credit purchases: for as long as tax and accounting law requires, which is at least six years.
Install and launch counts, and website visit counts: 13 months. None is linked to an account once the account is deleted.
Template installs: we keep the record of which template or starter pack was installed without a time limit today. It is not linked to an account once the account is deleted.
Crash reports: up to 90 days at Sentry.
Our sign-in provider's security log: 90 days. Your entries are erased when you delete your account.
Server logs: about a week.
The record that an account was deleted (a one-way fingerprint of the account ID and the time): indefinitely, so we can show a deletion was carried out.

Deleting your account removes everything in this list that is tied to it, except where the list says otherwise. The account deletion page has the details.

Your rights

You have the right to access, correct, delete and export your data, to restrict or object to how we process it, and to withdraw consent. Several of these are self-service, in the apps and at aurum-life.com/account:

Export: "Export my data" (desktop: Settings → Privacy; phone: Settings → Privacy & Data; web: your account page) downloads, as one file, most of what our database holds about you: your profile, synced content and its change history, memories, scheduled-task and research results, agent and approval history, voice session records, learning progress, notifications and their settings, template installs and ratings, credit purchases and subscriptions, the spaces and organisations you created, your memberships, comments and activity, connector jobs, and the devices registered for notifications (without their push tokens). The file also lists what it deliberately leaves out and why, such as two-step recovery code hashes, sign-in secrets and token values, and other people's notifications and invitations that you caused. Each table holds up to 20,000 rows, the newest first where there is an order in time; a table cut at that limit is named in the file with its real row count. The file does not include our sign-in provider's security log, stored files (capture photos and voice recordings, and cloud backups) or the payment records Stripe keeps. For any of those, or the rest of a table cut at the limit, email us: nothing produces them automatically, so we answer such a request by hand, within the month the law allows. Your Life OS folder is already yours, and backups can be downloaded in Settings → Cloud.
Delete: see deleting your account for deleting your account or only some of your data.
Correct: edit your content and profile directly.
Stop processing: switch the assistant to Local, disconnect a service, turn off backups, notifications or diagnostics, or turn off the consents for scheduled work.

For anything else, email privacy@aurumtechnologyltd.com. We will confirm it is your account and reply within one month. If you are in the UK you can complain to the ICO; elsewhere, to your local data protection authority.

International transfers

Our servers are in the United States, and most of our providers process data there; Google may process AI requests in other countries where it operates, and Cloudflare's network is global. When we transfer UK personal data abroad, we rely on the UK's data bridge with the United States for providers certified to it, and otherwise on the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses in the provider's data processing terms.

Security

Connections to our servers are encrypted in transit, and our database and storage are encrypted at rest by our providers. Access rules in the database let each record be read only by its owner or by the members of the workspace it belongs to. The desktop app's database is encrypted with a key in your operating system's keychain, and sign-ins are kept in that keychain. Two-step verification is available for your account. Text that arrives from email, calendars, websites or teammates is marked as outside content when the AI sees it, and after reading it the agent asks before using connected-service tools that would otherwise run without asking. Your data is not end-to-end encrypted: our servers can read what is synced, backed up or sent for AI processing, which is what lets those features work. No system is perfectly secure. To report a vulnerability, email security@aurumtechnologyltd.com.

AI and automated decisions

The assistant works for you on your own Life OS. With the default setting it makes ordinary edits straight away, and they can be undone; it asks before a round of more than five changes, before deleting or overwriting anything, before sending anything through a connected service and before setting up scheduled work. "Ask before every change" in Settings → AI → Agent approvals makes it ask every time. AI output can be wrong, and it is not professional advice. We don't make decisions about you by automated means that have legal or similarly significant effects.

Children

Aurum Life is for people aged 18 and over, and we don't knowingly collect data from anyone younger. From the desktop release after v0.1.53 and the mobile app update that added the Crash reports switch, the screen where you create an account says that creating it confirms you are 18 or older and agree to the Terms and this policy, with links to both. So does the page on this website where someone invited to Aurum sets a password to create their account. We don't verify age. If you believe a child has given us personal data, email us and we will delete it.

Changes to this policy

We will tell you about material changes in the app or by email before they take effect, and the date at the top of this page shows when the policy last changed. For this version, the desktop release after v0.1.53 and the mobile app update that added the Crash reports switch show a one-time notice, "We've updated our Privacy Policy and Terms", with links to both. The desktop app shows it on a computer where Aurum was used before this version, or where someone signs in to an account made elsewhere, and remembers that you dismissed it on that computer. The mobile app shows it to accounts created before this version was published, and remembers each account's dismissal on that phone, so another phone shows it again.

Contact

Aurum Technology Limited
Company no. 17127517 (England & Wales)
Registered office: 167-169 Great Portland Street, Fifth Floor, London, W1W 5PF, United Kingdom
Privacy: privacy@aurumtechnologyltd.com
Security: security@aurumtechnologyltd.com

← Back to home