last updated: may 22, 2026
when you use the tilly website, join the waitlist, or sign into the chrome extension using firebase authentication, we may collect:
when you use the tilly chrome extension, your saved profile, preferences, memories, and reusable answers are stored locally in chrome extension storage on your device. tilly does not upload your full local profile as an account database.
when you trigger tilly on a page, the extension sends only the context needed to provide the form-filling feature. this may include form labels, field names, placeholders, options, current field values, page title, page url, optional screenshot context, microphone audio, transcripts, and ai prompts or responses related to the current task.
for paid access and usage limits, tilly may process an install identifier, firebase user id, account email, credit balance, usage reservations, stripe customer id, stripe subscription id, subscription status, and selected plan. payment card details are handled by stripe and are not stored by tilly.
we use your information to:
we do not sell your personal information. we do not use extension data for advertising. tilly does not automatically submit forms for you.
extension profile data is primarily stored locally in chrome extension storage on your device. website waitlist data is stored in google cloud firestore, managed through firebase. extension account sign-in is handled by firebase authentication. billing and usage metadata is stored in cloudflare d1 and stripe. data sent to tilly's backend is encrypted in transit.
we use the following third-party services:
these services process data under their own privacy policies, including google, cloudflare, openai, anthropic, and stripe.
you can clear local extension data in chrome or by removing the extension. you can request deletion of waitlist, billing metadata, or support records by contacting us at nabilbakour0@gmail.com. some billing records may be retained where required for legal, tax, fraud-prevention, or accounting reasons.
the website may use firebase authentication local storage and session cookies to manage sign-in state. google analytics (ga4) sets cookies (e.g. _ga, _ga_*) to distinguish unique visitors and track sessions. the chrome extension uses firebase authentication storage for sign-in state and chrome extension storage for local profile data, preferences, install id, onboarding status, and billing status. you can opt out of google analytics by installing the google analytics opt-out browser add-on.
we may update this policy from time to time. any changes will be reflected on this page with an updated date.
if you have any questions about this privacy policy, contact us at nabilbakour0@gmail.com.