elastudio Privacy Policy

Version 1.6. Effective date: 27 October 2026. Version 1.5 applied earlier that day. Version 1.4 applied from 15 October 2026 (versions 1.3 and 1.2 earlier that day), version 1.1 from 14 October 2026 and version 1.0 from 13 October 2026, when elastudio went live.

This policy explains how elastudio handles personal information about studio owners and staff who use elastudio, and about visitors to our website elastudio.app and to our sign-in and sign-up pages at app.elastudio.app. It is written to meet Brazil’s LGPD (Lei Geral de Proteção de Dados, Law 13.709/2018), Canada’s PIPEDA (Personal Information Protection and Electronic Documents Act) and similar laws.

Are you a member of a yoga or pilates studio? If you book classes at a studio that uses elastudio, the studio decides how your information is used. The studio is the “controller” and elastudio only processes your data on the studio’s behalf (as its “operator” or “processor”). Please read your studio’s privacy notice and contact the studio first. Section 11 explains how we help. If you use our website, our sign-in and sign-up pages at app.elastudio.app or our help centre directly, including the help assistant, elastudio is responsible for that information and this policy applies.

1. Who we are

elastudio is a booking platform for yoga and pilates studios. It is operated by Edilson Brito Bezerra Junior, operating as BRITO.AI, a sole proprietorship registered in Ontario, Canada (“elastudio”, “we”, “us”).

• Registered business name: BRITO.AI, registered under Ontario’s Business Names Act. GST/HST registration number: 786293639 RT0001
• Mailing address: 73 Watt Street, Guelph, Ontario N1E 6W6, Canada
• Support: support@elastudio.app (in English and Brazilian Portuguese only)
• Privacy and data protection: privacidade@elastudio.app

Privacy officer and encarregado (data protection officer under LGPD): Edilson Brito Bezerra Junior, privacidade@elastudio.app. He is accountable for elastudio’s compliance with privacy law (PIPEDA Principle 1) and is the contact for people and for Brazil’s data protection authority, the ANPD (Autoridade Nacional de Proteção de Dados).

Where we offer elastudio. We offer elastudio to studios in most countries. We do not yet offer it to studios in Quebec, the European Union, the European Economic Area or the United Kingdom. Before we do, we will update this policy and appoint a representative there where the law requires one.

2. What information we collect, and why

We collect only what we need. For each purpose, the table shows the legal basis we rely on under LGPD. Under PIPEDA, we rely on your consent, which is implied where the use is obvious from the context (for example, using your e-mail to run your account) and express where it is not (for example, analytics cookies and marketing e-mails). For the help assistant, we tell you in the assistant itself, before your first question, that your question goes to Anthropic in the United States, and we keep a record of your agreement. If you visit our website from the European Union or the United Kingdom, we rely on the matching GDPR (General Data Protection Regulation) bases: contract (art. 6(1)(b)), legitimate interest (art. 6(1)(f)) and consent (art. 6(1)(a)).

