iBeauti

iBeauti Privacy Policy

Effective date: November 3, 2026

IBEAUTI TECHNOLOGY LLC (“we”, “us”, “our”) operates iBeauti, a beauty routine application available on the web at ibeauti.com and as a mobile app for iOS and Android (“the Service”). This policy describes what information we collect, how we use it, and the choices you have.

What we collect

Account information

When you create an account we store your email address and, if you provide one, a display name.

You can sign in with an email address and a password, or through Google, Facebook or Apple. If you set a password, it is held only by our authentication provider and only as a hash — we never see it, and nothing else in the Service stores it. If you sign in through a provider, that provider shares your email address (and, for Apple, your name if you allow it) so we can create your account. We do not receive or store your password from those providers.

When you agree to our Terms of Service, we record which version you agreed to, and when, with your account, and delete it with your account.

Your email address is never shown to other users. Our own staff can see it: see Who at iBeauti can see what below. Your display name and profile picture are shown on your profile, on routines you publish and beside comments you leave — including to people who are not signed in. Your bio is shown on your profile to anybody who can read it — anybody, signed in or not, if your profile is public, the followers you have accepted if it is private.

Profile information

You may optionally provide:

We also keep a shareable profile code, so you can hand somebody a link to your profile, and you can revoke it. A routine you publish can have a code of the same kind.

Routines and products

The core of iBeauti is beauty routines — ordered lists of products with notes and face-chart placements. We store the routines you create, the products you add to them, the tools you say each step is done with (the kind of tool, and the exact one where you pick it), the notes you write, and where on the face chart you place each step. A routine, and each of its steps, keeps two separate pieces of writing: a private note, which is yours, and a public note, written to be read by whoever you publish it to. We also store your folders, the order you arrange your routines in, and unfinished work you have kept as a draft. While you are signed in, we also store the one new routine you are in the middle of building, so it is there when you sign in again or open iBeauti on another device. It is sent to us at points as you build it — choosing a step’s product, adding, removing or reordering steps, changing its type — and when you leave the builder, and removed when you save it, keep it as a draft or discard it.

When you press Mark as done on one of your routines, or Done at the end of stepping through it, we keep a record of which routine, when, and whether it was the web app or the phone app, so your home screen can show what you did last. Only you can see these records — not the people who follow you and not a consultant whose makeover it was. Undo removes the record just made. They are kept for as long as the routine and your account exist, and are deleted with either.

The Getting started list on your home screen ticks itself from what is already stored — the routines, shelf and codes above and below. What it keeps of its own is that you dismissed it, and when, that you finished or skipped the guided first routine, and when, and that you first opened your account screen after signing up, and when, so each item stays ticked or away on every device. If an account is set back to the start of its first run, it also keeps when that happened, so the list counts only from then, and the other three are deleted. Only you can see those three; the last is part of your profile record, which an administrator can also read. All go with your account. Setting an account back to the start of its first run also deletes your answers to the first-run questions: your skin type, how sensitive it is, style preferences, how much makeup you do, your age range and what you would like help with.

You may also keep a product shelf — a personal inventory of products you own or want, organised into collections and into an order you arrange, with favourites, the date you opened something, when you would like to replace it, a private note and private star rating on a product, and tags of your own invention. Where a product comes in shades, the shelf, a collection, the note and the rating each record which shade it is about, when you say so. All of that is visible only to you, except a collection you choose to publish to your profile: its name and the products and shades in it can then be read by whoever can read your profile — anybody, including people who are not signed in, if your profile is public, and the followers you have accepted if it is private — until you unpublish it. A published collection has its own web address, which stays the same when you rename the collection, and each product in it has a page of its own at that address. You may add to a product in a published collection a note for readers and, if you are a creator, a link of your own to a retailer; both are shown to whoever can read the collection, and the link is followed to a site we do not run. Your private notes, ratings, tags, dates and the rest of your shelf are never shown with it.

A note you wrote about one shade follows that shade. If the shade is taken out of the catalog — our staff reject it, or it is removed — the note becomes your note about the product itself. If you already have a note about the product itself, the shade’s note is added to the end of it, and its pictures move to it, so none of your words are lost.

If our staff find that a product is one the catalog already holds and link or merge it into that product, what you keep of it moves to that product: your shelf entry, collections, notes with their pictures, tags, ratings, comments and routine steps, each in the same shade where that product has it. Where you already have that product on your shelf, the two entries become one. Where you already wrote a note on it, the note from your copy is added to the end of that note, with its pictures. If you added the product that was merged, or our staff take a product or shade you added out of the catalog, we tell you in What’s new. A product taken out stays with everyone who already has it, and nobody else finds it.

A product or shade you add can be found by anyone searching the catalog from the moment you save it, marked as added by a member until our staff check it, and anyone can put a shade you added on their own shelf. While we roll this out, some people find it only once our staff have checked it. Your name is not shown with it. A barcode you scanned finds the product for you alone until our staff check it, and for everyone after.

