Privacy Policy

What Ilumible collects, why, who else sees it, and how to ask for it back or ask for it gone.

In effect since
6 September 2026
Last updated
12 September 2026

1. Who is responsible

Ilumible is operated by Wendel Freitas, an individual — a natural person, not a company. There is no CNPJ and no registered legal entity behind it. Requests about your data reach a person, and that person answers them by hand.

2. Two different relationships, and they are not the same

This policy covers two kinds of people, and Ilumible’s obligations differ for each. Read the one that is you.

  • If you subscribe — you signed up, you run a calendar here, you accepted these terms. For your own data, Ilumible is the controller: it decides what to collect and why.
  • If you booked with a professional who uses Ilumible — you never signed up for anything and never accepted these terms. For your data, the professional is the controller and Ilumible is the processor. Ilumible holds and moves your data on their instruction; it does not decide what to do with it, does not sell it and does not use it to advertise to you.
  • A practical consequence: if you booked an appointment and want your data corrected or deleted, the professional decides. Write to Ilumible anyway if you cannot reach them and Ilumible will pass it on and tell you it did.

3. What Ilumible holds about a subscriber

Only what running the product needs. There is no data broker, no enrichment, no purchase of lists.

  • Name, email address, phone number and date of birth, entered by you.
  • Your business: name, address, timezone, currency, working hours, services and prices.
  • A profile picture and a business logo, if you upload them.
  • Subscription state — plan, status and billing dates. Card numbers never reach Ilumible; see Stripe below.
  • Access tokens for Google or Zoom, but only if you connect them yourself, and only for as long as the connection lasts.

4. What Ilumible holds about someone who books

Collected on the professional’s behalf, at the moment of booking, and kept in that professional’s records only.

  • Name, email address and phone number, as typed into the booking form.
  • The appointments themselves: date, time, services, price and any note left on the booking.
  • Your address, and only if the professional sees people at their client’s address and you booked one of those. It is held against that one appointment rather than in your record: booking from home once and from work the next time rewrites nothing.
  • Notes the professional writes about you, which you cannot see.
  • If you later create an account with the same confirmed email address, your past bookings with that professional are attached to it.
  • One person booking with two different professionals is two separate records. Neither professional can see the other’s.

5. Why, and on what legal basis

Under LGPD article 7 and, where it applies, GDPR article 6. Purpose by purpose:

  • Running your account and your calendar — performance of a contract (LGPD art. 7, V; GDPR art. 6(1)(b)).
  • Sending booking confirmations, reminders and cancellations — performance of a contract for the subscriber; legitimate interest of the professional for the person who booked (LGPD art. 7, IX; GDPR art. 6(1)(f)).
  • Taking payment and keeping billing records — performance of a contract and legal obligation (LGPD art. 7, II and V).
  • Keeping the service working and investigating errors — legitimate interest (LGPD art. 7, IX).
  • Measuring how the public site is used — legitimate interest. See section 10, which describes exactly what loads and when.

6. Who else processes your data

Ilumible is one person and a lot of infrastructure. These are the companies that hold or move your data, what each one does, and where it runs. This list changes when the product changes.

  • Supabase — the database, sign-in, and stored files. Everything above lives here. Hosting region: PENDING VERIFICATION — confirm which region the project is provisioned in before publishing.
  • Vercel — hosting for the site, the booking pages and the dashboard. Serves pages and collects request logs.
  • Stripe — subscription payments. Checkout runs on a page belonging to Stripe, so card details never pass through Ilumible.
  • Resend — sends every email: confirmations, reminders, cancellations, sign-in and password links.
  • Google — Calendar and Meet, only for a subscriber who connects their Google account; Maps, to show a business address on a booking page. When a professional connects Calendar, the event it creates carries the address of the appointment — including yours, for a visit to your home. That calendar may be shared with their team, and Ilumible neither controls nor can see that.
  • Zoom — meeting links, only for a subscriber who connects Zoom.
  • Sentry — error reports from the server side, which can incidentally include an identifier of the account that hit the error. Optional and may not be enabled.
  • Google Analytics and Vercel Analytics — measurement on the public marketing site only. Not present on the dashboard or on a booking page.

7. Data leaving Brazil

It does. The providers above run outside Brazil, so operating the product means transferring personal data internationally under LGPD article 33. The basis relied on is that the transfer is necessary to perform the contract you entered into (LGPD art. 33, II), and each provider is bound by its own data processing terms.

8. How long data is kept

Honestly: there is no automatic deletion today. Nothing expires on a schedule, and no job removes old appointments or old client records. Data stays for as long as the account exists, and goes when it is deleted on request.

  • While your account exists — everything above is kept.
  • After you ask for deletion — the account and the records that hang off it are removed by hand, within 30 days of the request.
  • Billing records — Stripe keeps its own for as long as its own retention and tax obligations require, independently of anything deleted here.
  • PENDING VERIFICATION: the owner should decide the retention period he wants to commit to for finished appointments, and whether it should be enforced by a job rather than by a promise.

9. Your rights, and how to use them today

LGPD article 18 and GDPR articles 15 to 22 give you confirmation, access, correction, anonymisation or deletion, portability, information about sharing, and the right to object. All of them are available. None of them is a button yet.

  • The process is email. Write to the address below saying what you want and which email address or phone number your records are under.
  • Expect an answer within 15 days, which is the LGPD deadline.
  • There is no self-service export and no self-service deletion screen in the product. Both are done by hand against the database. That is a real limitation, not a policy choice, and it is on the list to fix.
  • If you booked with a professional rather than subscribing yourself, the professional decides — see section 2.
  • You can complain to the ANPD in Brazil, or your local supervisory authority, at any time.

10. Cookies and measurement

Described exactly as it behaves today, which is not the same as how it should behave. On this marketing site only, Google Analytics and Vercel Analytics load as soon as the page does — before you are asked anything, because you are not asked anything. There is no cookie banner and no consent gate.

  • Google Analytics sets cookies in your browser and measures pages and visits.
  • Vercel Analytics measures page views. PENDING VERIFICATION: confirm with Vercel’s current documentation whether it sets any cookie before describing it as cookieless.
  • You can block both with your browser settings or an extension, and nothing on the site stops working.
  • The dashboard and the booking pages carry neither. Only cookies needed to keep you signed in.
  • Adding a consent gate before these load is a change worth making. It has not been made, and this section says so rather than implying otherwise.

11. Security, described only as far as it can be pointed at

What follows is what the code does, not a standard being claimed. There is no certification, no penetration test and no monitoring rota.

  • Every table carries row-level security policies, so one business cannot read another’s rows even through a direct API call.
  • Traffic runs over HTTPS, terminated by Vercel and Supabase.
  • Card details never reach Ilumible: checkout is a page hosted by Stripe.
  • Secrets that reach outside services stay on the server side and are not compiled into anything a browser downloads.
  • Backups are whatever the Supabase plan provides. Ilumible runs no backup of its own and makes no promise about restore times.
  • There is no uptime monitoring and nobody is on call.

12. Children

Ilumible is not built for children and is not offered to them. Do not create an account if you are under 18. A professional may book an appointment for a minor as part of their own service; when that happens the professional is responsible for having the consent of whoever is legally responsible for that child (LGPD art. 14).

13. When this policy changes

The date at the top changes whenever the text does, and the previous version stays in this repository’s history. A change that widens what is collected or who receives it will be announced by email to subscribers before it takes effect. Small corrections will not be.

Every request and every question goes to one address:

wendel@ilumible.com