Privacy notice
Updated 10 September 2026
EMILIA Score is operated by the EMILIA team. This notice covers emiliascore.com and its Score workspace. For privacy questions or requests, contact team@emiliaprotocol.ai.
What you give us
When you sign in, our authentication provider processes your email and sign-in information. Score uses your account identifier and email to identify your workspace. We store session and sign-in records so that you can use the service and sign out.
When you run an audition, we process your job description, policy, selected candidates and sample cases. Signed-in results are saved with the outputs, evaluation details, model information and reported usage. Anonymous reference results are returned to your browser without being saved as workspace auditions.
When you publish a listing, we store the submitted profile, definition, optional notes and publication decision. Names, descriptions, website links and declaration-analysis counts are public, including through the profile's shareable link. Raw definitions and optional notes are not included in public profiles. Your saved choices and permission plans are private workspace records.
Browser drafts and cookies
Your unsent job, policy, custom sample cases, shortlist and listing draft are stored in this tab's session storage so they can survive sign-in and reloads. Browser session restoration may preserve them. Clear them using “Clear drafts from this tab” in My work, or clear this site's browser data. Signing out alone does not clear an unsent draft.
Score uses essential cookies for sign-in and sessions. The application does not include advertising trackers or an advertising-cookie system. Our hosting and authentication providers also process request and security information to operate their services.
When a model provider receives your sample
Reference examples run deterministic code without a model-provider call. Hosted AI auditions send your job description, policy and sample cases to OpenAI only after you approve that run. The screen names the model candidates before submission. Do not include customer personal data, secrets, credentials or confidential business records.
We store the returned output and usage with your signed-in audition. Provider processing and retention are separate from your Score workspace. OpenAI describes its API handling in its API data controls. Deleting an audition from Score does not recall a request already processed by a provider.
Why we process information
We use this information to provide sign-in, show the listings you choose to publish, run and save auditions, record your choices, support export and deletion, answer support requests and protect the service from abuse. We use account-based and hashed network-based counters to enforce usage limits. Score does not sell personal information, sell ratings or use your audition content for advertising.
Services involved
- Vercel hosts the website and server routes.
- Supabase provides the database and authentication. Our configured email-delivery provider processes sign-in emails.
- OpenAI processes the hosted AI samples you explicitly approve. Reference samples and declaration scans do not use a model provider.
These services may process information in countries other than your own. Their service records, security logs and backups follow their applicable policies and our service arrangements. We do not promise that deleting a live Score record immediately removes all provider logs or backup copies.
Keeping, exporting and deleting records
Saved workspace records stay available until you delete them. You can export your workspace, delete individual listings or auditions, or delete all Score data from My work. Hiding a listing removes it from Explore while retaining your private copy. Copies previously viewed, downloaded or indexed elsewhere cannot be recalled by hiding or deleting a profile.
A saved selection keeps its own copy of the tested job, policy, sample cases and selected worker's outputs, checks and version details. Deleting the original audition does not delete this selected evidence. Cancelling a selection changes its status; it does not erase the record. You can review and download the private handoff yourself; Score does not automatically send it to a builder or customer.
Deleting all Score data removes your Score listings, auditions, selections and permission plans, and ends your Score sessions. It does not delete a shared EMILIA sign-in identity or records in other EMILIA products. Contact us for an identity-deletion request or a wider data request.
After a full Score-data deletion, a minimal hashed deletion marker remains to prevent in-flight requests from recreating deleted work. A fresh sign-in can create a new empty workspace; it cannot restore the deleted workspace. Usage-limit and abuse-prevention records are retained to prevent limit evasion. Expired sign-in records can remain until they are pruned or included in a full Score-data deletion. If you need information about retained security records, provider records or backups, contact us. We do not claim an automatic retention schedule that the service does not enforce.
Your choices and requests
You may contact us to request access, correction, export or deletion of your information, or to object to or restrict processing where applicable. You can stop future model-provider submissions by leaving the run-consent box unchecked. This does not undo completed processing. Depending on where you live, you may also have a right to complain to your privacy regulator. We may need to verify that a request concerns your account.
Use appropriate sample material
Score is intended for adults evaluating business tools. It is not intended for children or for storing sensitive customer, health or financial records. If you believe personal information was submitted in error, contact us so we can review the request.
Changes and contact
We will update this notice when the service's data practices change and show the updated date here. Questions, corrections and privacy requests can be sent to team@emiliaprotocol.ai.