A description you write for a product you add is shown with the product, on its page, to anyone who can see the product — while it waits for review as well as once it is approved. The page does not show who added the product, though the catalog records which account did, and that record is not kept secret. If the product is rejected, the description is shown only to people who already have the product.

To put links of your own on a published collection you turn on the creator switch in your account, and we keep the date you turned it on. Your links are shown to whoever can read the collection, signed in or not, while the switch is on. Turning it off stops them being shown without deleting them.

Shade links. A product page can show, for each of its shades, similar shades in other products and shades often worn with it. Some of those links are worked out from how people use shades in their routines — private routines included — and from a record of one shade being swapped for another when somebody edits a routine: when you change a step from one shade to a shade of the same kind in a different product, we keep that your account made that swap, with no date, no routine and no step. Nobody can read that record, including our staff, and nobody can read which routines a link came from. A link worked out from use appears once at least five accounts support it and stays until fewer than three do, and it names and counts nobody. An account counts once it is fourteen days old and has saved a routine, and not while it is suspended or being deleted. A consultant’s suggestion is shown on its own, marked as a consultant’s (see Consultant handovers). You can keep your routines and swaps out of shade links at any time — see Your choices.

Corrections to the catalog. While a product you added is waiting for review, you can change what you wrote. Once a product is in the shared catalog, anyone with an account can propose a correction to it — its name, brand, kind, size, description or picture. We store the proposed change, the product as it stood, which account proposed it, and when. Until our staff decide it, nobody else is shown it, and you can withdraw it at any time. Our staff see it with your account’s email address beside it while they decide. If staff accept it, the change becomes part of the public catalog entry, with your name nowhere on it. A picture you attach is stored with product pictures, which are public. We do not send a notice of the decision. A proposal is kept, decided or withdrawn, for as long as your account exists, and is deleted with it.

Notes on a product. Instead of proposing a correction, you can send our staff a note saying what a product in the catalog is missing. We store its subject and description, the product, which account sent it, and when. Only our staff see it, with your account’s email address beside it, and nothing about the product changes because of it unless they change it themselves. A note is kept, open or resolved, for as long as your account exists, and is deleted with it.

You can also paste a list of such addresses, up to twenty, to add several products at once. The app reads each retailer’s pages one after another in one private window of the same kind for that retailer, up to three retailers at once, and one visit to the retailer for each page. Those windows share nothing with each other, and they keep nothing once the reading stops. The list you pasted, and what has been read from each page so far, is kept on your phone only — each address, and for a page already read the product’s details, its shades and the addresses of its pictures, together with anything you changed or typed for that product in the add-product form before saving it. It is not sent to us. A product leaves the list when it is saved or you remove it, and the whole list is removed when you clear it, when you sign out, when you delete your account from that phone, or thirty days after you last added links to it.

You can also open one of those retailers’ sites inside the app and move about it yourself, to find products and add them to that list. It opens in a private window of the same kind, which shows that retailer’s site and no other, and every page you open there is loaded on your phone and is not sent to us: the retailer receives what any visit to its site sends for each page, and its pages run as they would in a browser. While the window is open the app asks the page for two things and nothing else — its address, and whether a password box is showing on it — so that it knows when a product’s page is in front of you and when a sign-in has appeared. The only thing kept is the address of a product you press “Add this product” on, which joins the list on your phone described above and is read later exactly as a pasted address is; the app keeps no history of the pages you looked at. The app does not open the retailer’s sign-in, account, cart and checkout pages that it recognises by their address — it offers to open them in your phone’s own browser instead, which is then an ordinary visit there. If a password box appears on a page, the app covers the page with a card that says not to type your password there and offers three things: to close the retailer’s sign-in, to show the page anyway, and to open it in your phone’s own browser. “Close it” makes one press of that sign-in pop-up’s own close button for you; where the pop-up has no close button the app can recognise, it sends the Escape key to the pop-up and asks it to close, and does nothing else. It reads nothing from the page to do this, and removes or restyles nothing on it; the app does not read anything you type into a page, there or anywhere. It cannot recognise every such page: a cart or a sign-in step that the retailer draws over another page, without an address of its own and without a password box, is not covered. You should not type a retailer password or a card number into this window. When you close the window it keeps nothing, as above.

You can also send a product’s page to iBeauti from another app on your phone — your browser, or a retailer’s own app — by choosing iBeauti in that app’s share sheet. iBeauti receives only what you chose to share: the page’s address, or the text the other app sends with it. Your phone offers iBeauti for any web address or text you share, not only a product’s page, and whatever you send it that way is handled as this paragraph describes. Where what you shared is the address of one product’s page at one of those retailers, the app opens that page straight away, exactly as if you had pasted the address, without a further press. Anything else — several addresses, or text the app cannot read as one product’s page — is placed in the same box you would paste a list into, and nothing is opened or read until you press the button there; from then on it is handled exactly as a pasted list is. On iPhone, on its way from the share sheet to the app, what you shared is held on your phone, in storage only iBeauti can read, and removed from there as soon as the app has read it; if the app does not open, it stays there until the next thing you share to iBeauti replaces it. On Android it is handed straight to the app, which holds it in its memory only. It is not sent to us.

