A little clarity
about your data.
How the Servo website uses account and waitlist information.
Your Servo account
When you sign in with Google or GitHub, Supabase Auth manages the account and receives identity information supplied by your provider, such as your email, account identifier, and basic profile. Servo uses your verified identity to sign you in. Servo does not ask for your Google or GitHub password, or request access to your documents, repositories, or messages.
When you use email and password, Servo securely forwards those credentials to Supabase Auth to manage your account and verify sign-in. Passwords are not returned to page JavaScript or stored in the website repository. When email delivery is enabled, confirmation and password-reset messages are sent through our configured email provider, Amazon SES.
Account records remain in the authentication service until removed. Creating an account does not purchase a subscription or grant access to a product that has not launched.
Early-access updates
The waitlist is separate from your account. Joining it requires your email and consent to product updates. Servo stores your email, signup date, and consent to manage early access. An essential browser cookie lets you remove your signup from the browser you used to join.
Signups expire after 180 days. Expired entries stop being used immediately and are automatically deleted from AWS storage, usually within a few days. Use “Remove my signup” on the waitlist page to withdraw sooner. If you lose access to that browser, contact support@servoai.org or let the entry expire.
Questions or deletion requests
Contact support@servoai.org about your information or to request account deletion. Ownership may need to be verified before account records can be changed or removed.