Privacy policy

Last updated 17 October 2026 · bmvp.ai Ltd

Who we are

Treasynx is published by BMVP.AI LTD (trading as bmvp.ai), a company registered in England & Wales (company no. 17126191), registered office 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, registered with the Information Commissioner's Office under reference C1898705. For the purposes of UK GDPR we are the data controller for the limited processing described below.

Privacy questions: support@bmvp.ai
Formal or legal notices: legal@bmvp.ai

What stays on your device

The following never leaves your phone unless you explicitly export or sync it:

• Tasks, times, durations, categories and notes
• Saved planners and work-pattern templates
• Chronotype questionnaire answers and results
• Hourly rate, currency choice and time-value figures
• Hobbies, wellbeing entries, gratitude notes
• Fitness, food and health diary entries (unless you explicitly send them to an AI provider — see below)
• Finance holdings, watchlists and portfolio data
• Money data: your typed balance, bills, income, imported statements, transactions and savings goals
• Business records: clients, projects, billable time, invoices, quotes, expenses, receipt photos, mileage and the tax pot, for every business you set up
• Treasynx Intelligence: what it has learned from your entries, and its log of suggestions and your thumbs up or down
• Hobby sessions, hobby projects and your reading progress
• Everything you enter in the Singularity tools
• Home plan: the food you add (names, kinds of food, where it is kept, dates, quantities and your own prices), photos you add to items, barcodes you scanned and the product names found for them, the shopping list, and what you marked used, frozen or binned
• Your Prompt Forge library
• Streaks, XP, levels and badges
• Your six daily ring targets, the minutes you did each day (up to 400 days) and the trophies you have unlocked
• The NFC tags and Tag Rails your phone has seen, the names you gave them, any action you changed, and your last 200 taps
• Any AI provider API keys you enter
• Your theme, colour and alert preferences
• The learned profile and episodic memory

This is held in your app's private storage, which other apps cannot read. Uninstalling Treasynx deletes it. We cannot recover it for you, because we never had it.

What leaves your device, and when

Treasynx contacts other services only for specific features. Each one is listed here with what it receives.

Bring your own AI key

Treasynx does not operate an AI service. If you use the AI features you supply your own key, and your request goes straight from your phone to that provider, governed by their privacy policy rather than this one. It is worth reading the one that applies to you.

AI features are off until you set them up, and the planner works without any AI. For how AI works in Treasynx, what is sent and how AI output is labelled, see AI in Treasynx.

Sixteen are supported: Anthropic, OpenAI, Google Gemini, Grok (xAI), Groq, DeepSeek, Mistral, OpenRouter, Together, Fireworks, Cerebras, Perplexity, DeepInfra, and any other OpenAI-compatible endpoint — plus two that involve no third party at all: Ollama or LM Studio on your own machine, where nothing leaves your network, and the on-device model, where nothing leaves your phone.

Two are worth flagging rather than burying in a list. DeepSeek is operated from China, so your prompts would be processed there. Perplexity searches the web to answer, which means your prompt shapes outbound searches. Neither is a reason to avoid them; both are a reason to choose knowingly.

Money, business and Treasynx Intelligence

The money tools, Finance, the business tools, Treasynx Intelligence and the Singularity tools work on your phone, from your own entries. No AI is ever sent your money or business data: no prompt is built from a balance, transaction, merchant, holding, client, invoice or amount. There is no bank connection and no account linking, and nothing moves money. A statement file you import is read on the phone and never uploaded.

Treasynx Intelligence learns from your entries on the phone. Every suggestion shows the figures behind it, nothing is changed until you confirm, and its log can be deleted. A document such as an invoice or report leaves the phone only when you tap Share and choose where it goes.

The figures these tools show are estimates from your own entries, for planning only. They are not financial, investment, tax or legal advice.

Running the AI on your phone instead

You can install a small language model on the device and use the AI features with no key, no account and no network at all — aeroplane mode is a valid way to run it. In that configuration nothing about your schedule leaves the phone, which is a property of the wiring rather than a promise you have to trust.

We do not supply or host the model. You download it from its publisher and accept their licence — for the Gemma models, Google's Gemma Terms of Use. bmvp.ai Ltd is not a party to that licence and does not check it; complying with it is between you and the publisher. The file lives in the app's private storage and no new phone permission is required.