The details fill in a draft in the app’s add-product form, where you check and correct them before saving. When you add several from a list, each product is shown with what was read from its page, and those that need nothing more from you can be saved together as they were read. What you save is a product submitted to the catalog like any other you add. The page’s shades are submitted with it — all of them, less any you remove, and with any of their details you correct — one of them marked as yours, and each shade’s own link is kept as the product’s is. With the product we keep the link, cleaned — the address of the product’s page and the shade it names, with tracking tags and everything else removed — which retailer it is, when you saved it, and whether the details were changed before saving or rewritten by you afterwards. Which retailer it was read from is shown with the product to anyone who can see it. While the product waits for review, our moderators and administrators see the link, each shade’s link and that mark beside them, and nobody else does. If the product is approved — or our staff find the catalog already holds it and attach your link to that product — the link becomes that product’s public Find it at link for that retailer, where it has none there already, and each shade’s link becomes that shade’s public Find it at link in the same way, with your name nowhere on either. We also keep the addresses of the other pictures the page gave, so that you, or our staff reviewing it, can choose another of them as the product’s picture while it waits for review; only you and our moderators and administrators see them, and they are deleted as soon as the product has been reviewed, the chosen one staying as its picture. Unless you add a photograph of your own, the product’s picture is the retailer’s, and so is each shade’s, loaded from the retailer’s site — see Catalog picture hosts under Third-party services. The links are kept for as long as the product is; what happens to both when you delete your account is under Data retention.

Photographs

You may upload photographs for your avatar, for products, for how a look turned out, for a step of a routine, up to four on each step, for your private note on a product, up to six on each note, and one for each of your routine folders. The apps remove location data and other metadata from a photograph before it is uploaded — both apps re-encode a picture on your device before it leaves it.

Avatars and product images are public, with one exception: a photograph of a product or a shade you added can be held privately until our staff verify it. While it is held, only you and our moderators and admins can see it, and everybody else is shown the retailer’s picture or a placeholder instead; when the product or shade is verified, our staff publish a copy and it is public from then on. A product or shade you add is marked “In review” to everyone until then, without your name. A routine photograph, on the routine or on one of its steps, is private by default: only you can see it, even after you publish the routine it belongs to. You can mark an individual photograph to travel with the routine, and then anybody signed in who can read that published routine can see it — for a public profile that is any signed-in person, and for a private profile it is the followers you have accepted. Routine photographs are served through links that expire rather than from a public address. A copy of a routine — one you duplicate, or one somebody saves from yours — takes none of its photographs with it, and removing a step removes its photographs with it.

A routine photograph, and a routine folder’s picture, can be framed to one shape. When it is, so that you can change the framing later, we keep the whole photograph you took or chose beside the framed picture, re-encoded on your device the same way, along with where the frame sits on it. Only you can see the whole photograph — including when you have marked the framed picture to travel with a published routine, and whoever the reader is. Removing the photograph removes both, as does deleting its routine, its folder or your account. Avatars are framed too, but only the framed picture of an avatar is kept.

A photograph on your private note about a product is private and stays private: only you can see it, there is no setting that shares it, it is in nothing anybody else is shown, and no staff account can open it. It is held in private storage, apart from every other photograph, and served to you through links that expire. We keep it until you remove it or delete your account; removing it deletes the stored photograph as well as its place on the note. If the product a note is about is itself removed from the catalog, the note and its pictures go with it, and any stored copy left behind stays readable by you alone and is deleted with your account.

The picture of a routine folder, shown in the folder’s circle on its page and on your home screen, is private too: only you can see it, including on a folder you have put on your profile — your profile shows the folder’s name and routines and never its picture. It is held in private storage of its own and served to you through links that expire. Replacing or removing it deletes the stored picture and the whole photograph kept beside it, and deleting the folder deletes them too; if a deletion fails, the stored copy left behind stays readable by you alone and is deleted with your account.

For a folder’s picture or your avatar you may instead choose one of the app’s own pictures, which uploads nothing. Choosing, for a folder, the picture already on another of your folders or your avatar stores a private copy of it for that folder, which is kept and deleted like any folder’s picture above — removing the original does not remove the copy.

Your face chart photograph

You may add a photograph of your own face to your face chart, so the chart is drawn over your face rather than over the line art. It is optional: the chart works without one, and a screen explaining what happens is shown every time before the camera or the picker is opened — never once and then remembered.

What we store when you save one:

