Privacy Policy
Your privacy and data security are our top priorities
On this page
Perfumers Vault 2 ("the App") is owned and operated by Drydown Labs Ltd ("we", "us"), company no. 17558784, registered in England and Wales. This page explains what the App keeps on your device, what leaves your device, what we store on our servers, and how to get a copy of your data or delete it. It describes version 2.0.9 of the App and this website. Where version 2.0.8 or an earlier version behaves differently, the section says so.
Everything below describes version 2.0 and later, which changed how PV AI works and added optional accounts. Check your version at the bottom of Settings.
Who We Are
Perfumers Vault 2 is owned and operated by Drydown Labs Ltd (company no. 17558784, registered in England and Wales). We are the company responsible for your personal data.
In November 2026 we took over the App, its user accounts and the data held with them from the previous owner, M24 Media Ltd. If you had an account before then, that is where your account data came from: the previous owner passed it to us, and the account record and everything else described under What We Store on Our Servers is now held by Drydown Labs Ltd on the terms of this policy.
The change of company did not alter what the App collects or what it is used for. Your data protection rights are unchanged, and you now exercise them with us: write to hello@drydownlabs.com, or see Your Rights, Export and Deletion.
Two traces of the change remain. A few technical names still carry the previous owner's name, for example the iCloud container that backups are written to (see iCloud Backup); the App does not show them on screen, so they are names only. And version 2.0.8 is the first iPhone and iPad version published from our own Apple developer account, so you are asked to sign in once more after updating to it: see Your Account.
Data on Your Device
Everything you create in Perfumers Vault 2 is stored in a database on your device. That includes your categories, materials (with their synonyms, replacements, suppliers and safety data sheets), formulas with their revisions and history, PV AI advisory results saved with a formula, making sessions and completed batches, your products and their versions, the shopping cart, orders, custom odour profiles, the companies you enter for product labels and documents (name, address, country, email, phone, VAT number, website and a contact name), the IFRA library on your device, PubChem structures the App has cached, and the App's downloaded copy of the materials catalogue.
Also on the device: your settings, your PV AI consent record, and your PV AI chat transcript. The chat transcript is kept in the device keystore — Keychain on Apple devices, Keystore-backed storage on Android — under a key tied to your account, and holds at most the newest 500 messages. Starting a New chat clears it. On iPhone and iPad, version 2.0.8 cannot read the transcript an earlier version saved, so after that update the chat starts empty; Your Account explains why.
None of this is uploaded anywhere on its own. It leaves your device only when you make it leave: an iCloud backup, a file or PDF export, a QR code, a PubChem lookup (when PubChem Integration is on), a question you put to PV AI (which carries the vault details described under PV AI unless you have switched Let PV AI see my vault off), feedback you send (which carries a copy of your settings, never your formulas or materials), an item you send to another PV user, or a formula you publish on the marketplace. The last two leave a copy of your perfumery work with us, and they are described under Sharing with Another PV User and The Formula Marketplace.
One thing is outside the App's control: your device's own backup. If you have iCloud Backup or a computer backup switched on for your iPhone, iPad or Mac, or Google's backup on Android, the operating system may include the App's data in it, as it does for your other apps. That backup is made by Apple or Google under your own account. It is not sent to us and we cannot read it. You switch it on and off in your device settings.
iCloud Backup and Restore
On iPhone, iPad and Mac you can back up to your own iCloud from Settings > iCloud Backup. Tapping Backup Now writes a single JSON file, named perfumers_vault_backup_<timestamp>.json, into the App's own iCloud container (iCloud.com.m24media.pv2). The container keeps the name it was given under the previous owner; it is still part of your own iCloud account.
The file contains your perfumery data: categories, materials, suppliers, formulas with their revisions and history, PV AI advisory results saved with a formula, making sessions and batches, the shopping cart, orders, your products, the companies you entered, and the IFRA library on your device. Two things are left out because the App can fetch them again: cached PubChem structures and the App's copy of the materials catalogue.
Restore from iCloud reads a backup back and merges it into what is already on the device; a record with the same ID is overwritten. The exception is the IFRA library: if the backup has one, it replaces yours.
Without a Pro subscription the App keeps your three most recent backups and removes older ones each time you back up. With Pro it keeps every backup until you delete it. If the App cannot confirm your subscription at the moment you back up, it applies the three-backup rule.
It is entirely manual. There is no timer, no background upload, and nothing travels between your devices by itself — each device keeps its own database. The only thing the App does unasked is look in your iCloud for an earlier backup during first-run setup, so that it can offer to restore it. That is a read; nothing is uploaded.
The backup goes into your iCloud account, not to us. We cannot see it or read it. To remove one backup, delete it from the list under Restore from iCloud; to remove them all, delete the App's iCloud data in your device settings. Neither touches the data still on your device. For more information visit Apple's privacy policy.
Your Account
An account is optional, and it unlocks three things: PV AI, private sharing with another PV user, and the formula marketplace (version 2.0.8 and later). Everything else works signed out — formulas, materials, categories, IFRA compliance checking, suppliers, orders, exports, QR codes, iCloud backup, the biometric lock, and buying or restoring a Pro subscription.
You sign in through Firebase Authentication with Sign in with Apple, offered on iPhone, iPad and Mac, or with Google, offered on every platform and the only option on Android. We do not offer passwords and never see one. From your sign-in we receive:
- A user ID created for this app. It is given to RevenueCat with your subscription, and it is stored with your PV ID, with each share you send or receive and with any marketplace listing you publish. The App does not show it to other users, but the records that hold it can be read as described below.
- Your email address, as the provider gives it to us. With Sign in with Apple you can choose Apple's private relay address, in which case that is the only address we ever see.
- Your display name, if you allow it. Apple offers the name only the first time you authorise the App.
- The identifier Apple or Google uses for you with this App. Firebase Authentication holds it so that it can recognise you next time. Our server reads it only to work out the one-way hash used for the abuse ledger described below, and does not store it anywhere else.
Signing in also links your subscription record to your account ID, so our server can confirm you have Pro before it runs an AI request.
Your display name has two more uses. Once you share, it is what the person you are sending to sees, and what their notification says. If you publish a formula on the marketplace (version 2.0.8 and later), it is the name every signed-in PV user sees on your listing, it can appear in the notification that announces the listing, and it is written into the note on every copy someone downloads. A listing keeps the name you had when you published it. The listing also carries your user ID: the App does not show it to anyone, but it is part of the record every signed-in copy of the App can read, and it is what lets another user block you. You can change your display name in your profile. Sharing works without one; publishing does not.
You can sign out at any time in Settings > Account > Manage your account, and delete the account from the same screen. Signing out does not cancel your subscription, and it does not delete anything on your device. It leaves this device linked to your account ID at RevenueCat, so Pro keeps working while you are signed out; deleting your account is what removes that link.
Signing in again after updating to 2.0.8 (iPhone and iPad)
Version 2.0.8 is the first iPhone and iPad version published from Drydown Labs Ltd's own Apple developer account. Apple keeps each developer account's keychain separate, so 2.0.8 cannot read what earlier versions stored there. Two things follow the first time you open it: you are signed out, and Home shows a card titled “Please sign in again”; and your PV AI chat history from before the update is not carried over. Nothing was uploaded or moved to make this happen. Your formulas, materials, settings and everything else in the database are untouched, and Android is not affected.
To decide whether to show that card, the App looks only at your own device: whether it was linked to an account for subscriptions, and whether an AI notice had been accepted on it. Nothing is sent to us for this. From version 2.0.8 the App also keeps a yes-or-no marker on the device recording that an account has been used on it.
If you use Sign in with Apple, expect to come back on a new, empty account with a new user ID. Apple gives each developer account its own identifier for you, and the App is now published from ours. Signing in with Google is not affected in that way and should return you to the account you had. On a new account the AI notice is shown again, because acceptance is recorded per account.
An earlier account is not deleted and is not merged into the new one. Its account record, its PV AI notes (until they expire), its PV ID and any shares sent or received with it stay on our servers, and the App can no longer open it, so Export my data and Delete account do not reach it. To have the earlier account deleted, or to get a copy of what it holds, email hello@drydownlabs.com. If it had Pro, the App offers to bring the subscription across: see Subscriptions.
What We Store on Our Servers
Signing in is what creates an account record on our servers. If you never sign in, there is no account record, no PV AI notes and no moderation log. Three things do not depend on signing in: feedback you choose to send (see Feedback You Send), analytics, if it is on (see Analytics), and your subscription record with RevenueCat (see Subscriptions).
Once you sign in, our Firebase project (Google Cloud) holds the following:
- Your account record. Your user ID, email address, display name, the avatar colour you chose, whether PV AI memory is switched on, your PV ID once you have one, which platform you last signed in from, when the account was created and when it was last used. From version 2.0.9 it also holds your answer to the AI notice: which version of the notice you accepted, when the App recorded that, when you withdrew if you have, when the record last changed, and a mark if you accepted in an earlier version of the App and the App wrote it down afterwards. Our server adds to it: whether you currently have Pro, when that expires, when it was last checked and what kind of subscription event last changed it; your AI usage counters; and, if any request of yours, or any formula you tried to publish on the marketplace, has been blocked, safety counters — how many, since when, when the last one was and which rule it matched. The record also carries a role (user, tester or administrator) and, if an account is disabled for abuse, that fact, the reason, and the hashed identifier that links it to its abuse-ledger entry. Only you and our administrators can read it.
- Anything you have shared, and the sharing that supports it. The items you have sent or received and their payloads, your PV ID, the contacts you have built up, the people you have blocked, your registered devices for notifications, and a timestamp used to space sends out. This and the marketplace are the two parts of our database that hold your perfumery data, and Sharing with Another PV User sets out each piece of it. The short notes PV AI saves from your chats are kept there too; What PV AI Remembers describes them.
- Your marketplace listings, and the records that support them. Each formula you have published, readable by every signed-in user; its name and composition reservations; your publishing quota; the marks of what you have downloaded and liked; any report you have filed; and, if a listing is taken down after reports, a take-down record. The Formula Marketplace sets out each piece of it.
- What PV AI remembers. Short notes the assistant has saved from your chats, stored under your account. See the section below — you can read, delete and switch these off.
- Moderation logs. Written only when a PV AI request, or a formula you try to publish on the marketplace, is blocked by our safety checks, and they include a short excerpt of the blocked text. See "Safety Checks" below.
- An abuse ledger. AI usage counts, and a ban flag if an account has been banned for abuse. It is stored against a one-way cryptographic hash of your Apple or Google sign-in identifier rather than the identifier itself, and holds no name, no email and no message text. No app or user can read it.
- A deletion record. If you delete your account, we keep the former user ID and the date. See "Your Rights, Export and Deletion" for why.
- Subscription event receipts. A note that a particular subscription notification was handled, so a repeated delivery is not processed twice. These contain no user identifier and no purchase details.
- Short-lived PV AI request records. For a chat question, a record that lets one automatic retry of the same request, after a dropped connection, go uncharged: a one-way fingerprint of the request, a repeat counter and an expiry 15 minutes ahead. For a question PV AI answers in several steps, a record of how many steps have run, when it started, one-way fingerprints of the conversation and of the last request, and an expiry one hour after the last step. Both are stored against your user ID, hold no message text, and cannot be read by any app or user.
- Feedback you send, whether or not you are signed in. See Feedback You Send.
- Operational logs. Our service writes short technical lines as it works. When something goes wrong, or in a few routine cases such as a note PV AI was not allowed to save or a subscription check that could not be completed, the line usually records your user ID and the error or reason; for a refused note the reason is only the kind of rule that refused it, never the note. When a share notification or a marketplace announcement is sent, the line records the ID of that share or listing and whether delivery worked. And if a subscription notice arrives for an account that has since been deleted, the line records the kind of notice and the former user ID, and the notice is ignored. A log line never contains your prompt, PV AI's reply, or anything from your formulas. Google adds records of its own. When you sign in, Firebase Authentication logs the IP address and app version string the sign-in came from, and Google keeps those for a few weeks. For each streamed PV AI request, Google Cloud writes a line with the time, the outcome, and the IP address and app version string the request came from; it holds no prompt and no reply, and is deleted on the same 30-day schedule as our own lines. These are technical logs, held by Google Cloud on our behalf.
Beyond that, we do not store your formulas, materials, suppliers, batches, chat transcripts, or any photo you send to PV AI. Those are on your device, and — for AI requests — pass through our server without being written down.
There are two exceptions: a share, and a marketplace listing. When you send a formula, a material, a completed batch or your materials library to another PV user, that item's data is written to our database and stays there until one of you deletes it; a share is readable only by the two of you. When you publish a formula on the marketplace, it is written to our database and is readable by every signed-in user until you remove it, until it is taken down after three reports, or until you delete your account. Nothing is shared or published unless you send or publish it. Where the rest of this section describes data we hold about you, these are data you asked us to pass on. They are set out in full under Sharing with Another PV User and The Formula Marketplace.
Where this happens
Our AI service runs as Cloud Functions in Google Cloud's us-central1 region, in the United States. The Gemini model it calls is reached through Vertex AI at a location set on our server: by default that same region, or Vertex AI's global endpoint when the model we have selected is one Google serves only from there. The global endpoint is not tied to a single region. If you are outside the United States, your PV AI requests are processed outside your country either way. Google processes them for us under our Google Cloud agreement and its data processing addendum, both linked in the PV AI section below.
Account records, shares, marketplace listings and the records that support them, feedback, PV AI notes, moderation logs, the abuse ledger, deletion records, subscription event receipts and PV AI request records are held in our Firebase project's Cloud Firestore database, which sits in Google Cloud's eur3 multi-region in the European Union: the data is kept in Belgium and the Netherlands, and a third location in Finland helps keep those copies in step without holding a full copy. The Cloud Functions that read and write it run in us-central1, in the United States, and Firebase Authentication, which holds your sign-in itself, is operated by Google from the United States.
Who can reach it
Access rules on our database allow you to read your own account record and your own PV AI memories, and to delete those memories; our administrators can read and delete your PV AI memories too. A share is readable by exactly two accounts, the sender's and the recipient's, and either of them can delete it. A marketplace listing is readable by every signed-in account, and no app can change one: only our server does, when its publisher publishes or removes it, when other users download, like or report it, and when it is taken down. Your own download and like marks are readable by you alone. Everything else — moderation logs, the abuse ledger, deletion records, subscription receipts, PV AI request records, operational logs, and the marketplace's reservations, quotas, reports and take-down records — is closed to every app and every user, and is reachable only by our administrators. Feedback can be written by the App but read only by our administrators.
Requests from the App carry a Firebase App Check token, which lets our services check that a request came from a genuine build of Perfumers Vault 2 on a genuine device. To issue it, App Check asks Apple (App Attest or DeviceCheck) or Google (Play Integrity) to vouch for the app and the device. App Check does not identify you.
We do not sell personal data, we do not share it for advertising, and there is no advertising in the App.
The Formula Marketplace
Version 2.0.8 added the formula marketplace. It lets you publish one of your formulas for every other PV user to browse and download, and lets you download theirs. It is part of Professional mode and needs an account; publishing also needs a display name. Where a private share goes to one named person, a listing is public inside the App: this is the one feature that shows your perfumery work to people you have not chosen, so it is described here in full. If you are on version 2.0.7 or earlier, the marketplace is not in your copy of the App and nothing of yours can be published.
What a listing contains
Publishing writes one listing record to our database. Every signed-in PV user can read it. It holds:
- Who published it. Your user ID, and the display name your account carried at the moment you published. Changing your name later does not change a listing that is already up. The App shows other users the name and never your email, which is not in the record at all. The user ID is there so that other users can block you; the App does not display it, but any signed-in user’s copy of the App can read it.
- What it is. The listing name you chose (up to 80 characters), an optional description (up to 1,000 characters), the formula’s odour profile and concentration, and how many ingredients it has.
- The formula itself. Up to 200 rows, each with its material name, quantity, dilution, diluent and the row’s notes, plus the formula’s own notes (up to 4,000 characters), product name, created and updated dates, rating, status and revision number. Read your notes before you publish: whatever is written there becomes public. Images never travel, and neither do your suppliers, prices or stock.
- Two fingerprints and a key list. A normalised form of the name, a one-way hash of the composition, and up to thirty normalised ingredient names. Our server uses them to refuse a second listing with the same name, the same composition, or a composition too close to an existing one. The hash cannot be turned back into your formula, and the key list is the same material names that are in the formula anyway.
- Counters and dates. How many users have downloaded it, how many have liked it, how many have reported it, when it was published and last changed, and which version of the publishing terms you accepted (currently version 1).
- Whether it is one of our demo listings. See the end of this section.
What else the marketplace keeps
- Name and composition reservations. For each listing, two small records — the listing ID, your user ID and the date — that hold its name and its composition hash, so nobody else can publish the same thing while yours is listed. No user can read them, and they are deleted with the listing.
- A publishing quota. The times of the formulas you published in the 24 hours up to your latest publish, ten at most, which is how our server holds you to ten a day. You can also have at most fifty listings at a time. Timestamps only; no user can read it.
- Download marks. One record per listing you have downloaded, named after the listing and holding only the date, so a download is counted once however often you repeat it. Only you can read these. The publisher sees the count, never who downloaded.
- Like marks. One record per listing you have liked, holding only the date; tapping again removes it. Only you can read these. Everyone sees the count, nobody sees who liked.
- Reports you have filed. The listing’s ID, your user ID, the reason you chose, any message you wrote (up to 500 characters) and the date. No user can read a report, and the publisher is never told who reported them.
What a listing is used for
A listing is shown to other users in the App with your display name, and is copied into their own database when they tap Download to my formulas. We do not send it to an AI model, we do not use it to train one, and we do not publish it outside the App. As with every other part of our database, our administrators can technically reach it; we look where moderation, support or safety requires it.
When someone downloads your listing, the App writes a note at the top of their copy’s notes saying that it came from the marketplace, on what date, and your display name as it was on the listing. That note is in their database, on their device. Only they can remove it, and it goes wherever they export or share that copy.
Safety checks before a listing goes live
Before a listing is written, our server checks its name, description, profile, product name, notes, and every ingredient’s name, notes and diluent against the same blocklist that screens PV AI requests. If anything matches, the listing is refused, nothing is published, and one entry is written to the moderation log: the date, your user ID, up to the first 500 characters of the text that matched, and which rule matched, with the same expiry as any other entry. Repeated blocked attempts count toward an account being disabled. See Safety Checks and Moderation Logs. The “is this perfumery?” classifier and Google’s safety filters play no part.
Our server also refuses a listing whose name is already in use, whose composition matches a listing already there, or whose composition is too close to one. The refusal names the existing listing, so you know what it clashed with.
Reporting, taking down, and blocking
Any signed-in user can report someone else’s listing once, choosing one of five reasons and adding a message if they want. When three different accounts have reported the same listing, our server takes it down automatically: the listing leaves the marketplace, its name and composition are released, and a copy of the listing is kept with the three reports — each reporter’s user ID, reason and message — for us to review. The publisher is not notified and is not told who reported.
Block this publisher adds them to the same block list that private sharing uses — their user ID and display name, kept privately under your account — and their listings disappear from the marketplace wherever you are signed in. Because it is the same list, they can no longer send you a private share either; shares they had already sent you are hidden, not deleted. On the marketplace the block is a filter in the App rather than a rule on our database: a blocked publisher’s listings can still be read by your copy of the App; they are simply not shown. Unblocking is in your profile, under Blocked PV users.
Hearing about new listings
In Settings > Notifications, New marketplace formulas is off until you switch it on. On, the App asks the system for notification permission if it does not have it, and subscribes this device to a Firebase Cloud Messaging topic for the device’s language (English, French, German, Portuguese, Turkish or Hindi; English otherwise). When another user publishes, one of our Cloud Functions in Google Cloud’s us-central1 region sends a message to those topics. It carries the listing’s name, the publisher’s display name and the listing’s ID so that a tap opens the marketplace, and nothing else. At most one listing is announced per hour, and our demo listings are never announced. If you publish, this is one more place your display name appears: on the notification other users receive.
A topic subscription lives with the messaging service, against the device’s own messaging token. Nothing about it is written under your account and it does not depend on being signed in; the App remembers on the device which topic it joined and with which token. Switch the setting off and the App unsubscribes the device. The same switch puts a card in Notifications for what was published since you last opened the marketplace, and a count on the Home bell for what was published since the later of that moment and the last time the card was shown. Both are worked out on your device from the listings themselves, while you are signed in; the device keeps when you last opened the marketplace, when the card was last shown, and the last count. Clearing the card only moves that date forward.
Removing a listing, and what removal cannot reach
Remove from the marketplace, on your own listing, deletes it and its two reservations at once. There is no timer: a listing stays until you remove it, until it is taken down, or until you delete your account.
Removal does not reach into anyone else’s device. Every download made before that moment is ordinary data in that user’s own database, with your display name in its note, and only they can delete it. The second statement you tick when you publish says exactly this. Treat publishing the way you would treat posting a recipe on a public forum. Turning Allow private sharing off in your profile does not remove or hide your listings.
Deleting your account removes every listing you published with its reservations, your publishing quota, the reports you filed, every like mark (each like comes off that listing’s count) and every download mark (the download counts you added to other listings stay as they are). Two things are kept. If a listing of yours was taken down after reports, the copy made at that moment stays, with your user ID, your display name and the formula. And if a report of yours was one of the three that took a listing down, the copy of your report inside that take-down record stays too. See Your Rights, Export and Deletion.
The demo listings
We published ten formulas ourselves under the name Perfumers Vault, each marked Demo · AI-written. They were written by an AI assistant as examples of what a listing looks like and contain nobody’s data. Like every listing, they are not reviewed.
PV AI
PV AI needs three things: a Pro subscription, a signed-in account, and your acceptance of the AI notice shown in PV AI Settings the first time. Every AI request is something you start — nothing is sent in the background.
From version 2.0.9 your answer to the AI notice is recorded on your account as well as on your device, so that one answer covers every device you sign in on. If you accepted in an earlier version, the App writes that acceptance to your account the next time you open Settings or your profile, or use PV AI, marked as written down afterwards. You can withdraw at any time in Settings > Account > Manage your account with Withdraw consent. From version 2.0.9, declining the AI notice when the App asks you to read it again is recorded in the same way. PV AI then stops working for your account on all your devices, once the withdrawal has reached our server, until you accept again: our server refuses PV AI requests for an account whose record says the consent is withdrawn, including requests from a device still on an earlier version. Withdrawing also deletes the notes PV AI has saved about you. If they cannot be deleted at that moment, for example because the connection dropped, the App says so, and Clear all under What PV AI remembers on the same screen removes them.
In version 2.0.8 and earlier your acceptance is recorded on your device only, against your account ID, and the App does not send it to our server. Withdraw consent there stops PV AI on that device only, until you accept again, and does not delete the notes.
How a request travels
The App sends your request to a Cloud Function we operate, in Google Cloud's us-central1 region. That function confirms you are signed in, that the request came from a genuine copy of the App, that your subscription is active (if that cannot be checked, for example because RevenueCat cannot be reached and nothing was stored earlier, the request is let through), and that the request passes our safety checks and your usage allowance. It then adds our own instructions and — in chat — any notes PV AI remembers about you, and sends the result to Google Cloud Vertex AI, which runs Gemini models inside our own Google Cloud project. The answer returns by the same route.
The practical point: you have no contract with Google for this — we do. Google acts as our supplier, processing your request on our instructions under our Google Cloud agreement.
What is sent
Only what the feature you are using needs:
- Chat: your message and up to twelve earlier messages from the same conversation, so PV AI can follow it. While Let PV AI see my vault is on — and it is on until you switch it off — each question also carries your materials list (for up to 400 materials: the name, the type, the stock level and whether it is a top, heart or base note), how many materials you have, your measurement unit and, when you chat from inside a formula, that formula: its name, its concentration and up to 200 lines, each with the material’s share, dilution, diluent and note tier. Switch it off under What PV AI can see in PV AI Settings and chat sends your messages only.
- Formula advisory: the contents of the formula you are working on.
- AI generation and "inspired by": the description you type or, for a formula inspired by a scanned bottle, what the scanner identified; and, when you limit the AI to materials already in your database, those materials.
- Material enrichment and synonyms: the material name and the details you have entered.
- Bottle Scanner: the photo you take or choose.
- AI formula import: the text, PDF or image you supply — or, if you paste a web address, the page or PDF the App downloads from it. Fetching a pasted address is a request from your device straight to that website, so that website sees your IP address; the App then sends what it downloaded to PV AI.
Before generation, the text of your request is also passed to a smaller Google model that answers one question — is this about perfumery? In chat it is also given up to four earlier messages, each cut to 300 characters, so that a follow-up can be understood. A photo or PDF is never passed to it. Requests that are not about perfumery are refused and do not count against your usage allowance; the refusal is logged as described under Safety Checks.
When PV AI looks things up in your vault
Since version 2.0.7, while Let PV AI see my vault is on, PV AI in chat can also look things up in your vault to answer a question, and can propose changes to it. We switch this ability on from our server, so it may not be active for your account. Each lookup runs on your device, and its result is sent to our server and on to Google with the next step of the same question, for up to eight steps per question. A lookup can return:
- a list of your formulas, or any one formula in full, not only the one on screen: its name, concentration, status, rating and notes, and every line with its share, dilution, diluent and line notes;
- which of your formulas use a material;
- a material’s details: CAS, INCI, type, profile, odour description, your notes, your stock, and the IFRA Standards that match it;
- your supplier names and, for a material, each supplier’s price, stock and product code and name;
- IFRA check results for one formula or across your formulas;
- counts of what is in your vault, which mode you are in and which screen you are on.
Lookups run without asking and are listed with the reply. Anything that would change your vault — creating or editing a formula or a material — waits until you approve it. Lookup results are not stored on our servers; they pass through like the rest of the request. One question counts once against your usage allowance, however many lookups it takes. With Let PV AI see my vault off, none of this runs. From version 2.0.8 the description under that switch in the App says that PV AI can look these things up. In version 2.0.7 it covers only what is sent with every question; lookups can reach further, as listed here.
What is not kept
We do not store your prompts or PV AI's replies. There are exactly two exceptions, both described in their own sections below: the short notes PV AI saves about you, and — if a request is blocked — an excerpt of the blocked text. Photos and PDFs you send are never written to our storage; the App has no file-storage service at all.
We do not use anything you send to PV AI to train AI models, we do not sell it, and we do not show it to other users.
Usage allowance
PV AI has a fair-use allowance, counted per account. The current default is 400 requests in a rolling six-hour window; we can adjust it. Up to version 2.0.8 the App shows how many you have left and when the window resets. From version 2.0.9 it no longer shows a counter, and tells you only if you reach the limit.
Reporting a reply
If PV AI produces something wrong or offensive, use the report action on the reply. It opens an email addressed to hello@drydownlabs.com with only that reply quoted (up to 2,000 characters); for a reply that is only a proposal or a list of steps, the proposal or the steps are quoted instead. Nothing is sent until you send the email, and nothing else from your conversation is included. In version 2.0.7 and earlier the email is addressed to the previous owner's address; change it to hello@drydownlabs.com before you send it, so that it reaches us.
PV AI is optional. If you never sign in, no part of it runs and nothing is sent.
What PV AI Remembers
PV AI saves short notes about you from your chats so later answers fit your work — things like "sells in the EU and follows IFRA 51" or "avoids oakmoss absolute". Our server writes them; the App cannot. Each note is at most 500 characters and is stored under your account, and the notes are included in your later chats so the assistant has the context.
PV AI is told not to note health information, names, contact details, addresses, customers, companies, brands or prices, and our server separately refuses any note in which it detects contact details, health terms, wording that names you, a company or a customer, or wording that reads as an instruction. If you tell PV AI that a note is wrong, it can delete that note itself.
Memory is on by default. In Settings > Account > Manage your account you can:
- read every note PV AI has saved;
- delete any single note, or clear them all;
- turn memory off, after which nothing new is saved and nothing saved is used.
Notes are included in your data export. They are deleted when you delete your account and, from version 2.0.9, when you withdraw your PV AI consent. If that deletion cannot be completed at the time, the App says so and the notes stay until you clear them. There is a cap on how many are kept per account; when it is full, the note you confirmed least recently makes room for a new one.
Notes belong to the account they were saved under. If signing in again after the 2.0.8 update on iPhone or iPad put you on a new account (see Your Account), the notes saved under the earlier account are not shown in the new one and are not used. They stay on our servers until they expire, 12 months after each was last saved or confirmed, unless you email hello@drydownlabs.com and ask us to delete the earlier account sooner.
Safety Checks and Moderation Logs
Every PV AI request is checked on our server before it runs: against a blocklist, against the "is this perfumery?" classifier, and — on the way back — by Google's safety filters and the blocklist again.
From version 2.0.8, the text of a formula you publish on the marketplace — its name, description, profile, product name, notes, and every ingredient’s name, notes and diluent — is checked against the same blocklist before it is published. The classifier and Google’s filters are not involved, because a listing is not sent to an AI model.
When a request, or a marketplace listing, is blocked, we write one log entry. It contains the date and time, your user ID, up to the first 500 characters of the blocked text (your request, PV AI's reply when our own blocklist stopped that reply, or the part of a listing that matched), which rule matched, and at which stage it was blocked. From the server update that came with version 2.0.9, a refusal by the "is this perfumery?" classifier also notes which kind of request it was, how many earlier messages the classifier was given and which model it ran on; a refusal by Google's safety filters notes which model was answering and the safety categories Google reported. On a later step of an agent turn, a Google filter refusal is logged with the step number in place of the text. We keep these to stop deliberate abuse and to find false positives — perfumery chemistry legitimately trips generic safety filters, and we need to see when that happens.
Each entry carries a 90-day expiry and is removed when it expires; 90 days is the current setting and we can change it. Entries are deleted immediately if you delete your account. Only our administrators can read them; no app and no user can.
If a request is allowed, nothing is logged — no prompt, no reply, no excerpt. Repeated deliberate violations can lead to an account being disabled.
Feedback You Send
Settings has a Send feedback form, and now and then the App asks “Enjoying Perfumers Vault?” and offers it. Nothing is sent unless you send it. When you do, one record is written to our database. It holds your message (up to 2,000 characters) and the category you picked (Idea, Problem, Praise or Other), the App version, which platform you are on (iOS, Android or macOS), your device model and operating system version, your language, whether you are in Hobbyist or Professional mode, whether you have Pro, and a copy of your app settings, so we can see the configuration a problem happened in.
The form says so itself: “Your app settings and device model are attached to help us diagnose issues. Formulas, ingredients and API keys are never included.” Before that copy leaves your device the App leaves out anything secret, such as keys, tokens and your chat history, and replaces settings you typed that could name you — company details, names, email addresses, phone numbers, addresses — with the marker “[redacted]”, so we see that they are filled in but not what they say.
If you are signed in, your user ID and account email address are attached so we can reply. Switch on Send anonymously and neither is attached; if you are signed out, feedback is always sent without them. This is the one record the App can write to our servers without an account.
Only our administrators can read feedback. No app and no user can read it back, change it or delete it. It has no automatic expiry, it is not in the Export my data file, and deleting your account does not remove it. If you want feedback you sent removed, or a copy of it, email hello@drydownlabs.com. Feedback sent without your user ID and email address is not filed under your account, so we may not be able to find it. In version 2.0.7 and earlier it is not guaranteed to be untraceable: the settings copy there includes the App’s list of the notifications you have read, which holds the IDs of shares you received (up to 50), and while such a share is still on our servers its record names your account. From version 2.0.8 that list, and the list of notifications you have cleared, are left out of the copy.
Separately, the support options in Settings open an email to hello@drydownlabs.com with your App version already filled in, and on iPhone, iPad and Android your device model too (on a Mac the device model is not filled in). You can delete those lines, and nothing is sent until you send the email. In version 2.0.7 and earlier that email is addressed to the previous owner's address; change it to hello@drydownlabs.com before you send, so that it reaches us.
Subscriptions (RevenueCat)
We use RevenueCat to manage subscriptions across the App Store and Google Play.
RevenueCat receives:
- The purchase receipt issued by the store.
- An app user ID. Before you sign in this is an anonymous ID RevenueCat generates; after you sign in it becomes your account's user ID, which is what lets our server check your Pro status.
- Standard technical details the store and RevenueCat's own SDK collect, such as app version and device type.
The App contacts RevenueCat each time it starts, whether or not you have ever subscribed, to ask whether this device has an active subscription.
The App sends RevenueCat one more thing, and only if you choose to. When you tap Manage Subscription in the App while subscribed, a “Before you go...” box asks why you are thinking of cancelling. Tap Skip and nothing is sent. Tap Submit & Continue and the reason you picked, the comment you typed (up to 500 characters) and the date are saved on your subscription record at RevenueCat, against your app user ID, where we can read them. Apart from that the App sends RevenueCat nothing else about you — no email address, no name, no formulas, no materials. Our server asks RevenueCat whether your account has Pro and stores the answer (a yes or no and an expiry date) on your account record. RevenueCat also notifies our server when a subscription changes, so that record stays current.
Moving Pro to the account you are signed in to
Your subscription belongs to your App Store or Google Play account, but RevenueCat files it under one app user ID at a time. If you sign in to a different Perfumers Vault account from the one that held Pro — which can happen after updating to version 2.0.8 on iPhone or iPad, because that update signs everyone out once (see Your Account) — the App shows “Restore your Pro subscription”. Tapping Restore sends your store receipt to RevenueCat again and asks it to move the subscription to the account you are signed in to now; RevenueCat then tells our server, which updates the Pro status on the account records involved. Until you answer, the App keeps the two account IDs in its settings on your device. If the restore cannot find your subscription, Contact us opens an email to hello@drydownlabs.com with those two account IDs already in it, so we can find the right records; nothing is sent until you send it. The restore prompt and the Contact us email are new in version 2.0.8; version 2.0.7 and earlier have neither.
Analytics
The App includes Google Analytics for Firebase. Whether it starts on or off depends on the country you pick during setup.
- The measurement library ships disabled in both the iOS and the Android build and stays off until setup is finished, so nothing is collected when you first launch the App — not a first-open event, not a session, not an app-instance identifier.
- If the country you pick is in the European Union or the rest of the EEA, or is the United Kingdom or Switzerland, or you pick “Other”, the last step of setup asks “Help improve the app with anonymous usage data”. The switch starts off. If you finish setup without touching it, the answer is no.
- In every other country there is no question: analytics is switched on when you finish setup. This has been the case since version 2.0.5. Earlier 2.0 versions asked everyone, and an answer given then still stands.
- You can switch it off, or back on, at any time in Settings > Analytics > Anonymous Analytics.
While analytics is on, we collect screen views and a set of events that each carry only a category word, never content: app opened; setup completed; mode selected or changed; feature used (which page or quick action); formula action (created, imported, deleted, shared, published, scaled, made, exported and so on); ingredient action (created, edited, imported, deleted, PubChem lookup, AI enrichment); marketplace action (published, refused and why, downloaded, liked, like taken back, reported, publisher blocked, listing removed); share action (sent, imported, revoked or deleted, and what kind of item it was); PV AI request (which kind of task, never the prompt); paywall shown (which feature was locked, or where you opened it from); subscription purchase (how the attempt ended and which plan, and for a completed purchase the price and currency); restore (how it ended); IFRA library action (imported or updated); and your answer to “How did you hear about Perfumers Vault?”, if you gave one. With these go two properties: whether you are in Hobbyist or Professional mode, and whether you have Pro. Most of these events were added in version 2.0.8; version 2.0.7 sends only screen views and the app opened, mode selected and setup completed events. Google's library also records a few events of its own while analytics is on, such as the first open after analytics is switched on, the start of a session, time spent in the App, and app or operating system updates.
Alongside these, Google's library collects the app version, device model, operating system version and pseudonymous identifiers: a Firebase app-instance identifier and, on Apple devices, the identifier for vendor. The identifier for vendor is an ID Apple gives to our apps only — no other developer can see it — and it resets when you delete every app of ours from the device. On Android, version 2.0.7 and earlier can also collect the device's advertising ID, because those builds carry the permission Google's library uses to read it. Version 2.0.8 removes that permission and switches that collection off, so it cannot read the advertising ID. You can reset or delete the advertising ID in your Android settings.
How you heard about us. From version 2.0.8 the App asks “How did you hear about Perfumers Vault?” — on the last step of setup, or later in a small dialog if you have not answered. You pick one of seven fixed answers (“App Store or Google Play”, “Web search”, “Social media” and so on); there is nothing to type. Answering is optional: “Not now” puts it off for two weeks and “Don’t show again” stops it. Your answer is kept in the App's settings on your device, and it is sent to us once, as an analytics event, only if analytics is on at that moment. If analytics is off, it is not sent at all.
Analytics is never linked to your account: the App does not set a user ID for analytics. It carries no formula, material, supplier or chat content. On Apple devices the App does not ask permission to track you across other apps and services, and so cannot read the advertising identifier. There is no advertising in the App on any platform, and where an earlier Android version collected the advertising ID we do not use it for advertising.
Data is processed by Google under their privacy policy. See Google's Privacy Policy and Firebase Privacy Information.
Crash reporting
The App contains no crash-reporting or performance-monitoring library. Apple and Google may pass us aggregated crash and usage reports through App Store Connect and Google Play Console, if you have allowed that in your device settings. Those reports are produced by the platform, not by us, and you can switch them off in your device's privacy or diagnostics settings.
PubChem Lookups
PubChem lookups are part of Professional mode and stay off until you switch on PubChem Integration in Settings and accept its notice. Once it is on, opening a material's PubChem tab looks the material up in PubChem, the free chemical database run by the US National Center for Biotechnology Information. On an IFRA Standard's page a structure is fetched only after you have agreed to the PubChem notice, and then when you tap Fetch from PubChem, which works only while PubChem Integration is on. Every request goes from your device straight to PubChem over HTTPS.
What is sent from a material's PubChem tab is the compound ID if the material has one, otherwise the material's name, its CAS number and, if those find nothing, its synonyms; from an IFRA Standard's page only the CAS number, or the name if there is none, is sent. Each request also carries a fixed label identifying the app ("PerfumersVault/2.0"). No account information, no device identifier and no formula data is sent, and the request does not pass through our servers, so we never see your PubChem searches. For a material, the App keeps none of what PubChem returns; opening the material's PubChem tab looks it up again. For a structure drawing on an IFRA Standard's page, it saves the picture's PubChem address rather than the picture, so the picture itself is loaded from PubChem again when you view it.
IFRA Library
In Professional mode the App keeps a copy of the IFRA Standards on your device. Getting it is a download that you start: you confirm the Download from IFRA notice, and the App downloads the published IFRA Standards overview spreadsheets — the complete overview and any amendments published since — then builds the library from them. If the download fails you can import the spreadsheet yourself.
To know which amendments exist and where to download them, the App reads one small public list from our own servers (our Firebase project on Google Cloud). Since version 2.0.6 it does this at most once a day while you are in Professional mode with the IFRA library switched on, and a read that fails is tried again after an hour. A download reads it first only if its stored copy is more than a day old. The list holds amendment numbers and download addresses, and the request carries nothing from your library or your formulas. If a newer amendment has been published, Home shows “IFRA Amendment … is available: update your IFRA library” under Needs attention, with a Not now button, and the IFRA library page shows a banner. Nothing is downloaded until you accept. Updating adds the new Standards and revises the ones the amendment changed; if your library is older than the complete overview, it is replaced.
Nothing about you is sent. There is no IFRA account, no per-material lookup, and no identifier in the request. The spreadsheets are fetched by your device from the addresses in that list — the address built into the App is on Amazon's CloudFront network — and, as with any download, the server that sends the file sees your IP address. The downloaded Standards are stored on your device.
Why We Use Your Data, and Our Legal Basis
Data protection law lets us use personal data only when we have a legal basis for it. We rely on four. Each use named here is described in full in its own section of this page.
To provide what you asked for (contract)
When you use a feature, we use your data to deliver it under our Terms of Use:
- creating and keeping your account, and recognising you when you sign in again;
- passing a share to the person you send it to, with its notification, and keeping your PV ID, contacts and block list;
- publishing a formula you put on the marketplace, and recording what you download and like there;
- checking whether you have Pro, whether or not you are signed in, and keeping that status current;
- the notifications you have allowed: new shares, which are on once you give the permission, and new marketplace formulas if you switch them on.
Because you agreed (consent)
- PV AI. Your requests, and the vault data that travels with them, are sent to our AI service and to Google only after you accept the AI notice. The notes PV AI saves about you are covered by the same acceptance. See PV AI and What PV AI Remembers.
- Analytics, where the App asks. In the EU and the rest of the EEA, the United Kingdom and Switzerland, or if you pick Other, analytics runs only if you switch it on. See Analytics.
You can withdraw either consent at any time: with Withdraw consent in Settings > Account > Manage your account for PV AI, and in Settings > Analytics for analytics. Withdrawing does not affect anything done before you withdrew, and the rest of the App keeps working. From version 2.0.9, Withdraw consent covers your whole account: PV AI stops on all your devices once the withdrawal has reached our server, and the notes PV AI has already saved are deleted. If the notes cannot be deleted at that moment, the App says so and they stay until you clear them. In version 2.0.8 and earlier your PV AI acceptance is recorded on each device, so Withdraw consent stops PV AI on the device you use it on; if you use PV AI on another device, withdraw there too. In those versions it does not delete the notes PV AI has already saved. To remove them, clear them on the same screen, or email hello@drydownlabs.com and we will delete them.
Our legitimate interests
We rely on our legitimate interests in keeping the service safe and fair, keeping the cost of PV AI under control, finding and fixing faults, improving the App, and keeping it running through the change of owner. We use this basis for:
- safety checks, moderation logs, reports made on the marketplace and its take-down records;
- AI usage counters and the abuse ledger, including the entry that outlives account deletion, and the deletion record;
- App Check, PV AI request records, subscription event receipts and operational logs;
- the marketplace's duplicate checks and publishing quota;
- the send-spacing mark that stops sharing being used to flood someone;
- keeping your user ID, display name and PV ID in another PV user's contacts or block list, including after you delete your account, so that their list and their block keep working;
- delivering this website and the App's public downloads (the materials catalogue and the list of IFRA amendments), where our hosting providers receive your IP address so that the pages and files can be served and kept secure;
- feedback and emails you send us, and a cancellation reason if you choose to submit one, so that we can fix problems, reply to you and understand why people leave;
- analytics in the countries where it is switched on when setup finishes: events that carry a category word and no content, are not linked to your account, and can be switched off in Settings > Analytics;
- taking over your account and its data from the previous owner, M24 Media Ltd, in November 2026, so that the App could carry on without interruption.
We keep these records as small as the purpose needs. You have the right to object to any of these uses: see Your right to object.
To comply with the law (legal obligation)
We use your data where a law requires us to: to answer the requests you make under data protection law and keep a record that we did, and to keep or disclose information when a law or a court requires it.
Do you have to give us your data?
No law requires you to give us personal data, and almost the whole App works without an account. An account needs the sign-in details listed under Your Account; without one, PV AI, private sharing and the marketplace are not available, and nothing else changes. Pro needs your store receipt to reach RevenueCat, because we cannot give you Pro without it, and the App asks RevenueCat at each start whether this device has a subscription, signed in or not (see Subscriptions). Analytics can be switched off, and feedback is sent only if you send it.
How Long We Keep It
- Data on your device — until you delete it, or delete the App. We cannot reach it.
- iCloud backups — in your own iCloud until you remove them. Without Pro, only the three most recent are kept; with Pro, all of them.
- Your account record — until you delete your account. An earlier account left behind by the 2.0.8 update on iPhone or iPad stays until you ask us by email to delete it (see Your Account). PV AI memories — until you delete them, withdraw your PV AI consent (version 2.0.9 and later), delete your account, 12 months after they were last saved or confirmed, or, when your list is full, when a newer note takes their place, whichever comes first.
- Shares you have sent or received — until you or the other party deletes the share, or either account is deleted. There is no automatic expiry. Your PV ID, contacts and block list — until you delete the entry or delete your account. Registered devices — until you switch New shares off, sign out, or delete your account.
- Marketplace listings — until you remove them, they are taken down after reports, or you delete your account. There is no automatic expiry. A listing's name and composition reservations go with it.
- Your publishing quota, your download and like marks and the reports you filed — until you delete your account (a like mark also goes when you take the like back). Removing a listing does not remove other users' marks or reports about it.
- Marketplace take-down records — kept indefinitely as a moderation record: the listing as it was, the publisher's user ID and display name, and each reporter's user ID, reason and message. They survive the deletion of the publisher's account and of the reporters' accounts.
- Moderation logs — 90 days, or immediately when you delete your account.
- PV AI request records — set to expire 15 minutes after a chat request, or one hour after the last step of a question answered in several steps; the database removes them after they expire.
- Feedback you send — until we delete it. There is no automatic expiry.
- Emails you send us, and our record of a data protection request — for as long as we need them to deal with the matter and to show afterwards that we did.
- AI usage counters, the copy that survives deletion — about one usage window past your last AI request, roughly seven hours at the current setting. If an identity has been banned for abuse, the ban is kept.
- AI usage counters, the copy on your account record — held until you delete your account. It is a copy of the counters above and has no separate expiry. Up to version 2.0.8 the App shows it to you; we also use it to see how many subscribers use PV AI.
- Subscription event receipts — 30 days.
- Operational logs — 30 days. Google Cloud keeps each line for 30 days on our behalf and then deletes it.
- Deletion records — kept indefinitely. They hold a former user ID and a date, and exist so a late sign-in token or a late subscription event cannot recreate an account you deleted.
- Analytics — what was collected while analytics was on is held by Google under our Firebase project's retention setting.
Your Rights, Export and Deletion
Both controls are in the App, in Settings > Account > Manage your account. You do not need to email us for either. They act on the account you are signed in to. For an earlier account that the App can no longer open after the 2.0.8 update on iPhone or iPad (see Your Account), email hello@drydownlabs.com instead.
Get a copy of your data
Export my data builds a JSON file holding your user ID, email, display name, which provider you signed in with, when the account was created, your avatar colour, your AI usage counters, your subscription status, the memory switch, every note PV AI has saved, and your AI-consent record. The file is handed to your device's share sheet, so you choose where it goes. It is not uploaded to us.
Your shares and your marketplace listings are not in that file, because you can already see them: the sharing screen lists everything you have sent and received, the marketplace’s Mine tab lists everything you have published, and anything you imported or downloaded is in your own database. Ask us at hello@drydownlabs.com if you want them as a file.
What the file leaves out. If a request of yours was blocked by our safety checks, the log entry for it — including the excerpt of your own text — is not in the export. Nor are internal fields on your account record, such as the platform you last signed in from, when you were last seen, our safety counters and, if your account has been disabled, that fact and the reason. Your sharing records are not in it, as noted above, and neither are your marketplace records — your listings, what you have downloaded and liked, and any reports you filed — or feedback you have sent. Email hello@drydownlabs.com and we will send you a copy of any of these.
Delete your account
Delete account removes it. You will be asked to sign in again first if your last sign-in was more than ten minutes ago, because deletion cannot be undone. We then delete, in order: every PV AI memory, every moderation log entry belonging to you, every share you have sent or received, your PV ID, your send-spacing mark, your contacts, your block list, your registered devices, everything of yours on the formula marketplace — your listings with their name and composition reservations, the reports you filed, your publishing quota, your like marks (each like comes off that listing’s count) and your download marks (the download counts you added to other listings stay as they are) — then your account record, and finally your sign-in itself. The App then erases the chat transcript and consent record for that account from your device, and unlinks your device from the subscription record held by RevenueCat.
What we deliberately keep, and why
We deliberately keep four things when you delete your account. We are telling you plainly rather than leaving them out. A few other records are not kept on purpose but are not reached by deletion either — feedback you sent, your entry in other people’s lists, PV AI request records that have not yet expired, and operational logs — and they are listed under “What deletion does not touch” below. The four:
- The abuse-ledger entry. AI usage counts, and a ban flag if the account was banned. It is keyed to a one-way hash of your Apple or Google sign-in identifier, and contains no name, no email and no message text. Without it, anyone could reset their AI allowance — or shed a ban — simply by deleting the account and signing up again. An ordinary entry disappears about a usage window after your last AI request; only a banned one is kept.
- The deletion record. The former user ID and the date, so that a sign-in token or subscription event arriving late cannot bring the account back.
- Your subscriber record with RevenueCat, the service that manages subscriptions for us. Deleting your account unlinks your device from it, but the record keyed to your old account ID, including any cancellation reason and comment you submitted from the App, stays with RevenueCat. Email hello@drydownlabs.com if you want it erased and we will ask RevenueCat to delete it.
- Marketplace take-down records. When a listing is removed after three separate reports, we keep a copy of the listing as it was — the formula, the display name it was published under and the publisher’s user ID — together with the reports made against it, each with the reporter’s user ID, the reason chosen and any message. This is our moderation record. It is closed to every app and every user, it has no automatic expiry, and deleting your account does not remove it, whether you were the publisher or one of the people who reported the listing. Email hello@drydownlabs.com if you want us to review or erase one.
What deletion does not touch
- Your formulas and materials. They stay on your device — with the exception of anything still sitting in a share or listed on the marketplace, they were never on our servers, and we cannot delete them for you. Remove them in the App, or delete the App.
- What someone else imported from you. A formula another PV user imported from a share is in their database now. Deleting your account removes the share, not their copy, in the same way that deleting your sent mail does not empty anyone’s inbox. See Sharing with Another PV User.
- What someone else downloaded from the marketplace. A copy of a listing another user downloaded is in their database now, with your display name in its notes. Deleting your account removes the listing, not their copies. See The Formula Marketplace.
- Your entry in other people’s lists. If another PV user has you in their contacts, or has blocked you, their list holds your user ID, the display name you had at the time and, where they had it, your PV ID. Those lists belong to their accounts and only they can read them. Deleting your account does not remove you from them; your PV ID itself is deleted, so the entry no longer leads anywhere.
- Your iCloud backups. They are in your iCloud account; remove them in your device settings.
- Your subscription. It belongs to your App Store or Google Play account. Cancel it there, or it will keep renewing.
- Feedback you sent. Deleting your account does not remove feedback you sent earlier, and if you sent it while signed in without Send anonymously it still carries your user ID and email address. Email hello@drydownlabs.com and we will send you a copy or delete it. See Feedback You Send.
- PV AI request records that have not yet expired. They hold no message text and expire on their own, as set out under How Long We Keep It.
- Operational logs. A log line that recorded your user ID stays in our logging system until it ages out after 30 days. One more can be written after deletion: if a subscription notice arrives for the deleted account, the log notes the former user ID and that the notice was ignored. Log lines hold no prompt, no reply and nothing from your formulas.
Your rights in full
You can ask us: for a copy of your data (Export my data covers most of it; email us for the rest); to correct anything that is wrong; to delete your data (Delete account, or email us); to stop using your data while a question about it is settled; to give you your data in a form you can take to another service (the export file is JSON); and to withdraw a consent you have given, which you can also do yourself in the App by switching analytics off in Settings > Analytics or using Withdraw consent for PV AI in Settings > Account > Manage your account. You also have the right to object, set out next. These rights cost nothing to use. Write to hello@drydownlabs.com and we will answer within one month.
Your right to object
You have the right to object to Drydown Labs Ltd using your personal data. To object, write to hello@drydownlabs.com. We will stop, unless we have a compelling reason to carry on that outweighs your objection or we need the data for a legal claim, and we will tell you which. The right applies to the uses listed under our legitimate interests.
Complaints
If you are unhappy with how we have handled your personal data, you have the right to complain to us: write to hello@drydownlabs.com and we will look into it and tell you the outcome. If we decide not to act on a request you make, we will tell you why, within one month, and that you can complain to a supervisory authority or seek a judicial remedy. You also have the right to complain to the UK’s data protection regulator, the Information Commissioner’s Office (ico.org.uk). If you live in the European Union, you can complain instead to the data protection authority of the country where you live or work; elsewhere, to your local data protection authority where the law gives you that right. You can go to the regulator without complaining to us first.
Other requests
To ask a question we have not answered here, email hello@drydownlabs.com.
Children
Perfumers Vault 2 is a tool for perfumery work and is not directed to children. Our Terms of Use set a minimum age of 17. We do not knowingly create an account for a child, and we do not ask anyone’s age or collect anything designed to identify a child.
If you believe a child has created an account with us, email hello@drydownlabs.com and we will delete it and everything held under it.
Third-party links
The App and this site link to other people's websites — suppliers, IFRA, PubChem, Google's policy pages, the App Store or Google Play when you tap to leave a review or manage your subscription, and a parcel carrier when you track an order. Opening a tracking link hands the tracking number you typed to FedEx, UPS, DHL or USPS on their own site in your browser; for any other carrier the App opens a Google search for the number instead, so Google receives it. Tapping one of these links only opens the site in your browser. The exceptions are PubChem and the IFRA Standards download host, which the App itself fetches from, as described under PubChem Lookups and IFRA Library.
There are three places where the App does fetch from another website on your behalf. If you paste a web address into AI formula import, the App downloads that page or PDF directly from your device, so that website sees your IP address and knows the page was requested. What it downloads is then sent to PV AI in the usual way. The App also fetches from PubChem (see PubChem Lookups) and from the IFRA Standards download host (see IFRA Library).
We are not responsible for the privacy practices of any site we link to, or of any site you ask the App to fetch. Please read their policies before using them.
Contact
Drydown Labs Ltd (company no. 17558784, registered in England and Wales) is responsible for the data described on this page. For any question about it, or to make a request: