Privacy Policy
This policy covers the RUŌOD Lab Android application and this website at ruood.com/lab. It describes what the application stores, where it stores it, and every occasion on which anything leaves your device.
1. Summary
RUŌOD Lab is an offline-first application. Your materials, formulas, notes and settings are stored on your own device. There is no RUŌOD account, no RUŌOD server holding your library, and no background synchronisation.
The application contacts these services, and no others:
- Google — only once you connect Google Drive for backup, and only from then on;
- Google Play — through the Google Play app already on your device, to find out whether you have a RUŌOD Lab Premium subscription and what the plans cost. This happens when the app starts and when you return to it, and it never carries anything from your library;
- A public announcements file hosted on GitHub Pages, with any picture an announcement carries, which the app reads to show in-app notices;
- This website, ruood.com/lab — only when you open the RUŌOD Material Library or RUŌOD Formula Library, to download public catalog files and the materials, formulas and pictures you choose (in versions of the app that include them, not yet distributed). Nothing from your library is sent.
RUŌOD Lab has a Free plan and an optional subscription, RUŌOD Lab Premium. Which plan you are on changes what the application lets you do; it does not change what the application stores or sends.
There is no analytics, no crash reporting, no advertising and no tracking of any kind in the application. This website counts visits with Google Analytics, only where you allow it and never for advertising (section 13).
2. Who we are
RUŌOD Lab is developed and published by RUŌOD. For anything in this policy, write to info@ruood.com or developers@ruood.com.
3. Data stored on your device
Everything you create in RUŌOD Lab is written to the application's own private storage on your device, using your device's app storage and — for Google sign-in tokens only — the Android secure keystore. RUŌOD does not receive any of it.
| What | Where it is kept |
|---|---|
| Materials, material collections and their pictures | App storage; pictures as image files in the app's own directory |
| Formulas, formula entries and formula collections | App storage |
| Notes and note collections | App storage |
| Suppliers, fragrance families, Formula Hub calculations | App storage |
| Field, layout, display, search and status-bar settings, and appearance — your theme, glass transparency and splash-screen choice | App storage |
| Undo / redo history | App storage; deliberately never included in a backup |
| Announcement state — which notices you have read, and a cache marker | App storage |
| A copy of the public RUŌOD Material Library and RUŌOD Formula Library catalogs, so they can be browsed offline (versions of the app that include them — not yet distributed) | App storage; never included in a backup, and left in place by Factory Reset, because it is public data rather than yours |
| Pictures belonging to announcements | Files in the app's own directory, removed once the announcement is no longer published |
| Local backups (RUŌOD Lab Premium) — complete backup files you chose to make | Files in the app's own directory; not removed by Factory Reset |
| Drive backup metadata — the time of the last backup and your chosen schedule | App storage |
| Google sign-in tokens, and the email address and name of the connected account | The device's secure storage (Android keystore), never ordinary app storage |
All of this is removed when you uninstall the application. Without uninstalling, Factory Reset in Tools → Danger Zone removes your library and settings, and deliberately leaves backup files and your Google sign-in alone. See Retention and deletion.
Android's own device backup
Android can back apps up to your Google account by itself, or copy them to a new phone during setup, if you have turned that on in your device's settings. For RUŌOD Lab, Android's backup is limited to the application's small internal preference files. It does not include your materials, formulas, notes, pictures or backup files, and it always excludes your Google sign-in tokens. It is a feature of Android and your Google account, not of RUŌOD Lab, and RUŌOD receives none of it. To move your library to another device, use RUŌOD Lab's own backup (section 7).
4. What RUŌOD does not receive
We want to be precise rather than reassuring, so this section is about the application's behaviour rather than about a promise.
RUŌOD operates no server that receives your data. The only RUŌOD address the application contacts is this website, and only to download the public library catalogs you open (section 5); nothing from your library is part of those requests. There is no endpoint belonging to us for your data to be sent to. As a consequence, none of the following reaches us: your materials, your formulas, your notes, your settings, your backups, your device identifiers, your location, your contacts, your Google account details, or any record of how you use the app.
The application contains no analytics SDK, no crash-reporting SDK, no advertising SDK and no tracking library. It does not build a user profile, and there is no user identity in it to build one against.
Google Play's Data safety section
RUŌOD Lab's Data safety declaration on Google Play describes the same behaviour:
- Photos and other content you create — materials, formulas, notes — are declared as optional, for app functionality. They leave your device only when you choose to back up to Google Drive, and then only into your own Drive (section 7).
- No data is shared with third parties. A backup goes to your own Google account, at your request.
- Data is encrypted in transit. Every request the application makes uses HTTPS.
- There is no deletion request to make, because RUŌOD holds none of your data. You delete it on the device and in your Drive yourself, as section 16 describes.
The permissions update described in section 11 removes permissions the application never collected anything through, so it changes none of this.
5. Every request the app makes
These are all of them. No other network destination appears anywhere in the application.
| Destination | When | What is sent |
|---|---|---|
| Google's OAuth service | When you tap Connect on Google Drive backup, and when an expired access token is renewed | The standard OAuth exchange. No data from your library. |
| Google's user-info endpoint | Immediately after you connect | Your access token, to read back the email address and name of the account you chose, which are shown in the Backup section so you can see which account is connected. |
| Google Drive API | When a backup is written, listed, restored or deleted — including an automatic backup, if you chose a schedule | Your access token and, for an upload, the backup file itself. |
| A public announcements file on GitHub Pages, and any picture an announcement carries | Once per app launch; on returning to the app, at most once every six hours; and when you tap Check new announcements in Settings | An ordinary HTTP request for a public file. No account, no identifier and no data from your library is included — see section 9. |
| Google Play Billing | When the app starts and each time you return to it, and when you buy, restore or manage a subscription | A request to the Google Play app already on your device for this app's purchase records and plan prices. Nothing from your library — see section 8. |
The RUŌOD Material Library and RUŌOD Formula Library catalogs, public files on ruood.com/lab (versions of the app that include them — not yet distributed) |
Only when you open one of the two libraries (from an empty Materials or Formulas page, its ⋯ menu, or Tools → RUŌOD Library), when you import from it, and when you switch an imported material's picture between Aroma and Chemical on its profile and that picture is not yet on the device | Ordinary HTTP requests for public files — the catalog, and the materials or formulas you chose with the pictures you chose. No account, no identifier and no data from your library is included; which materials or formulas you browse or import is not recorded by the app or sent anywhere. |
Until you connect Google Drive, the only requests the application makes are the announcements file and the Google Play subscription check — and the RUŌOD Material Library and Formula Library catalogs, if you open them. Nothing about your library is ever part of any request except a backup — one you started, or one on a schedule you chose.
6. Google Account sign-in
Signing in with Google is optional and exists for one purpose: backing your library up to your own Google Drive. The application works fully without it, and it does nothing until you tap Connect in Settings → Backup.
What is requested
Sign-in uses Google's standard OAuth 2.0 flow with PKCE, requesting these scopes:
| Scope | What it allows |
|---|---|
openid, profile, email |
Identifying the account you chose. The application reads back the email address and display name of that account and shows them in the Backup section, so you can confirm which account your backups are going to. |
drive.file |
Access to only the files and folders this application creates in your Drive. This is Google's most restricted Drive scope. It does not grant access to your existing Drive contents: the application cannot see, read or list any file it did not create itself. |
Tokens
The access token, the refresh token, the token expiry, and the connected
account's email address and name are stored in your device's
secure storage (the Android keystore), never in ordinary
app storage. They stay on your device. They are not included in a backup and
are not sent anywhere except to Google, as the Authorization
header of a request to Google.
A refresh token is requested so the connection survives beyond the roughly one-hour life of an access token — without it, a scheduled backup could not run on a device left alone overnight.
Disconnecting
Disconnect in Settings → Backup deletes every stored token and the stored account details from your device. You can also revoke the application's access entirely from your Google Account, at myaccount.google.com/permissions. Backup files already in your Drive belong to you and are not removed by either action — delete them from Drive, or from within the app before disconnecting.
7. Google Drive backup
Backup — to your device's own storage or to Google Drive — is part of RUŌOD Lab Premium. Local Backup writes the backup file into the application's own storage on your device, and it goes nowhere else. The rest of this section is about Google Drive.
When it happens
A backup is written when you start one, or on a schedule you choose — Every Day, Every Week or Every Month. The default is Manual: connecting an account uploads nothing on its own, and no scheduled backup runs until you pick a schedule. Because the application runs no background service, a scheduled backup is checked for and performed when you open the app, return to it, or come back online and one is due. Nothing is uploaded while the application is closed, and nothing is uploaded at all unless you have connected an account. Each backup is a new file; the application never replaces or deletes an existing one on its own.
What a backup contains
A complete snapshot of your application data as it currently stands: materials and their pictures, material collections, formulas and formula entries, formula collections, notes and note collections, suppliers, fragrance families, Formula Hub calculations, and your settings. Records are carried whole.
Two things are deliberately excluded: your Google sign-in tokens and any other secure-storage item, and your undo/redo history.
Where it goes
Into your own Google Drive, in a folder the application
creates called RUOOD Lab / Backups, under the Google account you
connected. RUŌOD does not hold a copy, does not receive a notification, and
has no access to your Drive. Once the file is in your Drive it is governed by
your agreement with Google and by
Google's Privacy Policy;
you control it there as you control any other file you own.
Restoring
Restoring a backup replaces your current application data rather than merging with it. The application asks for confirmation and states what is about to be replaced before it does anything.
RUŌOD Lab does not synchronise. It writes a backup file when asked. It does not continuously mirror your library, and it does not keep your data on any RUŌOD infrastructure — there is none.
8. Google Play Billing and subscriptions
RUŌOD Lab offers a subscription, RUŌOD Lab Premium, sold exclusively through Google Play Billing. There is no other payment path in the application — no card form, no web checkout, and no third-party payment processor.
RUŌOD Lab works on a Free plan; RUŌOD Lab Premium lifts its limits and adds features such as backup, all eight reports and whole-library export — the home page lists them. The plan you are on changes what you can do in the application, not what it collects: neither plan sends anything from your library anywhere.
When Google Play is asked
So that it knows which plan applies, the application asks Google Play for this app's purchase records when it starts and each time you return to it, and again when you buy, restore or manage a subscription. It asks for the plans' current prices at the same time, so the Premium screen can show what Google Play will charge in your country. The request goes to the Google Play app on your device, which can answer from its own records without a network connection. Nothing from your library is part of it.
What the application sees
Purchases are handled entirely by the Google Play app already on your device. RUŌOD Lab receives from Play only the purchase records for this application — the product, its state, and the token Play uses to identify the purchase — and the localized price Play displays. From those records the application works out, on the device, whether a subscription is currently active.
The application never receives your payment card number, your bank details, your billing address or your Google Play account credentials. Those are Google's to handle, under Google's Privacy Policy.
Your subscription status is not stored anywhere by the application — not in app storage, not in secure storage, and not in a backup. It is derived from Play's records each time it is needed, and it is not sent to RUŌOD, because there is nowhere to send it.
Managing or cancelling a subscription is done in Google Play's own subscription settings. When a subscription ends, nothing in the application is deleted: records over the Free plan's limits stay, and backup files stay where they are.
9. In-app announcements
RUŌOD Lab can show notices — a new release, something you should know about.
To find out whether there are any, it reads a single public file
published at
adil-asad.github.io/ruood-announcements, hosted on GitHub Pages.
This and the Google Play subscription check are the only requests the application makes that you did not start, so:
- It is made once per app launch; when you return to the app, at most once every six hours; and when you tap Check new announcements in Settings.
- An announcement may carry a picture. It is downloaded from the same address, checked against a fingerprint in the signed file, and kept in the application's own storage on your device until the announcement is no longer published.
- It is a plain request for a public file. It carries no account, no device identifier, and nothing from your library — no materials, no formulas, no notes, no settings.
- The request is conditional, so a file that has not changed returns nothing at all.
- Which notices you have read is recorded on your device and is never reported back.
As with any request to any web server, GitHub receives the technical information a web request necessarily contains, including your device's IP address, and handles it under GitHub's privacy statement. We do not receive that information, and the file is served identically to everyone who asks for it — there is no per-user targeting and no response that could identify you.
10. Files you import and export
Exports are generated on your device and written where you choose — the folder you pick in Android's folder chooser, or the destination you select from the share sheet. Imports are read from the file you pick in Android's file picker. Android gives the application access to that file or folder only (section 11). Neither passes through RUŌOD. An export is prepared in the application's private cache on your device, which Android clears as it needs space; the application keeps no other copy.
Once an exported file leaves the application — sent, shared, or saved to a cloud folder — it is outside the application's control and subject to whatever service you sent it to.
11. Device permissions
RUŌOD Lab needs three Android permissions:
| Permission | Why |
|---|---|
| Internet | Google sign-in, Google Drive backup and restore, Google Play Billing, the announcements file and, in versions that include them, the RUŌOD Material Library and Formula Library. Everything else works offline. |
| Network state | Checking whether the device is online before a Google Drive backup or restore, and noticing when the connection returns, so that a scheduled backup that is due can run. The application reads only whether a connection is available; nothing about the network is stored or sent. |
| Google Play Billing | Required by Google Play in order to offer the RUŌOD Lab Premium subscription and check which plan you are on. |
Pictures: Android's photo picker
To attach a picture to a material, you choose an existing image in Android's own photo picker (on a device without one, Android's file picker). The picker is part of Android, not of RUŌOD Lab, and the application receives only the image you select. It cannot see, browse or index the rest of your photos. It keeps a resized copy of that image in its own private storage. Choosing a picture this way needs no camera permission: RUŌOD Lab does not take photos and has no feature that uses the camera or the microphone.
Files: Android's file picker and folder chooser
Import reads the file you pick in Android's file picker. Export writes to the folder you choose in Android's folder chooser, or hands the file to the app you pick from the share sheet. In each case Android gives the application access to that file or that folder only, and no broad shared-storage permission is involved. Local backups and material pictures are kept in the application's private storage, which needs no permission at all.
What the application does not use
RUŌOD Lab has no feature that uses the camera, the microphone, your location, your contacts, or fingerprint, face or any other biometric authentication. Google sign-in tokens are kept in Android's secure storage without a biometric prompt. The application plays no vibration or haptic feedback, apart from the build 12 behaviour described below.
Google Play's own listing can also show a license-check permission. Google Play adds it when it delivers the app, as part of its own app-integrity protection. RUŌOD Lab's code does not use it.
Build 12 and the next update
The build of RUŌOD Lab 1.0.0 currently with Google Play (version code 12) and the builds before it declare more permissions than the application needs. Some come from the libraries the application is built with. An update that has not yet been distributed removes all of them. Once it is installed, the three permissions above are the only ones the application declares. Until then, this is what build 12 declares beyond those three, and what each one does:
| Declared by build 12 | What it does in build 12 | After the update |
|---|---|---|
| Camera | Nothing. It is never requested, and no feature takes a photo. | Removed |
| Storage (read and write) | On Android 12 and earlier, requested the first time you choose a picture for a material, before the photo picker opens; the picker still passes the application only the image you select. Android 13 and later do not ask. Not used for import or export. | Removed; the photo picker needs no permission |
| Vibration | Brief haptic feedback when you change tab, change the theme, or press and hold to start selecting items. | Removed, together with the haptic feedback |
| Fingerprint and biometrics | Nothing. Declared by the secure-storage library and never used; the application never shows a fingerprint or face prompt. | Removed |
| Wi-Fi state | Nothing. Declared by the network library and never read. | Removed |
| Install referrer | Nothing. Declared by a library and never queried; the application does not record how it was installed. | Removed |
None of these permissions has ever been used to collect anything. The update changes what the application declares, not what it stores or sends.
12. This website
This site — every page under ruood.com/lab — is
static HTML, CSS and a small amount of JavaScript. It was
built to collect as little as possible:
- Visitor statistics, and nothing else. Google Analytics counts visits — only where you allow it — so that we know how many people read the site, from which countries and which pages. It is the one thing the site loads from another company, and it sets the only cookies; see section 13.
- No advertising, no tracking pixels and no session recording.
- No other third-party requests. There are no external fonts, no CDN-hosted scripts, no embedded videos, no maps and no social widgets. Every other file the page loads comes from this domain.
- No forms and no accounts. The contact page offers email addresses as links; there is nothing here that submits data anywhere.
- The JavaScript runs the mobile navigation menu, the dark / light theme switch, a little motion on the home page, the search box and topic filters on the blog, and the search, filters, ordering and Aroma / Chemical image switch of the materials encyclopedia, and the Listen to article player on blog articles. Both searches filter the list already on the page, inside your browser: what you type is not sent anywhere.
- Listen to article. On a blog article, Play reads the article aloud with your browser's own speech feature; nothing is read until you press it, and this site sends nothing anywhere to do it. Some of your browser's voices are online: with one of them, your browser itself sends the words being read to its own speech service (Google's or Microsoft's, for example), under that company's terms. Where your browser offers it, the voice the player starts with is Google UK English Male, which is one of these — the line under the player then says Online voice. Voices marked Offline speak on your device, and you can choose one from the voice control at any time. The article is public text, and nothing about you is part of it.
- A few preferences, kept in your browser. If you switch the site to its light theme, or use the encyclopedia's Aroma / Chemical switch, the site remembers that choice as a single word in your browser's local storage, so the next page opens the same way; if you change the speed or the voice of Listen to article, those two choices are kept the same way, together. If you use the Academy's progress controls (marking a lesson complete, bookmarking it, or checking a quiz), the site keeps which lessons and your quiz scores the same way, so that you can pick up where you left off; reading a lesson stores nothing, and the Academy's Clear my progress button removes it. Nothing is stored until you use a control (switching back to the dark theme removes the word again), it is never sent anywhere, it identifies no one, and clearing this site's data in your browser removes it. Your choice about visitor statistics is kept the same way (section 13).
These pages, and the public library catalogs the application downloads, are hosted by Netlify, which also hosts ruood.com. As with any website, Netlify processes the technical information every web request contains, such as your IP address and browser user-agent, in the course of delivering the page and keeping the server secure. RUŌOD does not use that information to identify or follow anyone.
The only links that leave this site are the ones you can see: the email links, the link to ruood.com, the links to Google's and GitHub's own policies in this document, and, in the blog articles and the materials encyclopedia, links to the published sources they cite — such as IFRA, PubChem, the US Food and Drug Administration, the European Commission and GOV.UK. Nothing is loaded from those sites; following a link takes you there, under that site's own privacy policy.
13. Cookies, tracking and visitor statistics
The application contains no advertising identifier, no analytics and no tracking SDK. This website uses one service to count visits: Google Analytics 4, a service of Google, so that we know how many people visit, from which countries and regions, and which pages they read. The RUŌOD perfume shop at ruood.com is counted separately, as its own Google Analytics property.
- When it is used. If your device is set to a time zone in Europe (the European Economic Area, the United Kingdom or Switzerland), nothing is loaded from Google until you choose Allow in the box that appears at the bottom of the page. Elsewhere, it is used unless you switch it off below. It is never used if your browser sends the Global Privacy Control signal, or once you have switched it off. Your choice is one word in your browser's local storage, never sent to us, and it also applies to ruood.com, which is the same address.
- What Google receives. Each page you open (its address,
without anything after a
?), the page that sent you here, the time, your browser's language, screen size and type of device, and, from your connection's IP address, an approximate place — country, region and city. Google Analytics 4 does not keep the IP address. Nothing from the application, and nothing you type, is sent. - Cookies. Two, set only when your visit is counted:
_gaand one beginning_ga_, holding a random number that lets Google tell one browser's visits from another's. They expire after thirteen months, and switching statistics off below deletes them. - Not for advertising. Google Signals, ad personalisation and every advertising feature are switched off, and the browser's own advertising features are switched off on this site. We see only totals, never a visitor. Google processes the data on our behalf under Google's Privacy Policy (see also how Google uses information from sites that use its services). The record of each visit is kept for two months, the shortest Google Analytics offers; the totals made from them for as long as we use it.
Besides that, the website keeps in your browser only the theme, image-view and listening preferences and any Academy progress described in section 12, which you set yourself and which track nothing.
14. Third-party services
The complete list. Google is reached only if you choose to connect Google Drive, and Netlify only if you open a RUŌOD library; Google Play and GitHub Pages are reached automatically. None of them is sent anything from your library except Google Drive, which receives the backups you make.
| Service | Used for | Optional? |
|---|---|---|
| Google (Sign-In and Drive) | Backing up to, and restoring from, your own Google Drive | Yes — only if you connect an account |
| Google Play (Billing) | Offering the subscription, and checking which plan you are on | No — checked when the app starts, through the Google Play app on your device; it carries nothing from your library |
| GitHub Pages | Hosting the public announcements file the app reads, and its pictures | No — but it carries nothing about you or your library |
| Google Analytics | Counting visits to this website (not the application) — see section 13 | Yes — in Europe only once you allow it; elsewhere until you switch it off; never with Global Privacy Control |
| Netlify | Hosting this website and the public RUŌOD Material Library and Formula Library catalogs | Yes, for the application — only when you open a library (versions not yet distributed); it carries nothing from your library |
There is no other third party, and the website uses no service but Netlify and Google Analytics. In particular the application uses no analytics provider, no crash-reporting provider, no advertising network, no payment processor other than Google Play, and no RUŌOD backend that receives your data.
15. Security
Your library is kept in the application's own private storage, which Android isolates from other applications on the device. Google sign-in tokens are held in the Android keystore rather than in ordinary app storage. All network requests the application makes use HTTPS.
Two things it is only fair to be plain about. The application does not separately encrypt your library with a password of its own: it relies on your device's own protection, so a device lock and Android's own device encryption are what protect it, and anyone with access to an unlocked device has access to the app. And a backup file placed in your Google Drive is protected by your Google account and by Google's own security, not by anything RUŌOD does to the file.
No method of electronic storage or transmission is completely secure, and we cannot guarantee absolute security.
16. Retention and deletion
RUŌOD holds nothing, so there is nothing for us to retain or delete. Your data is kept on your device for exactly as long as you keep it there.
- Individual records — delete them in the app.
- Everything in the app — Tools → Danger Zone → Factory Reset returns the application to an empty state: every material, formula, note, collection, supplier, family and calculation is removed, stored pictures are deleted, the undo history is cleared and every setting returns to its default. Google sign-in and backup files are deliberately left alone by a reset, so disconnect and delete those separately if that is what you want.
- Everything, including tokens — uninstalling the application removes its storage, including the secure-storage items and any local backup files.
- Local backups — delete them in Settings → Backup → Local Backup, which is part of RUŌOD Lab Premium; on any plan, uninstalling the application removes them.
- Drive backups — delete them from within the app's backup list (with Premium), or from Google Drive directly on any plan. They are your files and remain in your Drive until you remove them.
- Google's access — Disconnect in the app, and/or revoke at myaccount.google.com/permissions.
- Subscription — cancel in Google Play. Play retains purchase records under its own policy; we have no copy.
17. Your controls
Because your data stays on your device, you exercise control over it directly rather than by asking us:
- Access — everything is visible in the application.
- Portability — export your records as PDF, CSV, Excel or JSON at any time: one at a time on the Free plan, or a selection or the whole library with RUŌOD Lab Premium, which can also write a complete backup file.
- Correction — edit any record in the application.
- Erasure — as described in section 16.
- Withdrawing consent — disconnect Google Drive at any time; the application continues to work. On this website, switch visitor statistics off in section 13.
If you believe RUŌOD holds personal information about you — for example because you have emailed us — you can ask us about it at info@ruood.com, and we will respond. We use the address you write from only to reply to you.
18. Children
RUŌOD Lab is a professional formulation tool intended for adults and is not directed at children. It has no account system, no social features and no user-generated content that is shared with anyone, and it does not knowingly collect information from anyone — including children — because it collects no personal information at all.
Perfumery involves materials that require adult handling and judgement. If you believe a child has used the application in a way you are concerned about, contact us at info@ruood.com.
19. International use
RUŌOD Lab keeps your data on your own device, wherever in the world that is, and there is no transfer of it to RUŌOD in any country. If you choose to use Google Drive backup, your backup file is stored on Google's infrastructure, which may be located in countries other than your own; that processing is governed by your agreement with Google and by Google's Privacy Policy. This website is hosted by Netlify, its visits are counted by Google Analytics (section 13), and the announcements file is hosted by GitHub — companies based in the United States — so the technical information of a request to any of them may be processed outside your country.
20. Changes to this policy
If the application's behaviour changes — a new feature that contacts a service, or a new kind of data it handles — this policy will be updated before or alongside that release, and the date at the top of the page will change with it. Material changes will be described in the application's own announcements.
21. Contact
Questions about this policy, about what the application does, or about your data:
- General — info@ruood.com
- Technical — developers@ruood.com
See also the contact page.