If you switch on local training, a small scorer is trained on your phone from which plans you keep, and used to choose between drafts. That training never leaves the device. It is not the language model changing — no phone can retrain a language model, and we do not claim otherwise.

Treasynx AI

Treasynx AI is a small AI model made by bmvp.ai Ltd. From version 1.2.1 it is available in the app as an option. It is off until you choose it in AI settings, read the first-use notice and tap Download; nothing is downloaded for it before then. It does four planning jobs (help answers, quick capture, duration estimates and the weekly review); everything else uses the AI provider you choose. See AI in Treasynx.

The model runs on your phone. What you type into it, and your plans and other content, are processed on the phone and are not sent to us or anyone else.

The download. When you tap "Check for Treasynx AI", your phone fetches a small signed list of versions from treasynx.com, which is hosted by GitLab (see Website visitors and hosting). When you tap Download, the model file (about 640 MB) comes from models.treasynx.com, which is served by Bunny.net (BunnyWay d.o.o., a company in Slovenia, in the EU), with the files stored in the UK. Like any download, Bunny.net receives your phone's IP address so that it can deliver the file. We have switched off Bunny.net's request logs, and no other information about you is sent. We receive nothing about who downloaded the model.

It is trained on synthetic examples and on examples we write ourselves, with no personal data. Data from Help improve Treasynx could be used for it only if you tick both boxes, and then only as totals that each combine at least 20 people. Energy ratings and any text anyone wrote are never used to train it. You can remove the model at any time in AI settings → Treasynx AI → Remove.

Fitness, food & health data

Treasynx includes optional diaries for movement, meals and daily health (sleep, energy, mood, soreness, water, weight). All entries are stored locally on your device and are never uploaded to us. Health data is special category data under Article 9 of the UK GDPR, and each diary is off until you switch it on individually.

Health diary entries go to your AI provider only if you switch on AI sharing in Health. That optional AI suggestions feature inside the wellness screen is the one path by which health data can leave your device. This requires its own separate consent — beyond the general AI setup — and you are shown exactly what will be sent before each request. Health entries are never added to the general AI context used by the planner, the agent, the chatbot or the chief of staff. The wellness screen builds its own prompt, on its own consent.

Weight logging is behind a further switch and an age confirmation (self-declared, 18+). There are no calorie figures, no targets, no BMI, no body-fat estimates, and no gamification of food or body metrics. A safeguard watches for patterns that may indicate disordered eating and suppresses AI suggestions when one is detected, showing support information instead.

Voice input

The microphone in the schedule interview is optional and does nothing until you tap it. When you do, Android passes the audio to your phone's speech recognition service, which on most phones is Google's and works by uploading the recording for transcription. We never receive the audio, never store it, and cannot see it — but it does leave your device, and it goes to a company you did not pick as an AI provider. The first time you tap the microphone the app explains this and asks. Typing produces exactly the same result.

Help improve Treasynx

This is one of only two features in Treasynx that can send anything to us (the other is pseudonymous (linked only to a random ID made on your phone) usage statistics). What it sends is pseudonymous too: linked only to a random donor ID made on your phone. It is off unless you tick it on the Help improve Treasynx screen (Plans & data → Your data, or AI settings). There is no prompt, no reminder, and nothing in the app works worse if you decline.

Sending is not switched on in the current version of the app. You can read the screen, preview the data and record your choice, but nothing leaves your phone for this feature yet. When it is switched on, the summaries go to our processor Supabase, which hosts our database in Ireland (EEA); this page will say so here first.

Two separate choices

1. Share pseudonymous usage patterns to improve the app. A pseudonymous weekly summary of how the app is used (linked only to a random donor ID made on your phone), used to find what works, what confuses people and what to fix. We combine summaries into totals, each from at least 20 people. An AI service (Groq) looks only at those totals and suggests what to improve, and the developer gets the findings each week by Telegram. They don't include your summary or your donor ID.
2. Also use these patterns to train Treasynx AI. Treasynx AI is our small, optional AI model that runs on your phone. If you tick this, the weekly summary above and the twelve-number plan shapes (from plans you keep, edit or reject) may be used to train and test it. Needs the first box. Suggestions for improving Treasynx AI, such as typical block lengths, come only from totals of at least 20 people, and the developer approves each version of the training data before it is used. Never sold, and it can be unticked on its own.

Both boxes start unticked. Each summary records which choices were in force when it was sent, and only summaries sent with the second box ticked may be used for AI training or evaluation.

