This statement explains how we handle personal information when you use the free Reader Beta at reader.itrevolution.com and account.itrevolution.com, including the member AI connector when available. It applies from October 5, 2026. Version 2026-10-beta.
1 Who is responsible
IT Revolution Press, LLC, 4802 SW Scholls Ferry Road, Suite F, Portland, OR 97225, United States, operates the Reader and is responsible as controller for the processing described here. Contact support@itrevolution.com for privacy questions, requests, or complaints.
Our marketing website, events, and Video Library have separate privacy notices. This statement explains the data they supply to the Reader where relevant. Reader community integration with Slack and authorised partner-credential access may be offered during Beta, as described below. Separate participation in an event or community is not permission to disclose Reader account information.
2 The important points
We record passages you read and your progress, and we keep the notes and lists you create. We use Beta reading records to test reading measurement and the allocation of author payments. Beta reading does not itself generate author payments.
We do not sell personal information or disclose it for targeted advertising. Optional research analytics and promotional Beta emails require your separate choice. Declining them does not prevent you from reading.
Connecting an AI app sends the material it requests to that app. Reading history, notes, and lists are available to a connected app only for the categories you separately enable. Disconnecting prevents further authorised access after a short technical delay, but does not recall copies already received.
Deleting something from your screen is not always the same as removing its historical records. Section 8 explains retention and deletion. Contact us if you want those records erased.
3 Information we collect and its sources
Account and sign-in information. We receive your email address, account identifier, and any display name you provide. Firebase Authentication handles sign-in. Google or GitHub provides your verified email if you use that sign-in option. If phone sign-in is offered and you link a number, Firebase processes the number and fraud-prevention information; the Reader database does not store the number. Providing the information needed to authenticate you is necessary for account access.
Your reading and work. We store your reading position, saved and finished works, highlights, notes, private lists and paths, practice work, and settings. You choose what to enter. Do not include passwords, sensitive personal information, or confidential information about other people in notes or feedback unless you have authority and the feature is appropriate for it.
Reading measurement. While you are signed in, we record book or paper character ranges visible for at least three seconds, the work and chapter, reading mode, account and session identifiers, and receipt time. The Reader sends these records periodically and when you leave a page. Protected PDF access records include page number, time, and session information. Invalid reading records may be retained briefly to diagnose faults or suspected abuse. Reading free samples while signed out does not create account-linked passage records.
Optional analytics. If you opt in, we record account-linked feature events, active-reading intervals and daily totals, and library searches to understand use and improve the catalogue. Search records can include up to 100 characters of your query, the search area, result count, and selected result. Filters remove common patterns such as email addresses, phone numbers, and web addresses, but do not guarantee anonymity. We do not record searches of your private highlights and notes for this research. You can withdraw your analytics choice through support or the available privacy controls.
Technical information. Hosting and security systems process IP addresses, browser information, request times, requested pages, referrers, errors, and access alerts. Some existing operational logs may contain email addresses and older search URLs. Essential security processing continues if optional analytics are declined. We also record when an account first visits and the terms version accepted, acceptance time and route, and a keyed fingerprint derived from IP and browser information.
Messages and support. We keep feedback, relevant page or passage context, support correspondence, and email preferences. Email providers report delivery, bounces, and complaints. We do not track email opens. The limited Beta does not use account-linked email-click tracking. Essential sign-in and service notices are separate from optional promotional emails and requested reminders.
Other IT Revolution services. Where your existing entitlement or learning path requires it, we receive relevant title entitlements, Video Library membership status, viewing progress, saved courses, or certificates, matched by account email. These records come from the relevant IT Revolution service or legacy account records. They do not make your activity public. We do not collect payment-card information for this free Beta.
Optional profiles and sharing. Profiles start private. If you enable visibility, signed-in members can see your selected profile information, including name, photo, title, organisation, links, problems and focus areas. Separate choices control reading activity, finished books, and badges or certificates. Shared lists expose their title, description, steps, notes, creator name and participation counts to signed-in members and can be copied with attribution. Public badge pages can be viewed on the open web and indexed by search engines. The LinkedIn sharing control makes the badge public before opening LinkedIn for you to finish sharing.
Photos use public image URLs, including when your profile is private. Anyone with the URL may view or share the image. Upload only an image you are comfortable making accessible this way. New uploads are resized and stripped of embedded photo metadata. Removal and version retention are described in section 8.
The optional, skippable profile assessment collects your role, learning goals and challenges, role tenure, learning preferences, and relationship with IT Revolution. We keep current and historical answers within section 8’s limits. Answers are available to authorised staff for recommendations and service planning. Title and organisation can populate your profile; clearing assessment answers does not clear those profile fields. The assessment creates a private My starting point list and updates it only while you have not edited it. Public author and speaker information needs a separate notice and is not governed solely by this member statement.
4 Why we use information
We use account details and the reading content you save to provide access, synchronise your work, answer support requests, and deliver service messages. Where EU or UK data-protection law applies, our basis is performance of the agreement with you, to the extent that processing is necessary for the requested service.
We use limited reading measurement to test accurate author-payment allocation during Beta, and security information to protect accounts and licensed content. We rely on legitimate interests where applicable: accurate measurement, diagnosing defects, preventing unauthorised access, and defending legal claims. We assess necessity and the effect on you, and you may object. We do not treat an author contract as a statutory obligation to retain every reading event.
We use optional assessment answers with your consent to suggest learning material and inform service planning. You can skip or clear the assessment. We display and share contributions at your request through the visibility controls, using consent where required. Optional account-linked research analytics and promotional emails use your consent where applicable. Requested reminders use the basis appropriate to delivering that requested feature. Withdrawing consent does not invalidate earlier processing that was lawful, and does not end your core reading access.
We keep limited acceptance and dispute records to establish and defend legal rights. Where a specific law requires other records or disclosure, we rely on that legal obligation. We do not use this Beta to make solely automated decisions producing legal or similarly significant effects on you. Reading suggestions are not decisions about employment, credit, insurance, or eligibility for essential services.
5 Who receives information
Authorised IT Revolution staff use member information only for their work on the service, support, security, and the purposes described above. Staff support notifications may be sent to our internal Slack channels, including your email address and the feedback or request. Internal Slack processing is separate from an external member community or conference agent.
Google Cloud hosts the application, database, files, and logs. Google Firebase Authentication handles sign-in. Amazon Web Services SES sends service emails and reports delivery events. Slack supports internal team notifications and the optional member community. These providers receive the information needed for their roles, under the applicable arrangements with us. Sign-in providers can also process information for their own authentication and security purposes under their notices.
Your browser may contact Google for authentication, reCAPTCHA, or stored images, and the Video Library’s providers when you choose to open that separate service. The limited Beta self-hosts decorative fonts and scripts where practicable and does not load optional third-party assets merely to display a logo or thumbnail without an appropriate basis and any required permission. Our browser-storage notice identifies technologies actually enabled.
Member community and partner tools. Joining Slack can supply workspace and user identifiers, email, name, and photo URL through its authorisation flow; we do not retain the Slack access token. Slack also processes information under its own notice. Your community posts are visible to their channel audience. Before you use a community archive or conference AI relay, the feature notice must identify the content transmitted, recipients, purposes, retention, and controls. Partner credentials do not themselves authorise access to your Reader history, notes, or lists. A partner assistant may receive messages and identity information you supply through its interface under its disclosed arrangements; it is separate from your personally authorised Reader connector.
Authors receive aggregate Beta measurement or test reports, not member names, emails, account identifiers, session identifiers, or individual reading histories. Any later author-audit arrangement involving personal information requires its own review and disclosure before introduction.
Connected AI apps receive the content and permitted account information described in section 7. We may disclose information when legally required, to respond to an immediate safety threat, or to establish or defend rights, only where permitted by applicable law. Requests for protected reading records receive a specific legal review. A business successor may receive relevant information subject to applicable law and notice of material changes.
6 Cookies and information on your device
The Reader uses cookies and browser storage for sign-in, security, requested reading preferences, reading position, and a local copy of notes. Some sign-in cookies operate across Reader, account pages, and the Video Library. The principal Reader sign-in cookie lasts up to 30 days; a Video Library session cookie may last up to five days. Preference storage may last up to one year where permitted, or until you clear it.
We use nonessential storage or device access only after any required consent, unless a specific legal exception applies and its conditions are met. Optional consent can be refused or withdrawn without losing essential reading access. A first-party label does not by itself make a technology necessary. The notice available through Terms and privacy identifies active technologies, purposes, providers, durations, and controls.
Signing out is intended to end Reader access, but local copies may remain on a device. On a shared device, clear Reader site data and close the browser after signing out; we cannot erase material you separately downloaded or copied. If you suspect another person can access your account or notes, contact support promptly.
We do not use sale or targeted-advertising processing in this Beta. We honour legally applicable opt-out preference signals for covered processing. A browser Do Not Track signal does not turn off necessary authentication or security records; use our privacy controls or contact us about optional analytics.
7 Connecting your own AI app
The connector, using Model Context Protocol or MCP, lets an eligible invited member authorise an external AI app to search and retrieve permitted excerpts. It does not grant access to the entire library or permission to train a model. The User Agreement explains content restrictions.
When you connect, we retain the app’s registered name and addresses, connection and last-use times, authorisation and revocation records, and the accepted terms version. Access codes and tokens are short-lived; renewal authorisation can last up to 30 days unless revoked earlier. Disconnecting in Settings revokes authorisation, but cached authorisation can allow requests for up to 60 seconds afterwards. It does not delete copies already received by the app.
For requests, we log the tool, result status, duration, and credential type. Passage-delivery receipts identify your account, works, passage locations, and times, rather than the passage text. These receipts are not currently used to calculate payments. We do not log connector questions, search words, or AI answers as part of this request logging, and do not receive your full conversation merely because you connect an app.
Reading history, lists and paths, and notes and highlights are off by default for AI access. Each category requires your separate authorisation. Your app can receive that category after you enable it, and the access is recorded in your activity. Disconnect the app or disable the category to stop future access.
We transmit the requested material to your chosen app on your instruction. Its provider handles the received information under its own terms and privacy notice. Review its retention and training settings before connecting. Do not use the connector with a provider configuration that trains or fine-tunes models on retrieved protected content. We cannot promise that disconnecting removes information held by that provider. Ask it directly to exercise rights over its copies.
8 Retention and deletion
The following are the retention limits for this Beta, except where a specific legal obligation or a documented, necessary dispute or security hold requires a limited extension. We restrict held records to that purpose, review the hold, and delete or anonymise them when it ends.
Account information, current assessment answers, profile fields, and your private or shared work are kept while the account remains active, unless you remove them earlier. Replaced or cleared assessment answers are removed within 30 days. Removing assessment answers does not remove separately saved profile fields or an edited starting-point list; you can remove those separately. After a verified closure or valid erasure request, we normally remove personal content and identifiers from active Reader systems within 30 days, subject to the applicable legal deadline and lawful exceptions. If the Beta ends and you do not choose continued access under new terms, we close the Beta-only account after 30 days and apply that deletion process. Closing a Reader account does not automatically close a separate event or Video Library account; we coordinate your request if it includes them.
Raw Beta reading measurement, rejected events, optional search and engagement research, connector receipts, support-notification copies, and email-delivery records are retained for no more than 90 days. These maximum periods do not delay a valid request requiring earlier erasure. Support cases are kept for up to 12 months after resolution. Revoked or expired connector grants are removed within 30 days unless a limited security record is needed. Expired sign-in codes are made unusable immediately and their redemption records are removed within 30 days.
Security and operational logs are retained for up to 90 days. Pre-Beta legacy logs and histories are reviewed and brought within this schedule before the Beta opens. Records evidencing agreement and material disputes are retained for up to three years after the relationship ends, unless a different period is legally required; they exclude note text and detailed reading history.
Removing a note or list in the interface may initially hide it while historical copies await erasure. Historical content and replaced or removed profile images are removed within 30 days of deletion. Turning off sharing ends future access through that sharing route; it does not automatically remove copies others already made. We handle erasure requests for controlled copies and notify recipients where the law requires, but cannot guarantee recall of independent copies or search-engine caches. Database backups expire within seven days; deleted file versions are purged within 30 days. During this interval, deleted data is unavailable for ordinary use, and restoration procedures reapply deletions. Material already lawfully downloaded or received by independent third parties is not automatically recalled.
We may keep genuinely anonymous statistics. Removing a name or replacing it with an account code is not, by itself, anonymization. We retain only the minimum suppression information necessary to honour an unsubscribe or prevent prohibited contact.
9 Where information is processed
Reader application data, databases, files, and backups are hosted principally in the United States using Google Cloud and Firebase. The connector also operates in the United States. Email delivery uses AWS in the United States. Support providers and the AI app you select may process information in other locations under their arrangements.
For EU or UK data subject to transfer restrictions, you can request information about, and copies of, applicable safeguards at support@itrevolution.com. We do not claim that IT Revolution itself is certified under a data privacy framework unless that certification is current and applicable.
10 Your choices and rights
Contact support@itrevolution.com to request access, correction, deletion, a portable copy, or review of how we use your information. Where applicable, you can restrict processing, object to legitimate-interest processing, withdraw consent, obtain required information about recipients, or opt out of sale, targeted advertising, or qualifying profiling. We do not carry out those sale or targeted-advertising activities in this Beta. We do not discriminate against you for exercising protected rights.
We verify requests proportionately and may ask for information needed to identify the account or your authority. Do not send identity documents unless requested through an appropriate channel. An authorised agent may act where the law allows, subject to suitable proof of authority and verification.
We respond within the deadline that applies to your request: ordinarily one month under EU or UK data-protection law, and ordinarily 45 days for applicable Oregon and other US state requests. If the law allows an extension, we explain it within the required period. We explain any refusal, applicable exception, and review route. Requests are normally free; we charge or refuse only where the law permits and explain why.
If you disagree with our response, reply with “Privacy appeal” or “Privacy complaint.” We review it and respond within the applicable period, including within 45 days for an Oregon statutory appeal. You may complain to Oregon DOJ at doj.state.or.us, the UK Information Commissioner at ico.org.uk, your EU supervisory authority, or another competent regulator. You do not have to contact us first where the law permits a direct complaint. EU complaints may be made where you live, work, or believe an infringement occurred.
11 Security and age eligibility
We use access controls, encrypted connections, and other safeguards appropriate to the information and service. We limit staff access by role and use security records to investigate abuse. No service is perfectly secure. We assess incidents and notify affected people and authorities when required by law.
Beta accounts are for people aged 18 or over. If you believe an under-18 user has supplied information, contact support so we can restrict the account, investigate, and remove information as appropriate under applicable law.
12 Changes and contact
We publish the effective date and version of this statement. We notify members before material changes where practicable and before a new use requiring notice or consent. Reviewing this statement does not constitute consent to optional processing. We obtain separate consent where required.
Privacy requests and questions: support@itrevolution.com. Postal address: the entity and address in section 1.