Who operates Tinyjolt
Tinyjolt is published under the name Ozeily, which determines the purposes of the processing described here. Contact us about privacy, account deletion or support at alban@ozeily.com. This policy covers tinyjolt.com and the Tinyjolt Music browser extension.
Your account and sign-in
We use your email address, account identifier and authentication information to create and secure your account and save your widgets. If you choose Google sign-in, Google shares your email address and basic profile information, such as your name and profile picture, with our authentication provider, Supabase. We do not request access to Gmail, Drive or your Google listening history.
Account processing is necessary to provide the service you request. Google sign-in is optional; you can use email instead. Resend delivers sign-in emails and processes the recipient address, email content and delivery events.
Google sign-in: data we receive and why
When you select Continue with Google, you choose a Google account and authorize Google to share your account identifier, email address and verification status, name, and profile-picture URL with Tinyjolt through Supabase Auth. We request only the openid, email and profile permissions needed to identify you. Tinyjolt never receives your Google password and does not request Gmail messages, contacts, Drive files, calendars, YouTube account data or listening history.
We use this Google identity information to create or identify your Tinyjolt account, authenticate your sign-in, maintain your session and associate your saved widgets with the correct account. The name and profile-picture URL may be stored in the authentication record even when they are not displayed in Tinyjolt. Signing in with Google does not connect a music service or allow us to read your music tabs; the browser extension requests those permissions separately.
Supabase processes and stores this information for Tinyjolt as our authentication provider. Vercel hosts the Tinyjolt server that verifies your session and serves your account pages. We do not send your Google profile information to your overlay or its viewers. Our application does not use Google authorization tokens to access other Google APIs after sign-in.
Google user data is used only to provide and secure the account features described in this policy. We do not sell it, use it for advertising or credit decisions, or use it to train generalized artificial-intelligence or machine-learning models. Any sharing is limited to providers needed to operate these features or disclosures required by law. Tinyjolt’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Music information and the extension
After you allow a music website and select a player, the extension reads the current track’s title, artist, artwork address, track identifier, duration, position and playback state. These details are sent to Tinyjolt to display your music widget and overlay. The extension does not record, capture or transmit audio.
Website permissions are optional and requested when you connect a site. The extension reads player metadata and the relevant player elements on the selected page. It uses eligible tab addresses and titles locally to help you choose a source. It does not collect your general browsing history or use unrelated page content for advertising.
Connection credentials, allowed source addresses and preferences are stored in the browser. The current music state is relayed through Cloudflare. It is replaced as playback changes; Tinyjolt does not build a listening-history feature. We also keep operational usage counters to enforce plan limits and maintain the service.
This processing provides the overlay you request. You can stop sharing by disconnecting the extension, closing the selected player, revoking site access in the browser or uninstalling the extension. Anyone who has your overlay URL can view its contents. If you include the overlay in a stream, your audience can see the displayed track information.
Settings, billing and security
We store widget settings and connection identifiers to provide your saved designs. When you use paid billing, Stripe handles payment details; Tinyjolt receives customer and subscription references, amounts and statuses. Full card numbers and security codes are not stored by Tinyjolt. These uses fulfil your contract and applicable accounting obligations.
Support messages and technical information, such as IP address, browser details, request errors and security logs, help us answer requests, diagnose incidents and prevent abuse. Our legal basis is our legitimate interest in running and securing the service, or the contract for account and billing support. Hosting country information selects the displayed currency without requiring precise location permission.
Providers and sharing
Vercel hosts the website and server functions. Supabase provides authentication and the database. Cloudflare delivers current music data to connected overlays. Resend delivers authentication emails. Stripe processes payments and subscriptions when used. Google provides optional sign-in, the fonts used on the website and, only if you accept analytics cookies, Google Analytics. Album artwork loads from music-provider image servers, which receive the image request and associated network information.
We do not sell personal data or use music information for targeted advertising. Data is shared with the providers needed to operate the functions above, with people to whom you share your overlay, or where legally required. We do not use Google account data for advertising or unrelated purposes.
These providers may process data outside your country, including the United States. Their data protection documents describe processing locations and transfer safeguards, such as contractual protections where applicable. Contact us for information about the safeguards applicable to your data; we do not promise EU-only processing.
Tinyjolt Music uses data obtained through Chrome permissions only to provide and secure the music-overlay features described here. This use follows the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not use this data for personalised advertising, creditworthiness or lending. Human access is limited to your specific consent for support, security investigations, legal obligations or anonymised internal operations.
How we protect account data
Tinyjolt uses HTTPS for communication between your browser, our website and the authentication service. Google sign-in uses an authorization-code flow with PKCE, which binds the return from Google to the browser that started the sign-in. Authentication cookies maintain your Tinyjolt session; signing out removes the local session.
The database checks account ownership before allowing access to saved widgets. Server credentials are kept outside the public website code. Access to account data is limited to operating the service, responding to a support request, investigating abuse or meeting a legal requirement. No service can guarantee absolute security; contact alban@ozeily.com if you suspect unauthorized account access.
Storage and retention
Authentication cookies keep you signed in, a language cookie remembers your preference, and extension storage keeps its connection and source settings. Tinyjolt installs no advertising trackers. If you accept in the cookie banner, Google Analytics sets _ga cookies (kept up to 13 months) to measure visits, the pages that lead to an install or a subscription, and purchases. Nothing is loaded if you decline, and you can change your choice at any time with the Cookies link at the bottom of each page. Deleting browser storage can sign you out and disconnect the extension.
Account details and saved widgets remain while your account is active. Request their deletion by emailing us from your account address. Current playback state is temporary and is cleared after disconnection or inactivity; connection settings remain until removed. Billing records needed for legal obligations or disputes may remain after account closure. Support and security records are retained for handling the request, preventing abuse and meeting applicable obligations. Provider backups follow their own deletion cycles.
Removing Google access and deleting your account
Google identity information stored in the Tinyjolt authentication record is kept while your account is active so that you can sign in again and retrieve your widgets. You can remove Tinyjolt’s access from your Google Account connections at any time. Removing access prevents future Google authorization under that connection; it does not itself delete information already stored in your Tinyjolt account or cancel an active subscription.
To delete your Tinyjolt account and its stored Google profile information, email alban@ozeily.com from the address associated with your account and request account deletion. We verify the request before deleting the authentication record and associated widgets and music-connection records. Information that must be retained for legal, billing, dispute or security purposes is limited to those purposes. Residual provider backups are removed according to the provider’s backup-retention cycle.
If you want to continue using Tinyjolt without Google, use the email sign-in option. Do not send us your Google password or a sign-in code when requesting support. Changes to how we handle Google user data will be reflected in this policy before the changed use begins; if a new use requires permission, we will ask for that permission.
Your choices and rights
Depending on applicable law, you can request access, correction, erasure, restriction and portability, and object to processing based on legitimate interests. You can withdraw optional website permissions or disconnect Google access. This does not undo processing already lawfully performed. Tinyjolt does not make automated decisions producing legal or similarly significant effects about you.
Email alban@ozeily.com with your request. We may check your identity proportionately. Under the GDPR, the usual response period is one month; a justified extension is possible for complex requests. You can complain to your local data protection authority, including the CNIL in France. We update the date above when this policy changes.