What is collected

• The app version, your plan (Free, Pro, Advanced, Home, Super, Infinite or Singularity), the app language, Simple or Pioneer mode, and your phone's region setting — a country taken from the language settings, never a location, and only for common countries.
• For each day, by weekday but with no date: the number of blocks as a range, the share of each built-in block type (study, work, exercise and so on), how many you finished, the first and last block rounded to 30 minutes, whether your buffer held, and counts of running late, reshuffles and restarts after time away.
• For the week: block-type balance, measured-versus-planned time and estimate accuracy per block type, energy ratings averaged by time of day (only if you rate energy), which screens were opened by their code name and how often, timer, notification and AI use as counts, the type of AI provider (such as on-device or self-hosted), and streak lengths as ranges.
• A random donor ID made on your phone (see below).

What is never collected

• Any text you or an AI wrote: task titles, notes, names, journal entries, prompts, AI answers.
• Money amounts, or anything from Money, Finance or Business — clients, invoices, expenses and so on. Money and business data never leave your phone and never go to an AI.
• Health, fitness, food or wellbeing entries.
• Contacts, calendar event titles, photos or files.
• Your location, device identifiers or the advertising ID.
• Exact dates or times.

To keep rare values from singling anyone out, counts are sent as ranges, ratios are rounded and need at least two examples, rare block types are folded into "other", screens opened only once in a week are left out, and uncommon regions are omitted. See exactly what's sent in the app shows the full JSON built from your own last seven days before anything is sent. Summaries are sent at most once a week, only on an unmetered network such as Wi-Fi.

Purpose, basis, processor and retention

• Purpose: improving the app (choice 1) and, only with choice 2, training and testing Treasynx AI, our optional on-device AI model.
• How summaries are used: we combine them into totals, each from at least 20 people, with small random changes to the counts. Once a week, a report of these totals is sent to the developer in a private Telegram chat, with improvement suggestions that an AI service (Groq, United States) writes from the totals alone. Neither service is sent any summary, donor ID or text you wrote. Totals from people who ticked the second box may also be used to adjust Treasynx AI, for example its typical block lengths, after the developer approves each set. Combined totals are kept for up to 18 months.
• Controller: bmvp.ai Ltd.
• Lawful basis: your consent, Article 6(1)(a) UK GDPR, given separately for each choice and withdrawable at any time.
• Where it is stored: with our processor Supabase, which hosts our database in Ireland (EEA), under a data processing agreement.
• Retention: up to 18 months from receipt, then deleted, or aggregated further so that it no longer relates to any donor ID.
• No sale, no advertising: it is never sold, never shared for anyone else's own use, and never used for advertising — there is no advertising in Treasynx.
• Age: this feature is for users aged 18 or over.

Withdrawing, deletion and your donor ID

Untick either box at any time and uploads stop at once. Unticking the first also erases the counts kept on your phone and switches the second box and plan shapes off. You are then offered Request deletion, which asks the server to delete everything sent under your donor ID — or, while sending is switched off, tells you that nothing was ever sent. My data → Delete my data held by Treasynx covers this feature too. If you untick the second box, your earlier contributions will no longer be used for training: the app asks our server to delete your plan shapes and to mark your earlier summaries as not for training.

The donor ID is a random identifier generated on your phone. It is not your device ID, not the advertising ID, not the analytics ID, and not linked to any account — Treasynx has no accounts. New ID replaces it, after which earlier summaries cannot be linked to you. That is also the catch: the ID is the only way we can find your summaries to delete them. If you replace the ID, clear the app's data or uninstall without requesting deletion first, we can no longer locate what was sent. So request deletion first, then clear. We would rather tell you that now than discover it together later.

Crash and error reporting

There is no crash-reporting software in Treasynx, and we do not collect crash or error reports. An earlier version of this page said crash reports travelled through our analytics, under the same consent switch; the app never did that, so the claim has been removed rather than left to describe something that does not exist. (Before that, the page once named Firebase Crashlytics, which was never used either.)

Separately, Android itself reports crashes to Google Play if you have Google's "usage and diagnostics" setting switched on. That is controlled entirely by your Android settings, not by us, and we see those reports only in anonymised, aggregated form in the Play Console.

Checking for new AI models