Who	What we collect	Why	Legal basis (LGPD)
Studio owners and staff	Name, e-mail, phone number (optional), role, studio name and details, language, sign-in records (time, IP address, browser), and counts of which features your studio uses (not linked to a person)	To create and run your account, sign you in, keep it secure, support and bill the studio	Studio owners: performance of a contract (art. 7, V). Staff invited by a studio: our legitimate interest, and the studio’s, in giving its team access (art. 7, IX). Security: legitimate interest
Studio owners who sign up for elastudio	When you create your studio: your name and e-mail (or your Google account, if you sign up with Google), the studio’s name, its web address on elastudio, country, city and time zone, and what it teaches (yoga, pilates, both or another practice, in your words); a record that you agreed to our Terms and were shown this policy (the versions shown, the date and time, your IP address and browser). Afterwards, only if you answer (every question is optional): how you heard about elastudio (and, if you choose to tell us, who recommended it or where you heard about it), roughly how many members your studio has a month, a monthly revenue range in your currency (or “prefer not to say”), how members pay you today, whether you already use a booking platform and which one, how many teachers you have, and your studio’s website and social media profiles	To create and set up your studio (currency, languages, time zone, suggested class types); to propose your logo, colours and fonts from your website; to show your social media profiles publicly on your studio’s About page; to keep a record that you agreed to our Terms; to suggest the right plan and offer to import from the platform you use today; and to understand who signs up and how they found us (counted in totals from our own database, never sent to analytics or advertising services)	Creating and setting up the studio: performance of a contract and steps you ask for before it (art. 7, V). The agreement record: performance of a contract (art. 7, V) and the exercise of our rights in legal proceedings (art. 7, VI). Optional answers, the name of who recommended us, and counting who signs up and how they found us: our legitimate interest in improving elastudio and knowing which channels bring studios (art. 7, IX, and art. 10, I)
Studio owners and staff who sign in with Google	Your Google account name, e-mail and an account identifier	To let you sign in without a password	Performance of a contract (owners) or legitimate interest (staff)
Studio owners and staff who add a password with two-step verification	Your password, stored only as a salted one-way hash, so we never keep or see the password itself; the secret key shared with your authenticator app, stored encrypted; your backup codes, stored only as hashes; the time step of the last code accepted (so each code works once); short-lived sign-in checks that let you finish signing in (stored as hashes, valid for 5 minutes); and, if you ask our support to reset your password and two-step verification, who at elastudio checked your identity and how (we record the method, never a copy of an identity document)	To let you sign in with a password protected by a code from your phone, to e-mail you whenever these settings change, and to help you back in if you lose your phone	Performance of a contract (art. 7, V) for owners, or legitimate interest (art. 7, IX) for staff; security: legitimate interest (art. 7, IX)
Teachers who connect Google Calendar	Busy and free time periods only (no event titles, attendees or details). If the teacher also shows their classes in Google Calendar: the id of the one calendar elastudio creates in their account, and for that calendar only, the id, status and last change time of the events elastudio put there	To stop private sessions from being booked when you are busy, and to keep your classes and private sessions up to date in your own calendar	Not applicable: here we act as the studio’s processor (section 11)
Studio owners (billing)	Plan, billing contact, invoices, payment status, the last 4 digits and expiry of the card, country, province or state, tax details where needed	To bill your elastudio plan and charge the right sales tax	Performance of a contract; legal obligation for tax records (art. 7, II)
Anyone who contacts support	Your message, e-mail address and anything you choose to include	To answer you and fix problems	Performance of a contract or legitimate interest
Staff who send a bug report	Description, page, app version, role, studio identifier, optional screenshot	To find and fix bugs in the service	Performance of a contract (art. 7, V); legitimate interest in fixing the service (art. 7, IX)
Website visitors	Technically necessary data (IP address, browser, pages requested) in server logs. Your approximate country, which our hosting provider Cloudflare works out from the IP address of your connection each time you open a page; we use it at that moment and do not store it. If you use the language switch or open a link that asks for a specific language (such as the links in the elastudio dashboard and on the sign-in page), the els_lang cookie with that language. If you arrive through a link with campaign tags (such as utm_source), those tags, which we copy onto the sign-up links of that page	To deliver and protect the website, to show it in your language with prices in your currency (see “Language and currency on elastudio.app” below), and to pass a campaign link’s tags on to the sign-up page	Legitimate interest (art. 7, IX, and art. 10, I)
Website visitors who accept analytics cookies	Pages viewed, the links and buttons you click (for example the sign-up buttons; a click on a sign-up button such as “Start free”, or on our support e-mail address, is counted as a lead, with which button it was, the page language and the currency shown), how you reached our site (the website you came from and any campaign tags in the link, such as utm_source), clicks and scrolls, recordings of how you move through our pages (all page text and anything you type are hidden), device and browser type, approximate location from IP address. In your browser only (els_attr, 90 days): the campaign tags and any ad click id (such as Google’s gclid) of the first and the most recent campaign link that brought you, with the page you landed on and the date and time; sign-up links then carry those tags, so Google Analytics can see which campaign brought you	To understand how the website is used and improve it, and to measure which campaigns bring studios to elastudio	Consent (art. 7, I)
Visitors of the sign-in and sign-up pages at app.elastudio.app who accept analytics cookies there	Only Microsoft Clarity runs there, and only after you accept it in that page’s own cookie banner: clicks, scrolls and recordings of how you move through the pages with the whole page hidden (all text, and anything you type, such as your e-mail address, name and studio name, is hidden in your browser before the recording is sent to Microsoft), device and browser type, approximate location from IP address, and labels we add to each recording naming only the screen, the sign-up step, the type of business, the country and the language you chose. Never your name, e-mail address or studio name, and no recording of a visit that arrives through a sign-in link, a Google sign-in or the opening of a studio	To see where people get stuck signing in or creating a studio, and to fix it	Consent (art. 7, I)
Website visitors who make a cookie choice (on elastudio.app or on app.elastudio.app, each recorded separately)	A random identifier (also stored with your choice in your browser), your choice, the banner version and language, the date and time, and a keyed hash of your network (the first part of your IP address, scrambled with a secret key that only we hold, so the hash on its own does not reveal your network). We treat this hash as personal information. No name, no browser details and never your full IP address	To remember and prove your cookie choice, and to limit abuse of the record, such as automated fake submissions (the network hash)	Legitimate interest in being able to prove consent, a burden LGPD art. 8, §2 places on us, and in protecting the record from abuse (art. 7, IX)
Website visitors who use the help assistant	The question you type, the assistant’s answer, your earlier questions and answers in the same conversation (up to three), the page language, and your approximate country (worked out from your IP address and used only to show prices in your currency). To limit misuse, we count your questions under a short scrambled code (a hash) made from your IP address and the current hour. The code could in theory be traced back to your address, so we treat it as personal information; it is deleted automatically after about an hour	To answer your questions about how elastudio works from our help articles, and to stop the assistant being misused	Our legitimate interest in answering questions about elastudio and protecting the service (art. 7, IX, and art. 10, I). When you ask about a plan you want or already have, also steps you ask for before signing up, or performance of a contract (art. 7, V). We do not want sensitive information such as health details; if you type it anyway, we do not keep or use it. Sending your question to Anthropic in the United States: your consent, given in the assistant (section 5)
Website visitors who agree to the help assistant’s notice	A random identifier (also stored in your browser), the version and language of the notice you agreed to, and the date and time. No question, no name, no browser details and no IP address in the record. To limit abuse, such as automated fake submissions, agreements sent from one network are counted for an hour under a scrambled code (a keyed hash) of your network (the first part of your IP address), which is deleted within 2 days and is never stored with the record	To prove that you agreed before your questions went to Anthropic in the United States, and to limit abuse of the record	Legitimate interest in being able to prove consent, a burden LGPD art. 8, §2 places on us, and in protecting the record from abuse (art. 7, IX)
Studios and prospects we contact about elastudio	Name, business e-mail, studio name, our conversation history	To tell you about elastudio	Legitimate interest (art. 7, IX), or your consent (art. 7, I) where you gave it. For e-mails we also follow Canada’s anti-spam law (CASL), see section 10