What we do not store: no face landmarks, no face mesh, no face template, and no measurement of your face of any kind. There is no column anywhere in our database that could hold one. The chart is fitted to your face on your own device: the measurements the fit reads exist in your device’s memory for the length of one fit and are then discarded, and the photograph is never sent anywhere to be analysed. The detector that does the fitting is a page and a model file we serve from ibeauti.com itself — running it sends no request to Google or to anyone else, and sends them no part of your picture. We do not use any of this to recognise or identify you, and we do not use it to identify you in any other photograph.

On the phone, a copy of the photograph stays on the phone as well. When you save one in the iBeauti app, or the first time your chart is drawn on a phone that did not take it, the app keeps a copy of it in its own private storage on the device, so your chart draws straight away instead of waiting for the picture to come back down. The app draws your chart only from that copy, never straight from the internet, so no other cache on the phone holds the photograph. It is not shared with any other app on the phone. It is deleted when you delete the photograph, when you replace it with another, when you delete your chart, when you sign out, and when your account is deleted — and the app removes any copy that is not the photograph your chart currently points at each time it draws your chart. The iBeauti website keeps no copy of it: it fetches the photograph each time. The consent screen in the app says this before the camera is opened.

Where it is kept: the photograph goes into a private store of its own, in a folder named after your account, and the crop windows, the region outlines and the switch go into three database tables keyed to your account. Nothing beyond our database and storage provider receives any of it — see Third-party services.

Who can read it: only you. The photograph and the chart appear in no published routine, no profile, no consultant handover, no routine cover, no search result, no message and no feed — everybody else, including the people who follow you and a consultant you have done a makeover with, sees the drawn chart. Our moderators and administrators have no way to reach it through the app either; unlike some other things you store, there is no staff view of it at all. As with everything else in the Service, the people who administer our database and storage could technically reach the underlying data — see Who at iBeauti can see what. Your own device reads it through a link that expires about an hour after it is issued, rather than from a public address.

How long we keep it: until you remove it. From your face chart in either app you can delete the photograph, which also puts every chart region back to the drawing, because the regions were fitted to that picture; a chart with no photograph can be deleted outright the same way. Deleting removes the stored picture first and checks it is gone before the record is cleared, and if the picture cannot be removed you are told so rather than left with a record pointing at something we failed to delete. Deleting your account removes the photograph and all three records with it, described under Data retention. Replacing the photograph removes the old one when the replacement is saved; a photograph uploaded for a capture you then abandoned is removed when you leave that screen, and again by the next save that changes the picture. A link already issued to your own device keeps working until it expires, up to an hour.

Messages

You can send direct messages to people who follow you back, and a consultant and the person they handed a routine to can message each other. You can send a single message request to somebody you follow, or to anybody whose account is public; a private account takes requests only from its followers. The person you wrote to accepts or declines it; declining deletes it, and an accepted request lets you both keep writing until either of you blocks the other. Messages are visible only to the two participants in a conversation, with two exceptions:

Ratings, comments and reports

You may rate products, a single shade of a product, and published routines from 1 to 5 stars. Ratings are shown only as totals and averages — they are never displayed beside your name. Comments you leave on products are public, carry your display name and profile picture, and the shade you had selected when you left one, and can be read by anybody, signed in or not.

If you report a comment, a routine, a profile, a message, a collection, a product or a shade, we store what you reported, the reason you chose and any note you wrote. Only you and our moderators and admins can see it. A report about a product or a shade stays when the account that added it is deleted, if the product or shade stays in the catalog.

Support requests

If you send us a bug report or a suggestion from the support page, we store what you wrote, the contact address you gave us so we can answer, which app you sent it from and which version of it, and the page or screen you were on when you pressed the question mark. If you were signed in we also store which account sent it; if you were not, we store no account at all. You are shown a ticket number, which is how you refer to the request if you write to us again.

The forms work whether or not you are signed in, deliberately: “I cannot sign in” is a report worth being able to send. Your request is readable by our moderators and administrators, and is also emailed to our support address — see Third-party services below.

Following, blocking and activity

We store who you follow, who follows you, pending follow requests, and the accounts you have blocked — your blocks are visible only to you. Anybody signed in who can read your profile sees how many people follow you and how many you follow, and which of the people they follow also follow you; if your profile is private, only your followers see these. The same line works the other way: when somebody who can read your profile opens the profile of a person you follow, they may see that you follow that person, so your followers can learn some of whom you follow. We also store when you last opened What’s new, so the app can mark what has happened since.

To stop anyone flooding other people or the catalog, we note the time of each message, comment, report, follow, product you add, support request and publication, and which of these it was. These notes are deleted after a day and with your account.

Consultant handovers

If a consultant builds a routine for you in a store, we store the code they hand over, when it was first opened, how many times it has been opened, and — once you claim it — that your account claimed it and when. We also count scans and claims against the routine itself. That count records nothing about the person scanning: no IP address, no device details, no account.

