Privacy Policy for Revision History
Effective Date: July 23, 2026
Introduction and Overview
TabWrite, LLC, operating as Revision History ("Revision History," "we," "our" or "us") respects your privacy and is committed to protecting it through our compliance with this Privacy Policy.
This Privacy Policy describes how we collect, use and share information about you as well as your rights and choices about such collection, use and sharing, and applies to this website as well as the services offered by Revision History.
Please read this Privacy Policy carefully to understand our policies and practices regarding your information and how we will treat it. If you do not agree with our policies and practices, your choice is not to use our website or our services. By accessing our website or using our services, you agree to this Privacy Policy.
This Privacy Policy may change from time to time (see Changes to this Privacy Policy). Your continued use of our website or services after we make changes is deemed to be acceptance of those changes, so please check this Privacy Policy periodically for updates. If you have any questions about our privacy practices, please contact us as set forth in the Contact Us section below.
Note regarding Byline: Byline by Revision History is a separate, school-managed, student-facing Chrome extension that is installed separately on the student side and, unlike Revision History, does collect Student Data (including student writing content sent to an AI subprocessor to generate coaching responses). Byline is licensed exclusively through Schools under a signed Student Data Privacy Agreement (DPA). Section 3 of this policy describes the Student Data that Byline collects and how it is used. The terms of each signed DPA govern TabWrite's handling of Student Data for that School and supersede this policy where there is a conflict. To request a DPA, contact info@revisionhistory.com.
1. Information We Collect
Information You Provide
When you create an account with Revision History, we collect your email address and name at sign-up. Additional information may be collected when you contact our support team, send us emails, participate in surveys, or communicate with us in other ways.
Information for Plus Subscribers
For Plus subscribers, the limited information we collect includes:
- Email address for account identification and communication
- A randomly generated user ID to authenticate your subscription across devices
- Basic subscription information (subscription type, renewal dates)
2. What We Do NOT Collect
Revision History is designed with privacy at its core. The Revision History teacher extension analyzes documents entirely locally within your browser. We do not collect, store, transmit, or have access to:
- Student writing or document content
- The text within documents you analyze
- Document metadata (such as revision history, timestamps, or edit counts)
- Any information about the documents themselves
Byline, our separate school-managed, student-facing tool, does collect Student Data when enabled by a school, as described in Section 3 below.
3. Byline (Student Tool): Data We Collect and How We Use It
Byline by Revision History ("Byline") is a separate, school-managed, student-facing Chrome extension that provides students with guardrailed AI writing coaching in Google Docs and provides teachers with visibility into students' writing process and AI use. Byline is licensed exclusively to schools and school districts under separate agreements, including a Student Data Privacy Agreement (DPA), and is deployed and activated by the school. Individuals cannot sign up for Byline directly.
When Byline is enabled by a school, we collect and process the following Student Data on the school's behalf:
- Student writing content: the text of the student's Google Doc at the time of a coaching request, used solely to generate a relevant coaching response
- AI prompt interactions: the prompt type or feedback request the student selects, any text the student has highlighted at the time of the request and the AI-generated coaching responses
- Browsing metadata: websites visited and browser extensions active while Byline is active, collected to provide writing session context and authenticity signals to teachers through the Revision History dashboard
- Writing session data: word counts, document activity timing and session metadata
- Student identifiers: student name, school email address and school-managed Google account identifiers
- Usage and technical data: session timestamps, feature usage events, extension usage logs, internal document and session identifiers, IP address, browser, device and operating system information, and error and security logs
How we use Byline data: We use Student Data collected through Byline solely to provide the Byline services to the school, including generating AI coaching responses, giving teachers and school administrators visibility into students' writing process and AI use, and maintaining the security and functionality of the services. Student writing content and prompt interactions are processed through our infrastructure provider (Supabase) and transmitted to our AI subprocessor (Google Cloud Vertex AI) solely to generate coaching responses. We also use PostHog as a product-analytics subprocessor to process Byline usage and technical data (such as feature usage events, device and browser information, and IP addresses) to help us maintain and improve the services; we do not send student writing content to PostHog. Student Data is not used to train or improve our or any third party's general-purpose AI models.
What we do not do: We do not sell Student Data, do not use Student Data for targeted advertising and do not use Student Data for any commercial purpose unrelated to providing the services to the school.
School control; parents and students: The school controls Student Data collected through Byline. Each school's signed DPA governs our handling of Student Data for that school and supersedes this policy where there is a conflict. Parents, guardians and eligible students who wish to access, correct or delete Student Data should contact their school; we will support the school in responding to those requests.
Retention: By default, Byline AI coaching records and associated document context are retained for up to 12 months (or any shorter period configured by the school) and are then deleted or de-identified, subject to the school's signed DPA and applicable law.
4. How We Use Your Information
We use the collected information to:
- Operate, maintain, enhance, and provide all features of Revision History.
- Communicate with you about your account and respond to inquiries.
- Improve the app's functionality and appearance through analytics.
- Develop and improve our educational products and services.
How We Use Plus Subscriber Information
- To authenticate your access to Plus features
- To manage your subscription status
- To communicate important information about your account
- To provide customer support
- To process refunds when applicable
5. How We Share Your Data
We prioritize your privacy and share your personal information only as necessary for providing our service and in the following situations:
Within TabWrite, LLC: We may share information with other companies under the TabWrite, LLC umbrella, including subsidiaries and the parent company. These entities use your data as outlined in this Privacy Policy.
Merger or Sale: In the event of a merger, acquisition, bankruptcy, change of control, or sale of our assets, your personal data may be transferred, but we will strive to enforce privacy terms similar to those in this policy.
Other Legal Reasons: We may disclose personal data if required to comply with the law, legal processes, or government requests. We may also disclose data to protect our rights, property, or the safety of our users or the public, or to address fraud or security issues.
Payment Processing:
We use Stripe as our payment processor for Plus subscriptions. When you subscribe to our Plus tier:
- Your payment information is collected and processed directly by Stripe
- Revision History does not have access to your payment card details at any point
- We may store only the minimal information necessary to verify your subscription status, such as subscription status
- For information about how Stripe handles your payment data, please refer to Stripe's Privacy Policy at https://stripe.com/privacy
6. Third-Party Services and Data Collection
We use certain third-party services to help operate and improve our service:
- Google Analytics: Used within our Chrome extension to help us improve Revision History. Google Analytics (not Revision History itself) may collect certain data including:
- IP addresses and approximate location for metrics reporting
- Features you use and time spent on the app
- Device information such as device type, operating system, and language preferences
- PostHog: Used within our Chrome extensions (including Byline) to provide product analytics that help us understand how our services are used and to improve them. PostHog may collect usage events, device and browser information and IP addresses. For Byline, PostHog processes Student Data as a subprocessor on the school's behalf, as described in Section 3.
- Stripe: Handles all payment processing for Plus subscriptions. Stripe receives your payment card details, email address, and subscription information directly. Revision History does not have access to your payment card details at any point.
- Supabase: Provides secure database infrastructure to store minimal account information like email addresses and subscription status. All data is encrypted and stored according to industry security standards.
- Google Cloud Vertex AI: Used only for Byline. Student writing content and prompt interactions are transmitted to Google Cloud Vertex AI solely to generate AI coaching responses, as described in Section 3. Google processes this data under Google's Cloud Data Processing Addendum and does not use it to train or improve Google's AI models.
- Brevo: Handles transactional and marketing email delivery on our behalf. Brevo receives your email address and name in order to send account-related and product communications. For information about how Brevo handles your data, please refer to Brevo's Privacy Policy at https://www.brevo.com/legal/privacypolicy/.
- Microsoft Clarity: Used on our website to provide session recording and heatmap analytics, helping us understand how users interact with our site and improve the user experience. Clarity may collect anonymized interaction data including mouse movements, clicks, scrolls, page URLs visited, IP address, browser type, and device information. Microsoft Clarity is not loaded for visitors from the European Union, European Economic Area, or United Kingdom.
- Meta Pixel (Facebook): Used on our marketing website to measure the effectiveness of our advertising campaigns. This is not used within the Chrome extension. Meta may collect page URLs visited, IP address, browser information, and device identifiers. Meta Pixel is not loaded for visitors from the European Union, European Economic Area, or United Kingdom.
These third-party services have their own privacy policies governing how they handle user data. We encourage you to review these policies.
7. Cookies and Tracking Technologies
Cookies We Use
Revision History uses the following cookies and tracking technologies on our website (revisionhistory.com). The cookies listed below are used only on our website. Our Chrome extensions do not use advertising or cross-site tracking cookies; they use limited first-party product analytics (Google Analytics and PostHog) to help us improve the extensions, as described in Section 3 and Section 6.
| Cookie / Technology | Type | Purpose | Duration |
|---|---|---|---|
| Supabase Auth | Essential | Manages user login sessions and authentication | Session |
| Stripe session cookie | Essential | Manages payment session state for Plus subscribers | Session |
| Google Analytics (_ga) | Analytics | Distinguishes unique users for usage reporting | 2 years |
| Google Analytics (_gid) | Analytics | Distinguishes unique users for usage reporting | 24 hours |
| Google Analytics (_gat) | Analytics | Throttles request rate | 1 minute |
| Microsoft Clarity (_clck, _clsk) | Analytics (non-EU/EEA/UK only) | Session recording and heatmaps to improve user experience. Not loaded for EU/EEA/UK visitors. | 1 year / Session |
| Meta Pixel (_fbp, _fbc) | Advertising (non-EU/EEA/UK only) | Measures effectiveness of advertising campaigns. Not loaded for EU/EEA/UK visitors. | 90 days |
| Ad attribution (rh_ad_params — localStorage) | Advertising (non-EU/EEA/UK only) | Stores ad campaign identifiers in browser localStorage so we can attribute extension sign-ups to the campaign that brought you to our site. The specific identifiers stored are listed in the "Tracking for Advertising" section below. Not stored for EU/EEA/UK visitors. | 90 days |
Regional Exclusions for EU/EEA/UK Visitors
To support compliance with the General Data Protection Regulation (GDPR) and UK GDPR, Revision History automatically disables Microsoft Clarity, the Meta Pixel, and ad campaign attribution storage for visitors whose requests originate from the European Union, the European Economic Area, or the United Kingdom. Visitors from these regions are detected at the edge via geolocation headers, and the associated scripts and storage writes are not delivered to their browsers.
Tracking for Advertising
Revision History uses the Meta Pixel on our marketing website (revisionhistory.com) to measure the effectiveness of our advertising campaigns. The Meta Pixel is not loaded for visitors from the EU/EEA/UK and is not used within the Chrome extension itself.
We also store ad campaign identifiers in your browser's localStorage when you arrive at our site from a paid advertisement. The specific identifiers stored are: UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content), Google click and campaign identifiers (gclid, gbraid, wbraid, dclid, gad_source, gad_campaignid), the Facebook click identifier (fbclid), and the Microsoft click identifier (msclkid). This lets us understand which campaigns drive extension installs. These identifiers stay on your device for up to 90 days, are not collected for visitors from the EU/EEA/UK, and you can clear them at any time by clearing your browser's site data for revisionhistory.com.
You can opt out of interest-based advertising from Facebook by visiting your Facebook Ad Preferences. You can also opt out of interest-based advertising from many companies through the Digital Advertising Alliance (DAA) opt-out page.
Managing Cookies
You may control cookies through your browser settings. Disabling analytics and advertising cookies will not affect your ability to use Revision History's core features. Disabling essential cookies (Supabase Auth, Stripe) may affect your ability to sign in or complete Plus subscription purchases.
You can also opt out of specific analytics and advertising services directly:
- Google Analytics Opt-out Browser Add-on
- Microsoft Clarity Privacy Settings (you may also block Clarity by disabling third-party cookies or using a content blocker)
- Facebook Ad Preferences
- Digital Advertising Alliance (DAA) Opt-out
8. Marketing, Advertising, and Email Communications
We may send you emails about Revision History, our products, or services we think you might find interesting. You can opt-out by clicking the unsubscribe link in these emails. Revision History does not engage in targeted advertising within the app. However, we may conduct interest-based advertising outside the app using third-party advertising companies.
9. Access, Update, or Delete Your Information
Contact us at info@revisionhistory.com to update or delete your personal information. Certain data may be retained for operational or legal reasons. We may also retain de-identified or aggregated data that can't reasonably identify individuals.
Retention of Plus Subscriber Data:
You may request deletion of your account information by contacting info@revisionhistory.com.
10. Our Approach to Data Security
We employ physical, managerial, and technical safeguards to protect your data. While no system is impenetrable, we strive to maintain the integrity and security of your information.
Breach Response Protocol
TabWrite, LLC maintains a formal breach response protocol that includes:
- Containment: Immediate isolation of affected systems, revocation of compromised credentials, and temporary suspension of affected services if necessary to prevent further exposure.
- Investigation: Root cause analysis to determine how the breach occurred and assessment of the scope and type of data potentially affected.
- Notification: In the event of a data or security breach involving personal information of teachers or other account holders, we will directly notify affected users via email within 72 hours of confirming the breach, regardless of whether such notification is legally mandated. Notification includes what happened, what data was involved, and steps users can take. For Student Data processed on behalf of a school under a signed DPA, we will notify the affected school within 72 hours of confirming the breach, and the school will control notices to affected students, parents and guardians, consistent with the DPA and applicable law. We will also notify relevant regulatory authorities as required by applicable law.
- Remediation: Implementation of security fixes to address the vulnerability, forced password resets for affected accounts if applicable, and post-incident review to update security practices and prevent recurrence.
11. Children's Privacy
The Revision History teacher extension is intended for use by educators and schools and is not intended for use by children under 18. We do not store any data related to the content of student writing through the teacher extension. If you are under 18, you must have permission from a parent/guardian or teacher before using our service. If you are a parent or guardian and believe that your child has provided us with personal information without your consent, please contact us at info@revisionhistory.com. We take children's privacy very seriously and will take steps to remove such information from our servers promptly. We reserve the right to suspend or delete accounts that we become aware were created by users under 18 without appropriate permission.
Byline is different: it is a student-facing tool that may be used by students under 18, including students under 13, but only through a school-managed deployment under a signed DPA. Where the Children's Online Privacy Protection Act (COPPA) applies, we rely on the school to provide consent on behalf of parents for the collection of students' personal information for school-authorized educational purposes, consistent with Federal Trade Commission guidance. We use that information only to provide the Byline services to the school and for no other commercial purpose. Parents and guardians with questions about Byline, or who wish to review or delete their child's information, should contact their school, and we will support the school in responding.
For teachers and educational institutions using Revision History with students under 18, it is your responsibility to obtain appropriate parental consent as required by applicable laws, including the Children's Online Privacy Protection Act (COPPA) in the United States.
12. School Use
Revision History is available for educational use by teachers in schools. We follow best practices to protect student data privacy. Teachers and schools are responsible for managing student accounts and complying with applicable privacy laws. Schools that wish to deploy Byline for students must enter into separate agreements with us, including a DPA; see Section 3.
13. International Visitors
Revision History is operated on servers in the United States. By using our app from regions with different data laws, you agree to data transfer to the U.S. for contract performance and other specified purposes.
14. European Union Data Protection
We adhere to GDPR principles for personal data processing and provide rights to EU residents regarding their data.
15. Links to Other Sites
Our app may contain links to other websites. Please consult their respective privacy policies, as we cannot control their activities.
16. Extension Permissions
Our extension requires certain permissions to function properly. These permissions are used solely for the purpose of providing our document analysis service and, for Plus users, managing subscription status. Byline requires additional permissions in order to provide AI coaching and writing session visibility, as described in Section 3.
17. Disclaimer of Accuracy
Revision History provides tools to analyze document revision history and other document-related information. While we strive to provide accurate and reliable information, we do not guarantee the complete accuracy, reliability, or timeliness of the information provided by our extension. The information provided by Revision History, including document revision history and analysis, should not be considered definitive evidence for legal, academic, or disciplinary proceedings. Users should verify any critical information through other means before taking any action based on information provided by Revision History.
18. Changes and Updates to This Privacy Policy
We may modify this Privacy Policy, and significant changes — including changes to the third-party services we use or how data is shared with them — will be communicated to registered users via email at least 30 days before taking effect. Changes will also be posted on our website. Any new third-party services will be held to the same data sharing terms described in this policy. Continued use of Revision History after updates constitutes acceptance of the revised policy.
19. Regulatory Compliance & Data Rights
Data Ownership
You retain full ownership of all personal information you provide to Revision History. We do not claim any ownership rights to your data.
FERPA Compliance
Because the Revision History teacher extension does not collect, store, or transmit student education records or document content, our service is designed to support school compliance with the Family Educational Rights and Privacy Act (FERPA). When a school enables Byline, we process Student Data as a school official with a legitimate educational interest under FERPA, under the school's direct control and pursuant to a signed DPA.
COPPA Compliance
Revision History is designed to comply with the Children's Online Privacy Protection Act (COPPA). We do not collect personal information from children under 13 without appropriate consent, and we do not collect any student document content through the teacher extension. For Byline, we collect students' personal information, including from students under 13, only with school authorization under a signed DPA, as described in Sections 3 and 11.
GDPR Compliance
We adhere to the principles of the General Data Protection Regulation (GDPR) for processing personal data of EU residents.
Data Retention
- Student and document data: Not applicable — we do not collect, store, or retain any student writing, document content, or document metadata through the teacher extension.
- Byline Student Data: Retained as described in Section 3 and the applicable school DPA. By default, AI coaching records and associated document context are deleted or de-identified within 12 months.
- Account information: Your email, name, and subscription status are retained while your account remains active.
- Account deletion: Upon request, we will delete your account information within 30 days. Contact info@revisionhistory.com to request deletion.
20. Changes to this Privacy Policy
We reserve the right to revise this Privacy Policy at any time. When we do, we will update the "Effective Date" above and post the revised Privacy Policy here. For material changes, we will provide at least 30 days' advance notice as described in Section 18. Your continued use of our website or services after changes take effect indicates your consent to the revised Privacy Policy. You are responsible for ensuring we have an up-to-date, active and deliverable email address for you, and for periodically visiting our website and this Privacy Policy to check for any changes.
21. Contact Us
For any questions or comments, please reach out to us at:
Email: info@revisionhistory.com