What is required. You must give us your name and e-mail to have an account; your studio’s name, its web address on elastudio, country, city and what it offers, and your agreement to our Terms, to create a studio; and billing details to pay for a plan. Without them we cannot provide elastudio. The questions about your studio after sign-up (how you heard about us, size, revenue, payments, booking platform, teachers, website and social profiles) are optional. Everything else, including analytics cookies and marketing, is also optional, and saying no changes nothing about your account.

Legitimate interest. Where we rely on legitimate interest, we have weighed our interest against your rights. You can object, and we will stop unless we have a strong reason to continue, such as security or a legal claim. You can ask us for a summary of that assessment.

Payments. Card details for your elastudio plan are entered directly into Stripe, our payment provider. elastudio never sees or stores full card numbers.

Your brand and answers at sign-up. If you give us your studio’s website, we read its public home page (and the images, style sheets and web app manifest it links to) once, when you ask, to propose your logo, colours and fonts; nothing is saved unless you choose to use them. We never read your social media profiles: we store only the profile addresses you type, and show them publicly on your studio’s About page. Your revenue range and your other answers about your studio are seen only by you (the studio’s owner) and by the elastudio team. We use them to set up your studio and suggest a plan, and we count them in totals to understand who signs up and how; they are never sent to Google Analytics, Microsoft Clarity or any advertising service, and we never sell them. The sign-up page does not keep the campaign tags or ad click ids of the link that brought you (our hosting provider’s security logs keep page addresses for up to 7 days, as in section 6).

AI in bug reports. When staff send a bug report, our software first removes e-mail addresses, phone numbers and similar contact details from the text. The cleaned text, the sender’s role and the page address (with identifiers removed) go to an AI service (Anthropic) to suggest a title, a category and a severity, so a person at elastudio can review it. Other details someone types, such as a name, may remain, so please do not include member information in bug reports. The AI does not take any action in your studio and does not decide anything about you. Screenshots are never sent to the AI service; they stay in elastudio’s storage. Anthropic’s Commercial Terms say: “Anthropic may not train models on Customer Content from Services”, and, under its current policy, Anthropic deletes inputs and outputs within 30 days, except content flagged for abuse, which it may keep longer (checked 11 October 2026, anthropic.com/legal/commercial-terms).

AI help assistant. Our help centre (elastudio.app/help, elastudio.app/pt-br/ajuda and elastudio.app/es/ayuda) has an assistant that answers questions about how elastudio works, using only our help articles. Before your first question, the assistant tells you that your question goes to Anthropic in the United States and asks you to agree. We keep a record of that agreement (section 2 table and section 6) so we can show it was given, and your browser remembers it so the assistant does not ask on every page. It asks again when we change the notice and after 6 months. When you ask it something, your question, up to three of your earlier questions and answers in the same conversation, the page language and the currency for prices are sent through Cloudflare AI Gateway (a Cloudflare service; Cloudflare is our hosting provider) to Anthropic in the United States, which writes the answer. Anthropic does not receive your IP address. Logging of questions and answers in the gateway is switched off, and elastudio does not store them: the conversation exists only in your open browser tab and is gone when you close, reload or leave the page. Because we keep no copy, we cannot retrieve or delete a past conversation for you; Anthropic deletes it on the schedule below. The assistant sets no cookies. The only thing it saves in your browser is that you agreed (els_help_consent: a random identifier, the version and language of the notice and the date and time, never your questions), for 6 months. You can withdraw your agreement at any time with “Withdraw agreement” in the assistant: your browser forgets it, and no question is sent until you agree again. Withdrawing does not affect questions already sent to Anthropic. We keep the record of your earlier agreement for the period in section 6, as proof that it was given. The assistant cannot see any studio, account or member data, takes no action and decides nothing about you. The same Anthropic terms apply as for bug reports: no training on this content, and deletion within 30 days except content flagged for abuse. Please do not type personal information, health information or information about anyone else into the assistant. For questions about your own account, write to support@elastudio.app.