The model optimiser is optional and off by default. Switched on, it asks each provider you already hold a key for which models it currently offers, so it can warn you when the one you use is retired — which would otherwise break your AI features with no explanation. The request carries your key and nothing else: no schedule, no prompt, no personal data. It runs only while the app is open, never in the background, and at the interval you choose.

How AI content is labelled

Tasks and text written by an AI are labelled as AI-generated in the app: an AI-written task carries a visible AI chip, and exports, shared planners and printouts mark those items too, with a note that they contain AI-generated content. When the AI proposes rearranging your day, you review each change before anything is applied; nothing is moved without your say-so.

AI output is checked before you see it — for example, plans are checked against the expected format before they are used — but models can still be wrong, so check anything important yourself.

Reporting AI output

Every AI-generated response carries a control to report it. Choosing a category saves the report in the app straight away. You can then also send it to us, which opens your own email app with a message you can read before it goes. Whether the AI's response is attached is your choice and is off by default, because a response is built from your schedule and can repeat your own notes back. A report without it is still useful — the category and the model are the two things that matter most.

Location

Location is optional and used only for weather, nearby places and hobby conditions. Treasynx requests coarse or fine location only at the point you use one of those features, never in the background, and does not store a location history. The coordinates are rounded to about 1 km and used for the weather or places look-up you asked for (MET Norway or the Overpass API), and are not stored by Treasynx. Places you save yourself are kept on your phone, rounded to about 1 km. Deny the permission and the rest of the app is unaffected — you can search for a place or tap the map instead.

Camera permission (Home plan, optional)

Shelf life, part of the Home plan, can read a product's barcode with your phone's camera. The camera permission is asked for only when you tap Scan, after a short explanation, and never in the background. It is optional: without it you can type the name, or read the barcode from a photo you choose with Android's photo picker, which needs no permission.

• Read on your phone. Barcodes are decoded on the device by an open-source library (ZXing). No Google or other scanning service is used, and camera frames are not saved or sent anywhere.
• Photos stay on your phone. A photo you add to a food item is kept in the app's private storage and travels only inside your own backups (up to a size limit).
• Product names online are off by default. See Open Food Facts in the table above: if you switch the look-up on, only the barcode number is sent.
• You can withdraw the camera permission at any time in Android settings; the rest of the app is unaffected.

Shelf-life dates in the app are estimates from general guidance. The date on the label comes first. They are not food-safety or medical advice.

Encryption on your phone

Everything Treasynx keeps on your phone is encrypted: tasks, notes, health diaries, money and business records, settings, your AI keys and WebDAV password, and your photos and receipts. It is locked with AES-256 under a hardware-backed key held in your phone's secure hardware (the Android Keystore, in a separate security chip such as StrongBox where the phone has one), so the key itself cannot be copied off the phone.

Because that key never leaves the phone, Google's cloud backup and device-to-device transfer are switched off for Treasynx: a copy made that way could never be opened. The app's own encrypted backup is the way to move to a new phone.

If the key is ever lost, for example after the phone's security settings are reset, Treasynx deletes nothing: it sets the locked data aside for 30 days and asks you to restore from a backup.

Backups and encryption

Backups are encrypted with AES-256, with the key made from your passphrase by Argon2id, which makes every guess slow and memory-hungry. The passphrase is never stored and never transmitted. If you lose it, the backup cannot be opened — not by us either. Backups made by earlier versions still restore. Where you put the file is your choice; if you sync it to a third-party service, that service's policy applies to the file at rest.

Your subscriptions are not in the backup. They belong to your Google account, and the app asks Google Play rather than reading a file.

Moving to a new phone

1. On the old phone, make an encrypted backup with a passphrase and save it somewhere you can reach from the new phone.
2. On the new phone, sign in with the same Google account and install Treasynx from Google Play.
3. Restore purchases. Your plan comes back with no new charge, because subscriptions belong to your Google account, not to the phone or the backup.
4. Restore the backup and enter your passphrase.

If you use a different Google account on the new phone, the subscription does not move: cancel it on the old account and subscribe on the new one.

Autosave, and what survives what

Four different questions with four different answers, set out plainly because "will I lose my schedule?" is the thing people most need a straight answer to.

Google's Android backup

Switched off for Treasynx. Google's cloud backup and phone-to-phone transfer do not copy Treasynx's data, because it is encrypted with a key that never leaves your phone and such a copy could never be opened. Use the app's own encrypted backup instead.

