Last Updated: October 20, 2026

Privacy Policy

This Privacy Policy explains how iBeauty handles information when you use the iBeauty mobile app and website.

1. Who operates iBeauty

iBeauty is operated by SMART CODE STUDIO S.R.L.. For privacy questions, account deletion requests, or data requests, contact:

hello@danielzaharia.dev

2. Information you provide

When you use iBeauty, you may provide:

Account information, such as your email address and profile details.
Finance records you choose to enter, such as income, client counts, expenses, recurring expenses, wallets, notes, payment status, and payment method labels.
App preferences, such as currency, theme, notification settings, and reminder settings.
Support messages or other information you send directly to us.

You are responsible for the information you enter into the app.

3. Information collected automatically

iBeauty may collect technical and usage information needed to operate, improve, and protect the app, including:

Device and app information, such as platform, app version, language, and diagnostic details.
Analytics events that help us understand feature usage and product quality.
On the iBeauty website only, measurement of which pages were viewed and whether a visitor went on to sign up or to an app store, so we can tell whether our advertising is working. This does not apply inside the mobile app.
Crash reports, error logs, and performance diagnostics.
Push notification identifiers and delivery status when notifications are enabled.
Purchase entitlement status, such as whether your subscription is active.

The iBeauty website asks before it sets any advertising cookie. Until you accept, the Meta pixel is not loaded and nothing is sent to Meta. If you decline, the site works exactly as it does otherwise. You can change your mind at any time using the Cookie settings link in the website footer, which brings the choice back. This applies to the website only — the mobile app has no advertising cookies and no Meta pixel.

If you accepted advertising cookies on the website and then create an iBeauty account or start a subscription in the web app, our server tells Meta that this happened, so we can tell which ads bring people who actually sign up. It sends the kind of event (signed up, started the free month, subscribed), the plan and its price, your email address and account id in hashed form (a one-way code Meta uses to match the event to the ad you saw, which cannot be turned back into the address), your IP address and browser, and the Meta cookies the website set. It never sends anything you record in iBeauty. If you declined advertising cookies or never made a choice, nothing is sent; your choice is kept in a small first-party cookie so the server can respect it, and withdrawing consent removes it.

When you create an account from a link that carries campaign tags — the utm_ labels on links in our ads and posts — we keep those tags with your account (which campaign and which ad), so we can count sign-ups per ad. They name the campaign, not you, and are never sent to Meta. If you accepted advertising cookies and open the sign-up or sign-in page from such a link, the tags also wait in a first-party cookie for up to an hour, so a sign-up with Google or Apple can keep them; it is deleted once you sign up, withdraw consent, or it expires. Without that consent, no cookie is set for them; once your account exists, they are part of its details, which travel with the sign-in session your browser keeps for any account.

Separately, the website counts page views and app store clicks with OpenPanel, an analytics tool we host on our own server. It sets no cookies and stores nothing on your device. Visits are told apart by a one-way hash of your IP address and browser that changes every day, so it cannot recognise you from one day to the next, and no third party receives the data. Because nothing is stored on your device, it runs whether or not you accept cookies.

The web app works differently once you sign in, in the same way as the mobile app: it records usage events, such as which screens you open and when you add a record, linked to your account, so we can see how iBeauty is used across your phone and your computer. These events never contain what you entered — no client names, notes, phone numbers or amounts. They go to the same OpenPanel server, and only the signed-in web app sends them; the public website stays anonymous as described above.

4. How we use information

We use information to:

Provide account access and store your finance records.
Sync and display your income, expenses, wallets, summaries, and reminders.
Manage subscriptions and app access.
Send push notifications and recurring expense reminders if you enable them.
Send account emails you would expect from a service you signed up for: confirming your address, resetting your password, and helping you get set up. We do not send promotional email without your consent, and you can reply to any of these to ask us to stop.
Improve app reliability, product quality, and user experience.
Respond to support requests.
Meet legal, security, and operational obligations.

5. Third-party services

iBeauty uses trusted third-party services to operate the app:

Supabase for authentication, database storage, and backend services.
Brevo for sending account emails, such as sign-up confirmation, password reset, and messages about setting up your account. Brevo receives your email address and your first name where you have provided one.
RevenueCat for subscriptions, purchase status, and entitlement management.
OneSignal for push notifications and marketing messages where enabled.
PostHog for product analytics in the mobile app. The website does not use PostHog.
OpenPanel for website and app analytics. We run it on our own servers, so the data it collects is not shared with the company that makes it.
Meta (Facebook and Instagram) for advertising measurement on the iBeauty website. The Meta pixel runs on the website only, never inside the mobile app or the signed-in web app, and reports page views and button clicks so we can measure our ads. With your consent, our server also reports sign-ups and new subscriptions from the web app, as described under "Cookies on the website".
Sentry for crash reporting, error monitoring, and diagnostics.
Apple and Google for store payments, subscription management, and sign-in services where applicable.
Stripe for subscriptions bought on the iBeauty website, as the reseller that processes the payment and collects any tax. Stripe receives your email address, your payment details and your billing country.

These services process information according to their own privacy policies and data processing terms.

6. Payments

iBeauty does not receive or store your full payment card details. App Store and Google Play purchases are processed by Apple or Google, and website purchases by Stripe. RevenueCat helps iBeauty understand whether your subscription is active.

7. Data storage and security

We use reasonable technical and organizational measures to protect your information. No system can be guaranteed to be completely secure, but iBeauty is designed so your account data and finance records are stored through backend services with access controls.

We do not sell your personal data. We share information only when needed to operate iBeauty, provide third-party services listed above, comply with law, protect rights and safety, or respond to your requests.

9. Data deletion and privacy requests

You can request deletion of your account or personal data by contacting:

hello@danielzaharia.dev

Some information may need to be retained for legal, security, billing, or operational reasons.

10. Children

iBeauty is not intended for children under 13. If you believe a child has provided personal information, contact us so we can review and delete it where appropriate.

11. Changes to this policy

We may update this Privacy Policy as iBeauty changes. The latest version will be available on this page.