Privacy Policy
Last updated: 9 November 2026
Unrol is operated by YARKM Professionals Private Limited (“YARKM”, “we”), Andhra Pradesh, India. YARKM is the controller of the account data described below. Learn more at yarkm.com.
You accept this policy and our Terms when you sign in — the point at which your Unrol account is created. You can withdraw that consent at any time by deleting your account.
Signing in
You can sign in with Google, with X, or with your email address. Each method gives Unrol only what it needs to create your account and sign you in:
- Google: your name, email address, profile picture, and Google account identifier. Unrol requests only the basic sign-in permissions (
openid,email, andprofile) and never asks for access to Gmail, Google Drive, Contacts, Calendar, or any other Google data. - X: your X username, display name, profile picture, X account identifier, and the email address confirmed on your X account (when X shares it). Signing in with X does not give Unrol access to your private X account.
- Email: the email address you enter. We email you a one-time sign-in link and code; there is no password.
How we use Google user data
If you sign in with Google, Unrol receives the Google account information listed above and nothing else. We use it only to create your Unrol account, sign you in, and show your name and picture in your account. It is stored with your account in Supabase Auth (our authentication provider, in the European Union).
- We do not sell Google user data or use it for advertising.
- We do not share it with anyone except the service providers that run Unrol on our behalf (listed under “Where data is processed”), or when required by law.
- We do not use it to train or improve artificial intelligence or machine learning models.
- Deleting your Unrol account deletes it. You can also remove Unrol’s access at any time from your Google Account’s third-party connections page.
Unrol’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What we store
- Account: your email and basic profile (such as display name and avatar) from the sign-in provider you choose. Authentication is handled by Supabase Auth; Unrol does not store your password.
- Your library: the threads you save and the individual X posts you bookmark in Unrol, linked to your account and private to you. Unrol bookmarks are not your X bookmarks; Unrol never reads those.
- Ingestion records: when you unroll a thread, a job record is kept so you can track its status.
- Public thread content: the public X posts you unroll are stored so Unrol can display and search them. This content is public on X.
- Author subscriptions and notifications: the authors you choose to subscribe to, and the in-app “new thread” notifications you receive (created when someone unrolls a new thread by an author you subscribe to), linked to your account and private to you. Subscribing does not connect to your X account.
- Automation rules and history: the automation rules you create (their conditions, such as author, keywords, or read time, and the collection they file into) and a history of when a rule filed a thread (automation runs). Both are linked to your account and private to you. A rule on an author you subscribe to can also file a new thread that another user unrolls, but only ever into your own collections. Rules do not send notifications.
- Auto-save on unroll: every thread you unroll is automatically saved to your library, so it is stored with your account and private to you. You can remove it from your library at any time.
- Display preferences: your theme, reader settings (font, size, line spacing, and reading view), and Library display settings (sort order and the view for each Library section), stored in Unrol’s own database so they sync across your devices when you are signed in. They are linked to your account and private to you. Signed out, these preferences stay only in your browser.
Technical data
Your signed-in session is kept in your browser’s local storage so you stay logged in. Unrol does not use advertising or cross-site tracking cookies. Servers keep operational logs (with request identifiers and timings) to run and debug the service; secrets and tokens are never logged.
Diagnostics and error reports
To keep Unrol working, we collect diagnostic data about how the service runs. We use it only to operate, debug, and secure Unrol, not for advertising or to profile you.
- Operational logs: timestamps, request and job identifiers, the path requested (without its query string), status codes, timings, error codes, and thread identifiers.
- Metrics: totals and timings such as request counts, error rates, and job outcomes, plus server health such as CPU, memory, and disk use. Metrics are not linked to individual users.
- Error reports: when something fails on our servers, the error message and stack trace, the app version, and the request method and URL (without its query string). Reports leave out request bodies, cookies, request headers, and your account details. An error message can occasionally include details of what was being processed, such as a thread identifier.
Unrol’s web pages do not run error-reporting or analytics scripts for this; the data comes only from our servers.
Where data is processed
Account and thread data are stored in Supabase (PostgreSQL) and cached in Redis, in the European Union. Public thread content is retrieved server-side through the official X API. Sign-in emails (magic link and passcode) are sent through Zoho ZeptoMail. The application is hosted on Hetzner (Germany), with Cloudflare providing DNS and edge delivery. Diagnostic data is kept on our own monitoring server at Hetzner (Germany) and is not sent to a third-party analytics or error-tracking service. Only our operators can access it, and alerts about errors may be emailed to them through Zoho ZeptoMail.
Images, videos, and GIFs in threads and bookmarks are not copied to our servers: your browser loads them directly from X’s content servers (twimg.com), so X receives the request, including your IP address and browser details, when you view them. A video is only downloaded when you press play.
Because this media stays on X, whether it can be shown is up to X, not us. If X deletes or restricts a post, removes a file, or changes how its media can be accessed, the image or video may stop loading in Unrol and show as “Media unavailable”. We don’t control this and can’t restore media that X no longer serves.
What we do not do
Unrol does not sell your personal data, does not show advertising, and does not track you across other sites. Signing in with X does not give Unrol access to your private X account (bookmarks, timeline, direct messages, or similar).
Security
Traffic to Unrol is served over HTTPS/TLS. Access to stored data is restricted, and per-user data is isolated by database access controls. No method of storage or transmission is completely secure, but we take reasonable measures to protect your data.
Retention
Your account, library, author subscriptions, notifications, automation rules, and automation history are kept until you delete your account; they have no separate expiry. Diagnostic data expires on its own schedule: logs and metrics after 30 days, and error reports after 90 days. Deleting your account does not remove it sooner. Public thread content is retained independently of any single account (see below).
Your rights and choices
You can edit your profile and remove saved threads and bookmarks from your library at any time. You can delete your account from your account settings; this removes your account, profile, saved library, display preferences, author subscriptions, notifications, automation rules, and automation history. You can also delete individual rules, or clear your automation history, from the Automations page at any time. Public thread content already stored in Unrol is public X content and may be retained independently of any individual account. For access to, correction of, or questions about your data, email [email protected].
Children
Unrol is not directed to children under 13, and we do not knowingly collect data from them. If you believe a child has provided us data, contact us and we will remove it.
Changes
This policy may be updated as Unrol evolves. We will update the date above when we do.
Contact
Questions about privacy? Email [email protected].