Three things are deliberately left out of every backup and autosave: your analytics consent and identifier, your Help improve Treasynx choices and donor ID, and the register of alarms. Restoring a consent is not the same as being asked for one, and restored alarms would list things that will never ring.

Autosave

Autosave has three tiers, and which are on by default differs. The differences are worth reading once.

• Rollback points — on. Written inside the app each time you leave it, encrypted with this phone's key, keeping the last three. They let you undo a bad update or a mis-tap. They do not survive uninstalling — they are an undo, not a backup.
• Autosave to Documents — off unless you switch it on (Android 10 and later). A snapshot is written to Documents/Treasynx whenever you leave the app, at most once every five minutes, keeping the last five. Because that folder is outside the app, the files survive an uninstall. No storage permission is needed and none is requested — Android permits writing to Documents through the media store without one. It is off by default because the files stay after uninstalling, in a folder other apps with storage access can see; they are encrypted, so those apps cannot read them, and they are written only once encrypted autosave is set up. On Android 9 and below this tier is unavailable, because the same write would need a broad storage permission this app should not hold.
• Autosave to a folder you pick — off. Optional, and worth it for two reasons only: to put the file inside a drive you sync so it survives a factory reset, or because you are on Android 9 where the Documents tier does not work. This cannot be on by default, because until you pick a folder there is no folder to write to.

One limitation of the Documents tier, stated here rather than left to be discovered. Android shows an app only the files it wrote itself, and a reinstalled app counts as a new app for that purpose. So your autosaves survive the uninstall but the fresh install cannot see them, and the screen will look empty. Recovery is one step: tap "Restore from a file" and pick the newest one out of Documents/Treasynx in the system picker. Automatic would be better, and getting it would mean asking for a permission that lets the app read your whole device — a worse trade than one tap.

Autosave files are encrypted. Copies in Documents or in a folder you pick are encrypted with a public key, so saving needs nothing from you, and they open only with the recovery code shown when you set up encrypted autosave, or with your backup passphrase if you added it. Other apps that can see those files cannot read them, and we cannot open them either. Passwords and API keys are always left out of autosaves. Until encrypted autosave is set up, nothing is saved outside the app.

Post-quantum encryption for autosave. New encrypted-autosave set-ups use post-quantum encryption (ML-KEM-768) alongside X25519. If you set up encrypted autosave before this was added, tap Add post-quantum encryption on the Autosave card in My data and enter your recovery code once: the code stays the same, and older autosave files still open with it. Until you do, new autosaves keep using X25519 on its own. Backups with a passphrase and the encryption on your phone use AES-256 with no public-key step, so this change does not apply to them.

Seeing everything we hold

Under UK GDPR you have a right of access and a right to portability. Because your data is on your device and we hold no copy, both are answered in the app rather than by writing to us and waiting a month.

Settings → Storage & cache → Your data lists every store the app writes, with a plain-English description of what is in it, its size, and whether it travels in a backup. "Export everything" writes the lot to one file you choose the location of.

Values are deliberately not printed on screen — showing every key's contents would put your API keys and health entries in front of whoever is next to you. The export is the proper route to the actual contents, and it is one tap away.

Your phone's calendar

Optional, off until you ask, and read-only. Treasynx can pull an appointment out of your phone's own calendar rather than making you retype it.

• One day at a time, when you import. It reads the day you are planning, not your year. Today's events go into your day; another day's onto that date in your Treasynx calendar.
• Automatic sync is optional, and off until you switch it on. Then, every hour and when you open the app, it reads today and the next 13 days and brings new appointments in, updating ones that moved or were cancelled. It never changes a block you edited or deleted, and skips all-day events.
• What sync keeps. Only what it needs to avoid adding anything twice: each synced event's id and start time, and the block's time, title and length — on your phone only. It is not in backups, is shown under My data, and is erased by Erase everything. Without sync, nothing is kept: events are shown and discarded.
• Nothing is sent. A calendar event is never placed in an AI prompt.
• It cannot write. The write permission is absent from the app rather than merely unused — a stronger safeguard than a promise not to.

A calendar holds who you are meeting and where, which is more revealing than the schedule this app keeps. So the reason for the permission is explained on screen before Android asks you anything, and declining costs you nothing else.

Your notes, and what the AI can now see

This widens what an AI provider receives, so it is worth reading rather than skimming.

Basalt notes used to be invisible to the AI. They are not any more. When you generate a plan, the app searches your notes for ones relevant to that day's tasks and includes up to four in the prompt — so a note saying "no deep work for an hour after the gym" can actually change tomorrow.