If you are a consultant, we store your consultant record — the name customers see and whether the record is switched on — and every store it belongs to: for each store, when you joined it, how you were admitted and which account admitted you, and which of your stores you are working in now. The other consultants at a store you belong to, and our administrators, can see your consultant name there, when you joined, whether you were added by us or joined with an invite, and whether you manage the store. Anybody signed in who can read your profile sees that you are a beauty consultant there, and nothing else from the record.

A store may have a manager: one of its consultants, marked as one by our administrators. A store does not need one. A manager of a store you belong to, and our administrators, can see the list of that store’s consultants described above and can remove you from that store. Being removed takes the store off your Work tab, stops your collections there being shared — they stay yours — and ends the makeover codes you made for that store; what you added to the store’s shelf stays there. You can leave a store yourself at any time from Manage stores in the store switcher on your Work tab, with the same effect; a store does not need to keep a manager, so a manager can leave too. A manager sees nothing more of your work than any other consultant at the store does: not your clients and not your private collections. When an administrator makes somebody a manager, takes that away, or removes somebody from a store, the change is written to the log of what staff have done.

A store you belong to has a shelf of the products used there. When you add a product to it, we store that your consultant record added it and when, and the other consultants at that store, and our administrators, can see your consultant name beside it for as long as you belong to that store. If you leave the store, or your consultant record is switched off, the product stays on the shelf, your name is no longer shown beside it, and any consultant at that store can take it off; we keep the record of who added it, and your name is shown again if you come back to the store. A work collection is yours alone unless you share it with the store it is in; while it is shared, the other consultants at that store can see it with your consultant name, limit a makeover code of their own to it, and make a copy of it that is theirs — a copy stays with them if you stop sharing or leave the store. A makeover code records which of your stores it was made for, or that it was made for none, and the person who opens it is shown that store’s name with yours.

A store can also be joined with an invite that one of our administrators, or a manager of that store, made for it. If you join a store with an invite, we store which invite you joined with and when, and that record is kept if you later leave the store. Our administrators and that store’s managers can see your consultant name on the list of people who joined with the invite, when you joined, and whether you still belong to the store, and on the store’s list of consultants they can see which invite each one joined with. If you had no consultant record, joining makes one under the name you give, or your profile name. If you make an invite, your consultant name is shown to anyone who opens its link, before they sign in, as a makeover code shows its consultant’s name, and to our administrators and the store’s managers on the list of invites. Deleting your account deletes the record of the invites you joined with; an invite you made stops working and stays on the store’s list without your name.

If you are a consultant and suggest a shade link, we store the two shades, whether it is a similar shade or a pairing, when you suggested it, and the note you wrote for our staff. The link is shown on the product page as “Recommended by a consultant”, without your name, while your consultant record is active, your account is not suspended or being deleted, and our staff have not taken it down. Your note is read only by you and by our moderators and administrators. If you take a suggestion back, we delete its note and keep the rest, marked as taken back, until you suggest it again or delete your account; it still counts toward the number of suggestions you can make in a day.

Device information

If you enable push notifications, we store a device token — an identifier issued by Apple’s or Google’s push service via Expo — and which of the two platforms the phone runs. We do not collect device identifiers for any other purpose. The token is deleted when you sign out, and when the push service tells us it no longer names a device. To learn that, we keep the push service’s receipt number for each notification with the token it went to, and check it later; these numbers name no account, and none is kept longer than a day.

Push notifications are sent for direct messages, including the first message of a message request. One carries the sender’s display name, the beginning of the message — or “sent a routine”, “sent a product”, “sent a person” where there was no text — and the identifier of the conversation to open.

Announcements from iBeauti are pushed only to those who turn Announcements on, which is off until you do. One carries the announcement’s title, the beginning of its text and the identifier of the announcement to open. We send it to the phones of the accounts the announcement is for, and keep a count of how many phones it was sent to, never who. Everything else the app tells you about, including new followers, appears inside the app and is not pushed.

Camera and photo library

The mobile app requests access to your camera (to scan codes, to photograph products or a picture for your private note, to take a routine, folder or profile picture in its own camera, framed on your phone before anything is sent, and the photograph for your face chart) and your photo library (to select an existing picture, or a saved photo of a barcode or a label to scan). Each is asked for when you first do the thing that needs it, and you can refuse — for a picture the library is offered instead; the face chart needs none. The web app may request camera access for barcode scanning, and can read a barcode from a photo you choose, in your browser, without sending the photo anywhere. For a face-chart photograph it has no camera of its own: “Take a photo” and “Choose from library” open your browser’s own file inputs, and the first of them asks the browser for the front camera, which on a phone is the camera itself and not a picker offering it — so a photograph may be taken through your browser, while the page never takes camera access in its own right. We do not access your camera or photo library in the background.

In the phone app you can also photograph a product’s label, or choose a saved photo of one or of a barcode, to find the product. The photograph is read on your phone to pick out the barcode or the words on it, shown behind what was found while you choose, and the app’s copy is deleted once you move on: it is neither kept nor sent to us or anyone else, and a photo you chose stays in your library untouched. The words are used as a search of our catalog and, where you choose a shop to search, are sent to that shop’s website.