Language and currency on elastudio.app. When you open a page of elastudio.app, Cloudflare, our hosting provider, tells our website which country your connection appears to come from, based on its IP address. This is only an estimate of your country, not your precise location, and it can be wrong, for example if you use a VPN. We use it only while the page is being prepared for you. elastudio.app is available in English, Brazilian Portuguese and Spanish (the Spanish pages, including the help centre at elastudio.app/es/ayuda, are under elastudio.app/es). Until you choose a language yourself, visitors whose connection appears to come from Brazil get the pages in Brazilian Portuguese, visitors whose connection appears to come from a Spanish-speaking country (such as Mexico, Argentina, Colombia or Spain) are sent to the same page in Spanish, and visitors from other countries get them in English; if Cloudflare cannot tell the country, you get the page you opened. Prices are shown in reais (R$) for Brazil, Canadian dollars (CA$) for Canada and US dollars (US$) everywhere else. The sign-up links on the page carry the same currency and country, so the sign-up page shows the same prices. They also carry the campaign tags (such as utm_source) of the link that brought you, if it had any, whether or not you accept analytics cookies; we do not store them unless you accept, apart from our hosting provider’s security logs, which keep the addresses of pages opened for up to 7 days. Only if you accept analytics cookies do they also carry an ad click id (such as Google’s gclid). elastudio does not save your country or build a profile from it, and we use it for nothing else. If you accepted analytics cookies, Google Analytics records the addresses of the pages and links you open, which can include that currency and country. You can change the language at any time with the language switch. Links that ask for a specific language, such as those in the elastudio dashboard and on the sign-in page, also open this site in that language. Either way, we save that language in the els_lang cookie for 1 year, and from then on the language is no longer set by your country. Prices always follow your country. Search engines get the page they ask for, in any of the three languages. Reading elastudio.app in Spanish does not change where elastudio is offered (section 1) or the languages of support (section 14).

Google data. elastudio’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google sign-in gives us only your name, e-mail and account identifier. Google Calendar access has two parts. The busy-time check is read-only and limited to free and busy times: we never read the titles, attendees or details of events in your calendars. If you also switch on “Show my classes and private sessions in my Google Calendar”, elastudio asks Google for one more permission (calendar.app.created). It lets elastudio create one calendar of its own in your account and manage only the events in that calendar; it cannot see or change your other calendars or their events. elastudio writes your classes and confirmed private sessions there (the class or session name, room, place and address, the studio’s name, the number of bookings and the waiting list, and a link back to elastudio), never members’ names, contact details, notes or messages, and never a member’s home address (home sessions say “At the member’s address”), and reads back only those events, to keep them correct. We use what we receive from Google only to provide these two features to you: never for advertising, never to train AI models, never sold, and passed to others only as needed to run these features (our hosting provider, Cloudflare), to comply with the law, or, with your explicit prior consent, as part of a sale of elastudio; and people at elastudio do not read it except with your permission, for security, or where the law requires it. You can switch the calendar off or disconnect at any time in My schedule: elastudio then deletes its calendar from your Google account (when Google can be reached; if it cannot, we tell you the calendar stayed so you can delete it in Google Calendar), deletes the stored connection token and revokes our access at Google.

Automated decisions. elastudio does not make decisions about you that are based only on automated processing and that have legal or similarly significant effects.

Children. elastudio accounts are for adults running a business. We do not knowingly collect information from children for our own purposes. When a studio enrols members under 18, the studio adds them through its staff and records a parent’s or guardian’s consent; members cannot sign themselves up unless they confirm they are 18 or older. The studio is responsible for that consent (section 11).

3. Where your information comes from

Mostly from you. When you sign up, you may tell us who recommended elastudio. That name comes from you: please give only a name (no contact details), and only if that person would not mind. We do not use it to contact them. If you are the person named and want it removed, write to privacidade@elastudio.app. If you ask us to, we also read your studio’s public website (logo, colours and fonts). Some comes from Google (when you choose Google sign-in or connect Google Calendar), from Stripe (payment status for your plan), and from the studio you work for (when an owner invites you as staff). For studios we contact about elastudio, we may use business contact details the studio has published itself (for example on its website or social media profile).

4. Who we share it with

We do not sell personal information, and we do not use it for our own advertising. In Google Analytics, Google signals and data sharing with Google are switched off, and Microsoft Clarity is not linked to Microsoft Advertising. If you accept analytics cookies, Microsoft Clarity may also set a Microsoft identifier (MUID) that Microsoft may use for its own services, including advertising, under the Microsoft Privacy Statement. If you do not accept, it is never set by our website.

We share information only with:

