Privacy Policy — Estelle

Last updated: 2026-10-18

Who we are

Estelle is operated by Amitay (individual, based in the Netherlands), trading as Estelle and thebits.club ("we", "us", or "our"). We are the data controller for the personal data we use to operate Estelle. Contact us at [email protected].

This policy covers hiestelle.com, the Estelle iOS and Android apps, scouting and emailed results, accounts, subscriptions, notifications, public event and venue directories, and support. It applies to visitors, people requesting results without registering, anonymous app users, registered performers, subscribers, and people whose professional contact information appears in our research. Our Terms of Use explain the service agreement; this policy explains data use and is not a request for blanket consent.

What we collect and where it comes from

Account and profile information: your email, name, performer type, selected cities and their coordinates, account identifiers, preferences, and any website, social profile, phone number, or notes you provide. Some information is optional or comes from historical profile features. City coordinates describe your chosen performance area; they are not a record of your movements.
Authentication: Supabase processes passwords and authentication sessions. We do not store plain-text passwords. If you sign in with Apple or Google, we receive the provider identifier, email (which may be an Apple relay address), and any name the provider supplies. Anonymous app use can create a guest identifier and account before you provide an email.
Requests and opportunity activity: scouting requests, results links, saved or dismissed opportunities, interests, signup/reminder choices, calendar actions, manually added private events, and historical booking-request records. Private user-entered events are separate from our public event directory.
Subscriptions: identifiers linking your Estelle account with RevenueCat, purchase and transaction references, product and store information, subscription status, trial and renewal information, and entitlement dates. Web checkout also receives your email. Paddle, Apple, or Google Play collects payment and billing information for purchases through its channel; Estelle does not receive your full payment-card details.
Notifications: email preferences, push preferences and permission status, and a push notification device token (Apple Push Notification service on iOS, Firebase Cloud Messaging on Android) linked to your account when registered. Your device settings also control push delivery.
Technical and usage information: account, session and request identifiers; page paths; device/platform and browser information where available; actions such as searches, clicks, scroll depth, content views, purchases, and calendar exports; visit duration; referring domains and campaign parameters; and errors. Hosting, authentication, email, and other providers may process IP addresses and request information for delivery, operation, security, and troubleshooting.
Email information: email contents needed for delivery, delivery failures, complaints, and engagement events. Mailgun uses tracking images and links to report opens and clicks, as explained below.
Support and feedback: contact information, messages, attachments you choose to send through support channels, and information needed to investigate an issue.
Public-source information: venue and organizer names, professional contact names, email addresses, phone numbers, websites, social links, participation instructions, and source evidence from public websites, event calendars, directories, and social/event pages. Public availability does not remove an individual's data-protection rights.

Please provide only information needed for your use of Estelle. Do not submit passwords, financial credentials, confidential third-party material, or sensitive personal information such as health details or identification documents in profile notes, event descriptions, or ordinary feedback. If you provide another person's information, you must have an appropriate basis to do so.

Why we use your data and legal bases

Where EU or UK data-protection law applies, the purposes and legal bases are:

Purpose	Legal basis
Provide requested results, accounts, personalized scouting, saved/private events, subscriptions, and requested service notifications	Performance of a contract or steps you request before entering one (Article 6(1)(b))
Respond to support requests and feedback	Contract where necessary to provide your service; otherwise legitimate interests in answering requests and resolving issues (Article 6(1)(f))
Optional product announcements and optional new-event emails	Consent (Article 6(1)(a)); preferences and unsubscribe links let you withdraw it
Protect accounts, prevent fraud and abuse, diagnose failures, and maintain service reliability	Legitimate interests in protecting Estelle and its users (Article 6(1)(f))
Understand first-party product usage and improve the service	Legitimate interests in assessing and improving Estelle (Article 6(1)(f)), subject to the separate consent requirements for storage/access technologies explained below
Assess email delivery and limited open/click engagement	Legitimate interests in reliable delivery and evaluating communications (Article 6(1)(f)) where lawful; consent (Article 6(1)(a)) where required for engagement tracking. Legitimate interests do not replace required device-access consent
Research and present public performance opportunities and professional organizer contacts	Legitimate interests in making relevant public opportunities discoverable (Article 6(1)(f)), balanced against the rights of the people concerned
Keep required accounting records, respond to lawful requests, or meet other legal duties	Legal obligation (Article 6(1)(c))
Establish, exercise, or defend legal claims	Legitimate interests in protecting legal rights (Article 6(1)(f))