Before either app opens a camera or a picker for your face chart, it shows you a screen saying what will happen to the picture — see Your face chart photograph above.

When you scan a product barcode, the barcode is sent to our barcode lookup provider (see Third-party services) and the result is cached, along with which account asked for it, so the same barcode is not looked up twice.

Usage

While you are signed in, we record a short list of actions so we can see whether the app is being used and whether it is working: opening the app, opening the builder, opening one of your routines, opening somebody else’s published routine, opening a product, running a search, scanning a barcode or an iBeauti code, opening your shelf, sharing a link, and marking a routine as done. That is the whole list.

Each record holds which of those actions it was, whether it happened in the web app or the phone app, and when. It does not hold what you searched for, which routine or product it was, your IP address, your device, your screen size, or how long you stayed. We use these only for counts — how many accounts were active, how many came back, how often each action happens. Our staff work these out with a read-only analytics tool run on our own computer, over views of our database that leave out your name, handle, picture and email address and stand a scrambled code in for your account; no third party is involved. They are never used to build a profile of you, and they are never shared.

Nothing is recorded while you are signed out, and repeated openings of the app or of your shelf are collapsed into at most one record every thirty minutes each. These records are kept for as long as your account exists and are deleted with it.

Separately, while you are signed in we record which product or routine you opened, and, where the app shows you a list of recommended products or routines, which ones it showed you and which one you tapped, with the list and its place in it. Each of these records holds the product or routine, which of those three it was, where in the app it happened, whether it was the web app or the phone app, and when. A record of a list shown or tapped also holds the list’s place on the page and the score that placed it. A record of a list shown or tapped, and the record of opening what you tapped, also hold a random code made anew each time you arrive at a screen, so we can tell what was shown, tapped and opened in one visit, and whether a product you tapped was then added to your shelf; the code is not your device’s and does not carry from one visit to the next. None of these records holds what you searched for, your IP address or your device. We use them to choose what to recommend and to understand which products and routines are used and whether recommendations help. No screen in the app shows them to our staff: staff read them only through the read-only analytics tool described above, and only as counts per day, which do not say whose they were. They are not sent to any third party, and no recommendation or analytics service outside the app receives them.

These records are kept for 90 days and then deleted automatically, and they are deleted sooner, with nothing kept, if you delete your account.

Recommendations

The app can show you lists of recommended products and routines, chosen by our staff or drafted from public beauty trends and checked by our staff. A list can be meant for everybody or for some people: by your skin type, how sensitive your skin is, your style preferences, how much makeup you do, your age range, your role, or the shop you kept a makeover from. Which lists you see is worked out from your own answers each time the app asks, inside our database: beyond the 90-day record of what you were shown (above), we keep no list of who is in which group, our staff do not see who a list reaches, and nothing about you is sent anywhere else to choose them. A product you already own, or a routine of your own, is left out; a product on your Wishlist can still be recommended. Lists are put in order by how well they fit your answers: a list meant for an answer you have not given is placed lower, and one meant for an answer different from yours lower still or not shown. A list meant for a role, a shop or a skin sensitivity is shown only to people who match it, and if you told us you are 13 to 17, a list meant for other age ranges is never shown to you. Signed out, you see only the lists meant for everybody. How these rows are chosen says the same in plain words, with what counts most.

You can mark a recommended product, routine or whole list Not for me. We keep what you hid, and when, until you undo it in your account or delete your account, and we use it only to leave those things out of your own recommendations. Nobody else sees it, our staff included, and nothing of it is kept, even as a total, once your account is deleted.

Information we do not collect

We do not collect your location, contacts, browsing history, or any information from other apps on your device. We do not collect biometric identifiers — no face template, face mesh, fingerprint or voiceprint, and no measurement of your face taken from the photograph described above. The phone app can log you in with Face ID, Touch ID or your phone’s fingerprint or face unlock if you turn that on (see Stored on your device); your phone’s operating system does the matching, and no biometric data reaches the app or our servers. We do not serve advertising. Neither app contains an analytics or tracking SDK other than crash reporting (see Third-party services). A retailer’s page that the phone app opens when you add a product from a link is the retailer’s own and runs the retailer’s code — see Adding a product from a retailer’s link above. The web app’s security headers explicitly refuse access to microphone, geolocation and payment APIs. The mobile app reads only whether it is connected to a network, to say when it is offline and turn off what needs a connection; that reading stays on your phone and is never sent to us.

Stored on your device

Some things stay on your device rather than being sent to us:

Signing out clears the stored session, removes that phone’s push token and deletes the cached lists, the picture cache and its kept links, the copy of your face chart photograph, the list of retailer links you were adding products from, and any reminder to replace a product the phone had scheduled. Signing out on a phone with no connection does all of that on the phone at once and stops the phone receiving notifications: the phone forgets its sign-in, and our record of that sign-in is left unused, since nothing on the phone can renew it any more. Our copy of its push token is deleted once the push service tells us it no longer names the phone, or when another account signs in on it. Losing the connection, or the app being unable to renew your sign-in while offline, is not signing out, and leaves those copies where they are. Deleting the app, or clearing the site’s data in your browser, removes the rest. Deleting your account clears both.