The search runs entirely on your device: word matching over each note's title, tags and body, plus one hop through the links you drew between notes. No embedding model is used and no note is sent anywhere to be indexed — doing that would have quietly turned "your notes stay on your phone" into a false statement.

Note titles are included deliberately, so the model can cite which note it used and you can check it. Retrieval is sometimes wrong, and an uncited wrong note becomes a confident false premise. To stop it entirely, switch off the "notes" context source in AI settings.

Measured durations

Off until you switch it on. With it on, starting and finishing a block records two timestamps on your device, and the app works out how long things actually take you per category against what you planned.

It reports the median ratio, and only where there are at least eight measurements for a category — below that it reports nothing rather than a figure with a caveat. The median rather than the average, because a block cannot take less than no time but can take five times the estimate, so one bad afternoon would drag an average permanently.

What goes to an AI provider is the per-category bias figures, not the individual blocks or their titles. Running over is information about an estimate, not about you.

Time monitor

The time monitor times the block you start, and nothing else. It does not read which apps you use, your screen time, your location or your microphone in the background. The start time, pauses and finish time stay on your phone and are used for two things: the length recorded on the block, and the estimate-learning described above. Nothing is sent anywhere.

Saying a command — “done”, “pause”, “ten more minutes” — works like speaking an appointment: your phone’s own speech service turns the sound into words, and Treasynx receives only the words, which it matches against a fixed list in the app. No audio is recorded or stored.

When its sound plays, the monitor raises your phone’s alarm volume for about four seconds and then puts it back: up to 85% on the speaker and 40% with headphones connected. It never lowers your volume, and you can switch this off on the time monitor screen.

NFC tags and Tag Rails

Treasynx tags are passive NFC stickers (NTAG213) with no battery, which you buy separately (they are not supplied). They never broadcast: data moves only when you touch your phone to a tag.

• What is on a tag: a short treasynx.com link naming one action (for example “start or finish a Work block”), a random eight-character tag id, and for a Tag Rail a random rail id and slot number. Nothing about you, your schedule or your phone. Anyone who reads the tag sees only that.
• What happens when you tap: your phone reads the link and the app does the action on the phone — for example adding a finished block to Today. The feature makes no network calls. If the app is not installed, the phone may offer to open the link in a browser, which shows a page about Treasynx; the action part of the link is not acted on or stored by the website.
• What your phone keeps: the tags and rails it has seen, names you give them, any action you change on that phone, a block a tag is timing, and your last 200 taps. It is in your encrypted backup, listed under My data, and removed by Erase everything.
• Writing tags: when you write or lock a sticker, the app writes only the link and an Android app record. Locking makes the sticker permanently read-only.

Share cards and invites

The daily rings, streaks, XP and trophies are worked out on your phone from the blocks you tick off, and stay there. When you tap Share, the app draws a picture of your rings (the ring names, minutes against your targets and your streak) and hands it to Android’s share sheet with a short message and a Google Play link. Nothing is sent unless you choose an app to share with, and it goes only to the people you send it to.

The Play link on a rings or Wrapped card carries a label saying it came from a shared card, so that Google Play can count installs from shares. It contains nothing about you. The picture is saved briefly in the app’s private cache so the app you choose can read it.

Other screens offer Share as a card too. The picture is drawn on your phone, and money figures and names are hidden until you switch them on in the preview. It leaves the phone only through the share sheet you open.

Invite a friend sends a short message with the public Google Play link, through the share sheet, to whoever you choose. There are no rewards, no referral codes and no tracking, and the app keeps no list of who you invited.

Hobby conditions

When you ask what to do with your free time, the app fetches real conditions and scores your hobbies against them. What it fetches depends entirely on which hobbies you switched on.

The source is MET Norway, which needs no API key and no account. Its forecast gives UV and overnight frost; for sea hobbies, MET Oceanforecast gives wave height, but only for the seas of north-west Europe. Daylight and moon phase are not fetched at all — they are arithmetic the phone does without a network. Air quality, snow depth and soil temperature are not available, because no free source that allows a paid app to use them was found.

Coordinates are rounded to two decimal places, roughly a kilometre: precise enough for weather, imprecise enough not to identify a house. Nothing else is sent — no hobby names, no schedule, no identifier.