You can object to processing based on legitimate interests. Where we rely on consent, you may withdraw it without affecting earlier lawful processing. Providing information needed for a result request, account, or purchase is necessary for that feature; optional profile information is not required for every feature.

AI, search, and automated processing

Scout uses Google Gemini, OpenAI, Brave Search, and Google location services to research, check, organize, and rank opportunities. Requests include the selected city or area, city coordinates where needed, performer type, search queries, and public-source text and evidence. Public evidence may contain personal information about organizers. The service does not need your password or payment-card details for scouting.

Search providers receive queries, AI providers receive the material needed for their task, and websites we retrieve receive server requests. Provider processing and retention depend on the applicable service terms and configuration; this policy does not promise that every provider has zero retention or identical model-training practices. You can ask us about the providers and processing used for your request.

Automated matching can prioritize which opportunities you see and can produce mistakes or incomplete results. Scouting and ranking are not used to make solely automated decisions about you with legal or similarly significant effects within Article 22 GDPR. You decide what to pursue; organizers decide whether to accept you.

Sharing and subprocessors

The providers below receive the information needed for their role:

Supabase: database, authentication, backend functions, and related infrastructure. Privacy policy.
Deno: website/application hosting and request handling. Privacy policy.
Cloudflare: website traffic delivery, security, and protection of displayed email addresses. It processes connection information, including IP addresses and requests, when serving the website. Privacy policy.
Mailgun: emails, recipient details, delivery, and open/click tracking. Privacy policy.
Google: Gemini AI processing, Places city autocomplete on signup and Settings, geocoding and venue research, Google sign-in when chosen, and, for the Android app, Firebase Cloud Messaging push delivery, Google Play purchases, and city search through the device's location services. Google may receive search input and connection information directly when its browser features load. Privacy policy.
OpenAI: AI research and ranking inputs, including opportunity source material. Privacy policy.
Brave Search: scouting search queries and search results. Search API privacy policy.
RevenueCat: subscription management and entitlement checks using account identifiers and purchase information, including the web checkout integration. Privacy policy.
Paddle: web purchases as merchant of record, including checkout, billing, tax, fraud prevention, and subscription administration. Privacy policy.
Apple: App Store purchases, Apple sign-in, Maps city search, and Apple Push Notification service, when used. Privacy policy.
SupportRetriever: messages and contact details submitted through our linked support form, and connection information when its content loads. The form is hosted by that service; review its notices before submitting information.

Some providers process data on our behalf; others, including purchase resellers and sign-in providers for their own services, act as independent controllers. Their notices explain their own processing. We may also disclose relevant information to advisers or authorities where necessary for legal obligations, fraud investigations, or legal claims, or to a successor if the service is transferred, subject to applicable protections and notice requirements.

Public directories and results may include publicly sourced organizer contacts. Your account profile and private events are not published in those directories. Opening an organizer's website, sending an application yourself, using a calendar provider, or submitting an external form sends the information you choose to that third party under its own terms and privacy practices. Estelle does not automatically send your profile to venues as part of scouting.

International transfers

Providers and their infrastructure may process information outside the European Economic Area or the UK, including in the United States. The applicable transfer mechanism depends on the recipient and service: an adequacy decision, applicable Standard Contractual Clauses and supplementary measures, or other legally available safeguards. EU-US Data Privacy Framework coverage applies only where the relevant recipient is certified and the transfer is covered. UK transfers may require UK-specific safeguards.

Contact [email protected] to ask where your information is processed and request information about, or a copy of, the applicable transfer safeguards, with confidential material redacted where necessary.

Data retention and account deletion

Retention depends on the purpose, account activity, subscription status, and legal requirements. Different records are not all erased on the same schedule:

Accounts and activity: generally retained while needed to provide your service, unless you delete your account or inactivity cleanup applies. Cleanup is configured to identify unconfirmed profiles after 14 days of inactivity and confirmed profiles or anonymous app accounts after 30 days. Profiles with an active paid entitlement are excluded from that automatic cleanup. Eligibility and deletion are checked by scheduled jobs, so these periods are not a promise of deletion at an exact hour.
Application logs: the default cleanup period is 30 days, including email-engagement events recorded in those logs. Provider email, hosting, and authentication records have their own retention; the application-log period does not describe every provider's records.
Scouting evidence and public listings: source information, research history, and technical records may remain separately from your account to maintain and verify the opportunity catalog, resolve errors, or protect legal rights. We assess continued need according to those purposes, whether the information is current, and any correction or deletion request.
Billing, support, and legal records: retained as needed for purchases, disputes, statutory recordkeeping, and legal claims. Paddle, Apple, Google, and other providers may retain records independently under their own duties and notices.
Deletion: the account-deletion flow removes your profile, authentication account, private user-created events, and associated opportunity/booking activity, and removes account links from existing application logs. Removing an account link alone does not guarantee that every remaining record is anonymous. Necessary legal records and provider copies may remain; backup copies expire under the relevant backup cycle.