How we use your information

We use the information above to:

We do not sell your information. We do not share it with advertisers.

Who at iBeauti can see what

Access is by role, and it is narrower than the whole database.

Moderators can open the report queue — for each report, the reported comment, published routine name, profile name, message text, or product or shade name, who it belongs to or added it, and whether that account is suspended or its content hidden from others. They can also open the catalog review queue, which shows a submitted product, its description, shades, barcode and picture, the email address of whoever submitted it and whether that account’s content is hidden from others, what our barcode lookup provider returned for it — including which account scanned it — and, for a product added from a retailer’s link, the link and whether its details were changed before it was saved. The same queue holds the corrections people have proposed to catalog products and the notes they have sent about them, each with the email address of whoever sent it. They can open the support queue, which holds what somebody wrote on a bug or feature form and the contact address they left. Moderators and administrators both read the log of what staff have done, the shade links consultants suggested (the two shades, the consultant’s name and note) and those from use, which name no account, and can take a link down or hide a pair of shades from every product page.

Administrators can do everything a moderator can, and can also open the accounts list — every account’s handle, email address, display name, role, whether it is on early access, when it was created, how many routines it holds, and its consultant record with every store it belongs to — plus the stores, the feature flags, the announcements and the recommendation lists. An administrator can also read the rest of your profile record: your bio, your skin type, how sensitive it is, how much makeup you do, your age range, what you would like help with, whether your account is suspended or its content hidden from others, when it was last set back to the start of its first run, and which version of our terms you agreed to and when.

The analytics tool our staff run, described under Usage, reads counts, and records that stand a scrambled code in for your account, with no name, handle, picture or email address, no routine’s name or steps unless it is published, no message or comment text, and nothing of what is on your shelf.

Nobody on staff can read your routines, your shelf, your private notes, your drafts, your photographs, your face chart, your messages or your shade swaps, other than a single message that has been reported. Those are access rules inside the Service, enforced by the database itself. They are not a claim that the data is beyond human reach altogether: as with any hosted service, the people who administer our database and storage — and our storage provider — could technically read what is stored there, including your face chart photograph. We do not do so except where it is necessary to operate or repair the Service, or where the law requires it.

Third-party services

Supabase (supabase.com)
What we share: all data described above, plus the ordinary record of a web request (IP address, browser) that any host keeps.
Why: our database, authentication and file storage provider. Data is stored in the United States (AWS us-west-2).
Google
What we share: your email (during sign-in).
Why: authentication, if you choose Google sign-in.
Facebook / Meta
What we share: your email (during sign-in).
Why: authentication, if you choose Facebook sign-in.
Apple
What we share: your email and name (during sign-in).
Why: authentication, if you choose Apple sign-in.
Expo (expo.dev)
What we share: device push tokens, and the notification itself — the sender’s display name and the beginning of the message.
Why: delivering push notifications to your device. Expo hands each notification to Apple’s push service on an iPhone, or to Google’s Firebase Cloud Messaging on Android, which delivers it.
UPCItemDB (upcitemdb.com)
What we share: product barcodes (GTINs).
Why: looking up product information when you scan a barcode.
Catalog picture hosts (Open Beauty Facts, retailers and manufacturers’ own sites)
What they receive: your IP address and browser or device details, and which catalog picture was loaded.
Why: many catalog product pictures are loaded directly from whichever site supplied them rather than copied to ours, so your device fetches them from that site. We do not send them your account, your name, which page you were on or what you searched for.
Walmart, Target, Sephora, Ulta, Amazon and Olive Young
What they receive: only when you add a product from a link to one of them in the phone app, and only the one whose link it is — what any visit to its site sends: your IP address and device details, and whatever its own page collects while it is open. Olive Young’s global store is run by CJ Olive Young Corporation in South Korea, so a visit to it may be handled outside the United States.
Why: your phone opens the retailer’s product page itself, so the details can be read from it on your phone. These are sites your device contacts, not providers we send your data to: we send them nothing about you or your account, and they send us nothing. The pictures the app shows while you look over what was read are loaded by the app from the retailer’s picture servers, as under Catalog picture hosts above. See Adding a product from a retailer’s link above.
SMTP2GO (smtp2go.com)
What we share: a support request you send us — what you wrote, the contact address you gave, the ticket number, and which app, version and page it came from. For the mail our sign-in system sends you — the confirmation when you sign up, sign-in codes and password-recovery mail — your email address and the contents of the mail, which is a link or a code.
Why: delivering a support request to our support address as an email, so somebody reads it, and delivering account mail to you.
Sentry (sentry.io)
What we share: when something goes wrong — the app crashes, or an error our code did not expect happens in the app or on our servers — a report of it: what failed and where in our code, the app or site version, the kind of device or browser and its operating system, the address of the page or screen with any code, search, handle or id that would say whose it was cut out, and the last steps the app took before it (which screens it opened and which of our servers it called, never what you typed or what came back). On the phone, Sentry also counts app sessions and whether each ended in a crash, using a random number its code makes for that installation of the app; the number may appear on a crash report too, is not linked to your account, and is new if you reinstall the app.
A report is built without your account, name, handle or IP address, your routines, notes, messages or photographs, or anything you sent us, and before it is sent we take out any email address, sign-in or push token, or code that an error message happens to contain, so nothing in it says whose it was. Sentry receives it from your device or from our servers like any web request, and we have set it not to keep the address it came from. Reports are stored in the United States and deleted after at most 90 days.
Why: finding and fixing faults in the Service.
Vercel (vercel.com)
What we share: standard web request data (IP address, browser).
Why: hosting the web application.
Sites a creator links to (retailers and other shops)
What is shared: nothing from us. When you follow a retailer link that a creator has put on a product in one of their published collections, your browser goes to that site, which receives your address and browser details as any site does and applies its own privacy policy. Such a link is the creator’s own and may earn them a commission; the page says so beside it.
Why: a creator showing you where they buy something.