The recommendation is computed on your device from rules shown on screen, each with its reason. Your AI provider, if you have one, is then asked to phrase the result and is given the reasons rather than the raw data, so it cannot invent a justification the numbers do not support.

No AI is set up until you set it up

On a fresh install no AI provider is configured, none is enabled, and no AI feature will attempt a network call.

An earlier version got this wrong, and it is worth saying so. The app shipped with a default pointing at a local Ollama address, and because Ollama needs no API key the app believed AI was already configured. Features appeared available then failed, the prompts that would have told you to set AI up never appeared, and the multi-model features thought they had a provider. It is fixed.

Website visitors and hosting

This website, treasynx.com, is hosted on GitLab Pages, run by GitLab Inc. in the United States on cloud servers from Google and Amazon Web Services. When you open a page, GitLab's servers receive your IP address, your browser's user agent (its name and version) and the time of the request, and GitLab keeps access logs of IP addresses, the pages visited and the time, for security and to run the service.

• Lawful basis: legitimate interests (UK GDPR Art 6(1)(f)): keeping the site secure and running it.
• Retention: as set by the host. GitLab's privacy statement currently says access logs are kept for 7 days and then deleted on a rolling basis. We do not run analytics on them.
• Transfer: the logs are held in the United States. GitLab states that it complies with the EU-U.S. Data Privacy Framework and its UK Extension, and uses standard contractual clauses where those do not apply. GitLab's own privacy statement applies to these logs.

Cookies and storage on this website

This website sets no cookies. It has no analytics and no advertising, and loads no third-party scripts or fonts: everything comes from treasynx.com itself.

It keeps two small items in your browser's local storage, only to remember your language choice: treasynx-lang (the language you picked) and treasynx-lang-hint-dismissed (that you closed the “also available in” suggestion). They never leave your device. They are written only when you pick a language or close that suggestion.

Support emails

When you email support@bmvp.ai, an AI-assisted support system helps us answer. The text of your email is sent to Groq (Groq LLC, United States), which sorts it by topic and drafts a reply. Attachments are never sent to Groq.

• Purpose and lawful basis: responding to your request. Where your email is about something you bought or asked us to do, the basis is contract (UK GDPR Art 6(1)(b)); otherwise it is our legitimate interest in answering the people who write to us (Art 6(1)(f)).
• Groq, our processor: Groq acts on our instructions under its data processing addendum. Its terms say it may not use inputs or outputs to train or fine-tune AI models without the customer's permission. Groq says it does not keep inference requests by default, apart from logs it may keep for up to 30 days for reliability and abuse monitoring unless that is switched off.
• Transfer safeguard: Groq processes the text in the United States. Its data processing addendum includes the UK International Data Transfer Addendum to the EU standard contractual clauses.
• Attachments: they stay with us and are not sent to Groq. We get an internal alert on Telegram that contains only a ticket number and a short topic, never your name, email address, order details, message or attachments. Your email and any attachments stay on our own systems: our email provider (Zoho, EU) and our support system's server (Hetzner, Germany).
• Our other processors: Zoho (contracting entity Zoho Corporation Limited, UK) provides email hosting for support@bmvp.ai, legal@bmvp.ai and noreply@bmvp.ai, with the data held in Zoho's EU data centres. Hetzner Online GmbH rents us our support system's server in Germany.
• Human review: for now, a person reviews every reply before it is sent. Refunds and legal or data-protection matters are always decided by a person.
• Cancellations: if you ask us to cancel a subscription, the cancellation may be processed automatically through Google Play. Because refunds are always approved by a person, no decision with legal or similarly significant effects on you is made solely by automated means.
• Retention: support emails are kept until your enquiry is resolved, unless we need them to deal with a legal claim. Emails and records about refunds and cancellations are kept for 6 years.
• Your rights: you have the rights listed under Your rights, including the right to object. If you would rather your email were not processed with AI, say so in your email and a person will handle it.

Deleting your data

Quick route: treasynx.com/delete explains what can be held on our servers and how the app deletes it automatically (My data → Delete my data held by Treasynx).

All your data is stored locally on your device. Uninstalling the app or clearing app data from Android Settings removes everything. The app also provides an "Erase everything" option on the Storage & cache screen.

For Help improve Treasynx summaries and plan shapes held on our servers, untick the boxes on the Help improve Treasynx screen and choose Request deletion, or use My data → Delete my data held by Treasynx, or email support@bmvp.ai with the donor ID shown on that screen. While Help improve sending is switched off, nothing has been sent, so there is nothing to delete.