How to delete your account: on the website, use Settings. In the iOS app, use Settings. In the Android app, use More > Account > Delete my data. Without the app or website, email [email protected] from the address on your account (or include your account email) and ask us to delete your account; we will confirm when it is done. Deletion covers the data described above.

Deleting your account does not automatically cancel a Paddle, Apple, or Google Play subscription. Cancel with the provider you purchased through to stop renewal. You can also contact us about data held separately from your account.

Cookies and similar technologies

The website uses localStorage and sessionStorage for authentication sessions, signup drafts, session identifiers, and some feature preferences or purchase state. The app uses device storage for sessions and preferences. Authentication and storage needed for an action you request have a different purpose from usage measurement; not every identifier or storage operation is strictly necessary.

Our own analytics measure page and feature use, including clicks, scroll depth, referring domains, and campaign parameters. We do not use Google Analytics or PostHog, and we do not use these analytics for cross-context behavioral advertising.

Email tracking: emails sent through Mailgun include open-tracking images, and most also use tracked links; click tracking is disabled for some authentication links. Loading an image or following a tracked link can generate an engagement event. Email-client image blocking, caching, and privacy features can affect these measurements. Unsubscribing from optional emails stops those emails; it is not a separate control for tracking in required account messages.

Some storage/access technologies, including email pixels or tracked links, require prior consent under applicable electronic-communications law unless a specific exemption applies. A GDPR legitimate-interest basis, permission to send an email, push permission, or agreement to this policy does not itself supply that consent. We do not describe acceptance of these Terms or this policy as a tracking opt-in.

Google Places, the Android device's city lookup, and external checkout, sign-in, support, and calendar services may use their own technologies and receive connection data. Browser/device settings can block storage or remote images, though blocking essential storage may prevent features from working. Contact us if you have a question about tracking or want to exercise privacy rights.

Your rights and choices

Under applicable law, you may have rights to access your personal data, correct it, request erasure or restriction, receive portable data, object to processing, and withdraw consent. Objection to direct marketing is available at any time. Where processing is necessary for a legal obligation or claim, some information may need to be retained.

Update your profile and optional email preferences in Settings, or use unsubscribe links. Essential account, security, purchase, and requested-result messages may still be needed.
Manage push permissions in device settings and available in-app notification preferences.
Delete your account in Settings, or contact us to request erasure, access, export, correction, restriction, or objection.
If you are an organizer or contact included in our public-source research, ask us to explain the source, correct inaccurate information, or consider an objection or removal request. You do not need a performer account.

Send requests to [email protected]. We may request proportionate information to verify identity; do not send identity documents unless specifically requested through an appropriate channel. For GDPR requests, the normal response period is one month. Where legally permitted, complex or numerous requests may take up to two additional months, with an explanation within the first month. Requests are normally free, subject to the law's limited exceptions.

You may complain to the Autoriteit Persoonsgegevens in the Netherlands or another competent authority, including the authority where you live or work or where an alleged infringement occurred. You do not have to contact us first.

Security

We use measures such as encrypted connections, access controls, database row-level security, and restricted administrative access. Application logging is designed to avoid passwords, access tokens, and raw authentication headers. No service can guarantee absolute security. Keep account credentials and private results links confidential, and report suspected unauthorized access promptly.

Children

Estelle is intended for people aged 18 or older. If you believe a child has provided personal data, contact us so we can assess and address it, including deletion where appropriate.

Other regional rights

Applicable local laws may provide additional rights. Where California privacy law applies, these can include rights to know/access, correct, delete, and receive information about disclosures, and to exercise rights without unlawful discrimination. We do not sell account-holder personal information or share it for cross-context behavioral advertising. Publicly sourced professional contacts are used and displayed as described above. Contact us, including through an authorized representative where permitted, to exercise applicable rights or challenge our response. This policy does not assume that a particular business-size exemption applies.

Changes and contact

We will publish changes here with the date of the policy revision. Where required, material processing changes will be notified separately and any required consent obtained; posting a revised policy does not by itself authorize a new consent-based use. For questions, contact [email protected].