• Service providers who host and run elastudio for us, under contracts that require them to protect it: Cloudflare (hosting, database, file storage, e-mail sending, access control, and the AI Gateway that carries help assistant questions), Resend (backup e-mail sending, only when Cloudflare refuses a message because of its sending limits), Stripe (payments for your elastudio plan), Google (our support and privacy e-mail), Anthropic (bug report triage and the help assistant) and, only if you accept analytics cookies, Google Analytics and Microsoft Clarity. The full list, with what each does and where, is in our Sub-processor list at elastudio.app/legal/subprocessors.
• Google sign-in and Google Calendar, only if you choose to connect your own Google account. Google acts under its own terms and sends us only what section 2 lists.
• Our accountant, to keep our books and file taxes.
• Your studio, for staff and teachers: the studio owner and admins can see staff accounts within their studio.
• Authorities, when the law requires it (for example, a valid court order). Where we are allowed to, we will tell the affected studio or person first.
• A buyer or successor, if elastudio is sold or transferred, including a prospective buyer, under a confidentiality agreement, while a sale is being considered. The new owner must keep the promises in this policy, and we will tell you when it happens.

5. International transfers

elastudio is operated from Canada. Our main database and file storage are hosted by Cloudflare in eastern North America. Cloudflare offers no Canada-only option, so you should treat this data as stored in the United States. Our other service providers are mainly in the United States. Cloudflare’s network also passes requests through data centres around the world, close to the visitor. That means your information is processed outside the country where you live, including outside Brazil. Information held in another country can be accessed by that country’s courts and authorities under its laws.

For people in Brazil. When you give us your information directly (for example, when you create a studio account), we collect it from outside Brazil. Under the ANPD’s rules on international transfers (Resolução CD/ANPD nº 19/2024, Annex I, articles 3, V and 6) this is an international collection, not a transfer, and LGPD still applies to it in full. When we then send that information to our providers in the United States, we rely on these LGPD article 33 mechanisms:

Provider	What it receives	Mechanism (LGPD art. 33)
Cloudflare	Everything in section 2 except analytics (hosting, e-mail sending, server and security logs, the record of your cookie choice, the record of your help assistant agreement, help assistant questions passing through its AI Gateway, and the hourly question-count code)	Account and billing data of studio owners: necessary to perform our contract with you and to meet legal obligations (art. 33, IX, with art. 7, II and V). For all of it, Cloudflare acts only on our instructions under its written data processing terms
Resend (Plus Five Five, Inc.)	Only when Cloudflare refuses an e-mail because of its daily sending limit or a rate limit: that e-mail (sign-in links and codes, invitations, account, security and billing notices), with your e-mail address and name; kept by Resend up to 30 days (backups up to 7 days more)	Studio owners: necessary to perform our contract with you (art. 33, IX, with art. 7, V). For all of it, Resend acts only on our instructions under its Terms of Service and Data Processing Addendum
Stripe	Billing data for your plan	Necessary to perform our contract with you and to meet legal obligations (art. 33, IX, with art. 7, II and V)
Google (Workspace e-mail)	Support and privacy e-mails	The ANPD standard contractual clauses in Google’s Cloud Data Processing Addendum (art. 33, II, b)
Anthropic	Cleaned bug report text; help assistant questions and answers	Bug reports: necessary to perform our contract with you, which includes reporting and fixing problems in the service (art. 33, IX, with art. 7, V). Help assistant: your specific and highlighted consent, given in the assistant before your first question, which tells you that your question goes to Anthropic in the United States (art. 33, VIII). For both, Anthropic acts only on our instructions under its Commercial Terms and data processing addendum
Google Analytics, Microsoft Clarity	Website usage, and for Microsoft Clarity also usage of the sign-in and sign-up pages at app.elastudio.app, only if you accept	Your specific and highlighted consent, given in the cookie banner, which tells you, in bold, that the data goes to Google and Microsoft in the United States (art. 33, VIII)

Google sign-in and Google Calendar are not transfers by us: you connect your own Google account, and Google sends us your name, e-mail and identifier, or your free and busy times. When you switch on your classes, elastudio sends your own schedule, at your request, to a calendar in your own Google account (Google, United States), which Google holds under its terms with you, not as our provider. You can ask us for more detail, or a copy of the clauses, at privacidade@elastudio.app. For studio member data, where the studio is the controller, the transfer rules are in our Data Processing Agreement (section 11 below).

For people in Canada. We use contracts that require our providers to protect information to a standard comparable to ours.

For visitors from the European Union or the United Kingdom. Canada has an adequacy decision from the European Commission (and recognition under UK law) for organisations subject to PIPEDA. For onward transfers to providers in the United States we rely on their EU standard contractual clauses or their certification under the EU-U.S. Data Privacy Framework (and, for UK data, its UK Extension).

6. How long we keep it