Lawful basis for processing

Your right to object. Where we rely on legitimate interests (learning how you work): you can object at any time: pause or erase learning in Settings → What this app has learned, or email legal@bmvp.ai.

International transfers

Analytics events, if you enable them, and Help improve Treasynx summaries, once sending is switched on, are stored by Supabase in Ireland, inside the EEA, which the UK recognises as adequate. Supabase's support and infrastructure sub-processors outside the UK and EEA, such as in the United States and Singapore, may access them. That access is covered by Supabase's data processing agreement, which includes UK transfer safeguards (standard contractual clauses with the UK Information Commissioner's Addendum).

This website is hosted by GitLab Inc. in the United States; see Website visitors and hosting for the safeguard GitLab relies on.

The text of support emails is processed by our processor Groq in the United States, under the UK International Data Transfer Addendum to the EU standard contractual clauses. Internal alerts sent through Telegram contain only a ticket number and a short topic, no personal data. Our email (Zoho) and our support system's server (Hetzner) hold data in the EU; see Support emails. Groq also turns combined totals from Help improve Treasynx (each from at least 20 people) into improvement suggestions, under the same safeguard; it receives no summaries, donor IDs or text. The weekly insights report the developer gets through Telegram contains only those totals and suggestions, never your name, donor ID or anything you wrote.

Services your phone contacts directly: MET Norway, the Norwegian Meteorological Institute, is in Norway, inside the EEA. Photon is run by komoot in Germany, inside the EEA. OpenStreetMap map tiles come from the OpenStreetMap Foundation (UK) through a content delivery network with servers around the world, so a tile request may be answered from outside the UK. The Overpass API is a community service run from Germany. Directions are handled by your own maps app under its own terms; Treasynx contacts no routing service. Open Food Facts, used only if you switch on the product name look-up, is a non-profit association based in France, inside the EEA. If you choose a non-UK AI provider or WebDAV host, your request travels to wherever they operate — a transfer you initiate and control by choosing that provider. Voice audio goes wherever your phone's speech service processes it, which for Google's is subject to Google's own policy.

If you download Treasynx AI, the model file comes from Bunny.net (BunnyWay d.o.o., Slovenia, inside the EU), with the files stored in the UK. It receives your IP address only to deliver the file, and its request logs are switched off. See Treasynx AI.

Retention

On-device data lives until you delete it or uninstall. Analytics events are deleted automatically after 12 months, and your phone's events are deleted straight away if you switch analytics off; they are tied only to a random id, not to you. Help improve Treasynx summaries and plan shapes are kept for up to 18 months from receipt, then deleted or aggregated further so they no longer relate to any donor ID, or deleted sooner if you request deletion. Purchase records are kept as long as UK tax and accounting law requires. Support emails are kept until your enquiry is resolved, unless we need them to deal with a legal claim; emails and records about refunds and cancellations are kept for 6 years. Combined totals from Help improve Treasynx, each from at least 20 people and not linked to any donor ID, are kept for up to 18 months.

Your rights

Under UK GDPR you can request access, correction, erasure, restriction, portability, and object to processing. In practice, for most of it you don't need us: your data is on your device, exportable to a file you hold, and deletable by you at any time. For anything concerning analytics, Help improve Treasynx, purchases or support emails, write to support@bmvp.ai and we'll respond within one month.

Automated decisions

We make no decisions based solely on automated processing that have legal or similarly significant effects on you (UK GDPR Art 22). A cancellation you ask for by email may be processed automatically through Google Play; refunds are always decided by a person. See Support emails.

Complaints

To complain about how we use your data, email legal@bmvp.ai with “Data protection complaint” in the subject. We acknowledge within 30 days, investigate, and tell you the outcome. You can also complain to the ICO (Information Commissioner's Office) at ico.org.uk.

Children

Treasynx is for adults aged 18 and over. It is not designed for children, and we do not knowingly collect data from anyone under 18. There is no social feature, no user-to-user messaging and no public profile. The optional Help improve Treasynx feature is restricted to users aged 18 or over. Weight logging and AI-powered food suggestions are restricted to users who have confirmed they are 18 or over.

Changes to this policy

If we change how data is handled we'll update this page and the date at the top, and note material changes in the app's release notes. The current version always lives at treasynx.com/privacy.