Data retention

We keep your data for as long as your account is active.

When you ask us to delete your account, the account is closed immediately: you are signed out everywhere and nothing can be written to it again. The erasure itself then runs in the background on a schedule, and normally finishes within a few days. What we remove:

Some things are deliberately left behind, in a form that is no longer yours:

A support request is kept for as long as it is open, and for twelve months after it is closed. If you delete your account, the account behind a request you sent is removed from it — what you wrote, the contact address you gave and the ticket stay for the rest of that period, because a support thread we are in the middle of is a conversation with two people in it.

When you delete your account we keep a few anonymous totals from it, with nothing in them that says whose they were:

Everything else is deleted.

Copies of the data may survive in restricted backups until those backups age out, after the retention period configured for the Service. Nothing is restored from a backup into active use.

Crash and error reports are deleted by Sentry after at most 90 days. Nothing in them says whose they were, so they are not linked to your account and are not part of its deletion.

A deletion receipt is kept for 30 days after completion so you can verify the deletion was carried out, then it too is removed.

Your choices

Delete your account

You can delete your account from the app at any time. On the web, go to Account → Delete account; on the phone, go to Account → Delete account. You can also do it at ibeauti.com/delete-account without installing the app. You confirm in a dialog, and if you have not signed in recently you are asked to sign in again first — with whatever sign-in method you normally use.

Facebook data deletion

If you signed in with Facebook, you may also request deletion through Facebook’s interface. We provide a data deletion callback that Facebook calls on your behalf, which triggers the same deletion process. Deleting your iBeauti account does not delete your Google, Facebook or Apple account.

Control your visibility

Your profile is private by default: only the people you have accepted as followers can read the routines you publish and the profile page you arrange. If you make your profile public, your display name, picture, handle and published routines can be read by anybody, including people who are not signed in. You can remove a follower, and you can block individual users.

Your face chart

Adding a photograph to your face chart is optional, and the screen explaining what happens to it is shown before every capture. Once there is one, the photo menu on your face chart in either app lets you read the chart as the line art instead, replace the photograph, or delete it. See Your face chart photograph above for what deleting removes.

On the account screen in either app you can turn off Use my routines to suggest shades to others. From the next rebuild of the links, normally within a day, none of your routines count towards any link — the ones you saved before as well as after — and the shade swaps we had recorded for your account are deleted at once. A link that other people’s routines still support stays. Turning it back on counts your routines again from the next rebuild; the deleted swaps do not come back.

Manage notifications

In the mobile app, Notifications under More has a switch for messages and one for announcements; each is stored with your account and decides only whether that kind is pushed, not what appears inside the app. You can also disable push notifications at any time through your device’s settings.

Children

iBeauti is for people 13 and older. It is not directed at children under the age of 13. We do not knowingly collect information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it.

Security

All data is transmitted over HTTPS. The apps remove location and other metadata from a photograph before uploading it. Access to the database is controlled by row-level security policies — each user can only read and modify their own data, with specific exceptions for public content (published routines, public profiles, product comments). Routine photographs, the photographs on your private notes and your face chart photograph are held in private storage and served through links that expire about an hour after they are issued; your face chart photograph and the photographs on your private notes are readable by your own account and by no other. Staff access is restricted to accounts with the appropriate role and is limited to what Who at iBeauti can see what describes above; every action staff take on somebody’s content is logged.

Changes to this policy

We may update this policy from time to time. We will post the updated policy at this page and update the effective date. For material changes, we will notify you through the app.

Contact

If you have questions about this policy or your data, contact us at support@ibeauti.com, or through the support page, which reaches the same address.