Information	How long
Studio and staff account data	While the account is active. After a studio closes its account it can export its data for 30 days, and we then delete it
Sign-up answers and the record of your agreement at sign-up	While the studio’s account exists, then deleted with it (after the 30-day export window). If a studio’s sign-up is never finished and there is no activity on it for 30 days, we close that studio and delete its sign-up record and the owner’s profile in it automatically. If you delete your own elastudio identity, the answers stay with the studio’s account but are no longer linked to you, and the IP address and browser in the agreement record are deleted; until then we keep them with the record, as proof of your agreement
Billing records and invoices	6 years from the end of the tax year they relate to, as Canadian tax law requires (longer if a tax authority asks)
Support e-mails	Up to 3 years after the conversation ends, then deleted
Bug reports and screenshots	1 year, then deleted automatically
Google Calendar connection (tokens, the id of elastudio’s calendar, the ids of its events)	Until you switch the calendar off or disconnect, then deleted
Help assistant questions and answers	Not stored by elastudio: they exist only in your open browser tab until you close or reload it. The question-count code: deleted automatically after about an hour (62 minutes at most). At Anthropic: deleted within 30 days under its current policy, except content flagged for abuse
Record of your help assistant agreement	6 months in your browser (els_help_consent), or until the notice changes (then removed the next time you open the help centre); removed at once if you withdraw; the record on our server (a random identifier, the notice version and language, the date and time; never your questions or your IP address) for 20 months, so we can show consent was given. The abuse-limit counter: deleted within 2 days
Website and app server logs	Up to 7 days, then deleted by our hosting provider
Your approximate country (page language and currency)	Not stored: used only while the page is being prepared for you
Your language (els_lang cookie, only if you use the language switch or open a link that asks for a specific language)	1 year in your browser from when it was last set
Sign-in records	Up to 12 months
Password, authenticator key and backup codes	Password: until you change it, our support resets it at your request, or your account is deleted (turning two-step verification off keeps the password, but it then no longer opens a studio’s admin). Authenticator key and backup codes: until you turn two-step verification off, our support resets it, or your account is deleted; backup codes, used or not, until you create a new set. The last accepted code step is replaced at each sign-in. Sign-in checks: deleted a day after they expire. Counters of wrong attempts (which include your network address): deleted within a day. Records of a support reset (who checked and how): 2 years after the reset, then deleted
Security audit log of a studio	While the studio’s account exists, then deleted with it; IP addresses in it are removed after 12 months
Analytics data (only with consent)	Google Analytics: detailed data 14 months (summary statistics that do not identify you can remain in reports). Microsoft Clarity: up to 13 months
Campaign record in your browser (els_attr, only with analytics consent)	90 days from your last visit through a campaign link, then no longer used and removed on your next visit; deleted at once if you reject or withdraw analytics cookies. We keep no copy of this record on our servers; tags sent with a sign-up link stay in our hosting provider’s logs for up to 7 days and in Google Analytics (see Analytics data)
Record of your cookie choice	6 months in your browser (the cookie and its copy in browser storage); the record on our server (a random identifier, your choice, the banner version and language, the date and time, and a keyed hash of your network, never your full IP address) for 20 months, so we can show consent was given
Prospect and marketing contacts	Until you unsubscribe or ask us to delete, or 2 years after our last contact, whichever comes first. We keep only your e-mail address on a do-not-contact list for as long as we send marketing e-mails, so we never contact you again, and our record of your consent or unsubscribe for 3 years after our last contact, so we can show we respected your choice
Records of security incidents	At least 5 years after the later of the date the incident was logged and the date it was closed, then deleted unless needed for a legal claim

Backups follow the same rules and expire on their own schedule: nightly backups are kept for 30 days, and the database host keeps a 30-day point-in-time recovery history, so deleted data is gone from every copy within about 30 days.

7. How we protect it

Data is encrypted in transit (HTTPS) and at rest. Each studio’s data is kept separate from every other studio’s, and this separation is tested automatically before every release. Sign-in tokens, connection keys and similar secrets are encrypted before they are stored. Owners and staff who sign in with a password must also enter a code from an authenticator app, or one of their single-use backup codes (two-step verification). The app’s secret key is encrypted, backup codes are kept only as hashes, the number of wrong attempts is limited, and we e-mail you whenever these settings change. Card numbers never reach elastudio. Access to production systems is limited to authorised people (today, one person), protected by two-step sign-in, and logged. No system is perfectly secure, but we work to the standards described in our Data Processing Agreement.

If there is a breach, we follow our written incident response plan. For information we control, when a breach may create a relevant risk or damage to people in Brazil, we notify the ANPD and the people affected within 3 business days of learning that personal information was affected. When it creates a real risk of significant harm to people in Canada, we report it to the Office of the Privacy Commissioner of Canada and notify the people affected as soon as feasible. For studio member data, we notify the studio within 48 hours and help it notify (section 11). We keep a record of every breach for 5 years.

8. Your rights

Depending on where you live, you have the right to:

• know whether we hold information about you and get a copy of it (in a portable format where the law provides it);
• correct information that is wrong or incomplete;
• delete information, or have it anonymised or blocked when it is unnecessary, excessive or handled unlawfully;
• delete information you gave us with your consent;
• withdraw consent at any time (for example, for analytics cookies or marketing e-mails), without affecting what happened before;
• object to processing based on legitimate interest, and to direct marketing at any time;
• move your information to another provider, where the law gives that right (portability);
• know who we have shared your information with (LGPD art. 18, VII);
• be told what happens if you do not consent (LGPD art. 18, VIII);
• ask for a review of decisions made only by automated processing (LGPD art. 20). elastudio makes none today;
• complain to a data protection authority (see below).

How to ask. E-mail privacidade@elastudio.app. We may need to confirm your identity first. For access requests under LGPD, we give a simplified confirmation right away and a full answer within 15 days. Under PIPEDA we answer within 30 days; if a request is complex, we may extend that by up to 30 more days as the law allows and will tell you why, and that you can complain to the Privacy Commissioner of Canada. Exercising your rights is free.

Authorities you can complain to:

• Brazil: ANPD, https://www.gov.br/anpd
• Canada: Office of the Privacy Commissioner of Canada, www.priv.gc.ca
• European Union or United Kingdom: the data protection authority where you live (in the UK, the Information Commissioner’s Office, ico.org.uk)
• Mexico: the Secretaría Anticorrupción y Buen Gobierno (see section 15)

We would appreciate the chance to sort it out first at privacidade@elastudio.app.

9. Cookies

Without your consent, elastudio.app uses only strictly necessary cookies, including the els_lang cookie, which remembers your language if you use the language switch or open a link that asks for a specific language (such as the links in the elastudio dashboard and on the sign-in page). Choosing the language and currency by your country uses no cookie. Analytics cookies (Google Analytics 4 and Microsoft Clarity) are loaded only on elastudio’s own website pages, and Microsoft Clarity alone also on the sign-in and sign-up pages at app.elastudio.app (not on studio booking pages or the dashboard), and are off until you accept them. app.elastudio.app asks for its own choice, with its own “Cookie settings” link at the bottom of its pages. Only with consent on elastudio.app does the website also keep in your browser, for 90 days, which campaign links brought you (els_attr). You can change your mind at any time through “Cookie settings” at the bottom of every public page. The studio dashboard, studio booking pages and the booking widget on studios’ own websites use only strictly necessary cookies and storage. The help assistant sets no cookies; it keeps only your agreement to its notice in browser storage (els_help_consent, 6 months), listed in the Cookie notice. Details: Cookie notice.

10. Marketing e-mails

We send marketing e-mails only with your consent or where Canada’s anti-spam law (CASL) and the law of your country allow it. Every marketing e-mail identifies BRITO.AI and elastudio, gives our mailing address and an e-mail address where you can reach us, and has a working unsubscribe link. We act on unsubscribes within 10 business days, usually much sooner. When we use a business e-mail address a studio has published, we write only about matters relevant to the studio’s business, and never where the studio has said it does not want unsolicited messages. Service e-mails about your account (for example, invoices, payment reminders and security alerts) are not marketing and you will still receive them.

11. Studio member data: where elastudio is the processor

When a studio uses elastudio to manage its members (names, contacts, bookings, purchases, optional health notes, an optional profile photo and an optional password, which we store only as a salted hash and never see or e-mail), the studio is the controller and elastudio is the processor (operator under LGPD). We handle that data only on the studio’s instructions and under our Data Processing Agreement with the studio, which includes the ANPD standard contractual clauses for transfers from Brazil. The same applies to teachers’ calendar free and busy times, to the classes elastudio writes to a teacher’s Google Calendar, and to the optional profile photo a studio’s owner, staff member or teacher adds in My profile. That photo is used only so people recognise each other at the studio and at class, and, when a teacher’s profile has no photo of its own, it is shown with that teacher’s profile and classes on the studio’s public booking pages. It is stored as an image file with Cloudflare in the United States, at a random address that opens without signing in, after we remove the hidden details in the file (such as where and when it was taken). While on the studio’s team, the person can replace or remove it at any time in My profile, which deletes the stored file at once, and it is deleted with their account. A member’s own optional profile photo, added in Account > Profile, is private: only the member and the studio’s team see it (owner, admins and front desk, and teachers only for members booked or waitlisted in a class they teach), so they can recognise the member. It never appears to other members, on public pages, in e-mails or in calendar events, opens only for someone signed in, is stored with Cloudflare in the United States after the same removal of hidden details, cannot be added or changed by the studio’s staff, and is deleted when the member removes or replaces it or when their account is deleted or erased. We use member data only to provide elastudio to the studio. The one exception is counts and totals that do not identify any member (for example, how many members, bookings or sales a studio had in a month), which we use to run, support, bill and improve elastudio. We never sell member data or use it to advertise.

When a member’s account is deleted, we remove what identifies them from the studio’s records. At the studio’s Stripe account we cancel their subscriptions and delete their customer record (or empty it where Stripe does not allow deletion; invoices already issued stay with Stripe as the tax record). If that step fails, we keep retrying and warn the studio after 24 hours. The deletion is reported as complete, and the member receives the confirmation e-mail, only once every step is done. If the member had opted out of or complained about the studio’s messages, we keep only a scrambled code made with a secret key from their e-mail address and phone number (a keyed hash, never the address or number itself), for that studio only, and use it only to make sure the studio never messages them again.

If you are a member and contact us, we will pass your request to your studio within 2 business days and help it respond. If the studio no longer exists or does not respond, write to privacidade@elastudio.app and we will help as far as the law allows.

12. Changes to this policy

We will post every new version here with its date. If a change is significant, we will tell studio owners and staff by e-mail at least 30 days before it takes effect. Earlier versions are available on request.

13. Language

This policy is available in English and Brazilian Portuguese, the two binding versions. For people and studios in Brazil, the Portuguese version prevails if the two differ; for everyone else, the English version prevails. Section 15 (Mexico) is part of this policy. We also publish a Spanish translation on elastudio.app/es for information only; it is not binding and does not prevail over the English or Portuguese version, unless a law that cannot be waived requires otherwise. elastudio does not accept studios in Quebec until a French version is available.

14. Contact

Privacy questions and requests: privacidade@elastudio.app. Everything else: support@elastudio.app. Support is provided in English and Brazilian Portuguese only, including for people who use elastudio or this website in Spanish. This does not apply to privacy requests: you can write to privacidade@elastudio.app in Spanish (section 15). Post: BRITO.AI (elastudio), 73 Watt Street, Guelph, Ontario N1E 6W6, Canada.

15. Additional information for Mexico

This section is for people in Mexico. It explains how this policy applies under Mexico’s Federal Law on the Protection of Personal Data Held by Private Parties (Ley Federal de Protección de Datos Personales en Posesión de los Particulares, LFPDPPP). It adds what Mexican law requires. If anything in this section differs from the rest of this policy, this section applies to people in Mexico. It does not limit any right that Mexican law gives you.

Controller. If you are a studio owner or staff member, or you visit elastudio.app, its help centre or our sign-in and sign-up pages at app.elastudio.app, the controller (responsable) of your personal data is Edilson Brito Bezerra Junior, operating as BRITO.AI, with his address at 73 Watt Street, Guelph, Ontario N1E 6W6, Canada (section 1). If you are a member of a studio, the studio is the controller and elastudio acts as its processor (encargado) (section 11). Requests about your data are handled by our privacy officer at privacidade@elastudio.app.

Data and purposes. The data we process and what we use it for are in section 2. The optional purposes are only these: the optional questions after sign-up (and counting, from those answers, how studios heard about us), analytics on elastudio.app and on our sign-in and sign-up pages at app.elastudio.app, the help assistant and marketing e-mails. You can refuse them at any time (see “How to limit the use of your data” below), and refusing changes nothing in your account. Every other purpose in section 2 is needed to provide elastudio and our website to you, for example: creating and managing your account and your studio, signing you in and keeping your account and our website secure (including server logs), showing the website in your language and currency, keeping records of your acceptance of our Terms and of your cookie and help assistant choices, handling support and bug reports, billing you and meeting legal obligations. As controller, we do not ask you for sensitive personal data; do not type it into the help assistant or your support messages.

Consent. We process your data with your consent, which you give when you use elastudio after we have made this policy available to you and you do not object, or without it where the law allows, for example where the data is needed for our contractual relationship with you or to meet a legal obligation. For analytics (on elastudio.app and at app.elastudio.app) and the help assistant, we ask for your express consent before starting. For marketing e-mails, see section 10.

Sharing with providers and third parties (remisiones and transferencias). The service providers in section 4 process your data only on our behalf and on our instructions, mainly in the United States (section 5). We share data with third parties that use it for their own purposes only in the cases in section 4: your studio, which sees the staff accounts of its own team; Google, only if you connect your own Google account; authorities, where the law requires it; a buyer or successor of elastudio, which must keep the promises in this policy; and, only if you accept analytics cookies, Microsoft, which may use its MUID identifier for its own services.

ARCO rights and withdrawal of consent. You can exercise your rights of access, rectification, cancellation and objection (ARCO rights), and withdraw your consent, by writing to privacidade@elastudio.app. You can write in Spanish. Give your name, an e-mail address for our reply, the right you want to exercise and the data it concerns, and anything that helps us find it. We may first need to confirm your identity, or that of your representative. We answer within the time limits set by the LFPDPPP, and exercising your rights is free (section 8).

How to limit the use of your data. You can refuse or withdraw analytics cookies in “Cookie settings” at the bottom of every page of elastudio.app and, separately, of the sign-in and sign-up pages at app.elastudio.app; withdraw your agreement to the help assistant with “Withdraw agreement”; and unsubscribe from marketing e-mails with the link in each e-mail or by writing to privacidade@elastudio.app; and ask us to stop using, and delete, your optional sign-up answers, or to stop contacting you about elastudio, by writing to privacidade@elastudio.app. The cookies and similar technologies we use, and how to turn them off, are in section 9 and in the Cookie notice.

Changes. We tell you about changes to this policy as described in section 12.

Authority. If you believe we did not handle your request properly, you can go to the Mexican authority for personal data held by private parties (since 2025, the Secretaría Anticorrupción y Buen Gobierno).