Student data privacy statement
This page explains, in plain language, what the Clipboard History Pro extension does with data when a school uses it. It adds detail to our Privacy Policy for schools. Where the two differ, this statement applies to school users.
The short version
- Clipboard items are stored on the device, in the browser profile. We cannot see them.
- Nothing a user copies goes to our servers unless that user signs in to the optional Pro cloud sync and sends items there.
- Analytics get a random install ID and usage events. They never get clipboard text.
- The extension does not sell or share personal data, and it shows no third-party ads.
- A user can delete any item, or all items, at any time.
Who we are
Clipboard History Pro is made by Third South Capital. Districts that need our postal address for an agreement can ask for it. Contact: [email protected] for privacy questions and [email protected] for everything else.
What the extension collects, and where it goes
| Data | When | Where it is stored |
|---|---|---|
| Text the user copies, the date, its length, and the web address of the page it came from when the browser provides it. Also the user's favorites, tags, titles and text shortcuts. | Always, while the extension is on | On the device only, in the browser profile (IndexedDB). Not sent to us. |
| Settings (history limits, theme, PIN lock). | Always | On the device only. |
| Items the user syncs or sends to the cloud, with the date and the device type (for example "Chrome extension"). | Only if a Pro user signs in and turns on sync or sends an item. Auto-sync is off by default. | Our Firebase Realtime Database (Google Cloud), under that user's account. |
| Google account name, email address and profile photo. | Only when a user signs in for cloud sync. | Firebase Authentication (Google Cloud). |
| Usage events: a random install ID, a session ID, event names (such as install, popup opened, first item saved, trial started), the extension version, the platform name, the number of saved items and sessions, days since install and the plan (free or Pro). | Always | Google Analytics 4. No clipboard text, web addresses, names or emails are sent. |
| Error reports: the error, the code location, browser details and counts (for example, how many items an action affected). From build 3629 (late 2026), reports contain no item text, titles, tags, search words, item fingerprints, page addresses or emails. Earlier builds could include an item's title or tags, a search word, or an item fingerprint (hash). | When something breaks | Sentry (error monitoring). The full text of clipboard items is never included. |
| Billing details: name, email, payment method and subscription status. | Only when someone buys Pro. | Paddle (our payment provider) and our database. We do not see full card numbers. |
The extension also downloads feature settings from our server and a news feed of product updates. These requests do not include user data beyond what any web request carries (such as IP address and browser type).
What the extension does not do
- It does not send clipboard text to us unless a user turns on cloud sync or sends an item to the cloud.
- It does not show third-party ads. Free users, students included, see occasional prompts to upgrade to Pro. If your district does not want students to see them, contact us before you deploy.
- It does not sell personal data or use it for targeted advertising.
- It does not build profiles of students.
- It does not save images. It saves text only.
Who can access the data
- Local items: anyone who uses that browser profile. A Pro user can add a PIN lock. We have no access.
- Cloud items: the signed-in user, from the extension, the mobile app or the web viewer. Our database rules allow only the account owner to read them. Administrator access is limited to the company owner's account and the service accounts our server software uses. We use it to give support, fix billing and run the service.
- Service providers: companies that run parts of the service for us. They are listed below. They may use the data only to provide their service to us.
- Legal requests: we disclose data only when the law requires it.
Cloud items are encrypted in transit (HTTPS). Google Cloud encrypts stored data. Cloud items are not end-to-end encrypted, so we could technically read them. We do not read them, except when the user asks us to as part of a support request.
Service providers
| Provider | What for | What it receives |
|---|---|---|
| Google (Firebase, Google Cloud) | Sign-in, cloud database, server functions | Cloud items and account details, only for users who sign in |
| Google Analytics 4 | Usage analytics | Usage events listed above |
| Sentry | Error monitoring | Error reports listed above |
| Paddle | Payments | Billing details, only for buyers |
| OpenAI | Looks up public information about a new subscriber's organization, from the email domain, to help us support business and school accounts | The buyer's email domain (for example, a district's domain) and the public text of that domain's home page, only when a paid subscription starts. No student data. |
| Slack | Internal alerts to our team about new subscriptions | The buyer's email address and domain, and the result of the domain lookup |
| Postmark | Account and billing emails | Email address of buyers |
How long we keep data
- Local items stay until the user deletes them, until they pass a limit the user sets (by age or by count), or until the extension is uninstalled. By default the extension keeps up to 50,000 items. If your Chromebooks erase local data at each sign-out, local items are erased then.
- Cloud items stay until the user deletes them or until they pass the user's cloud auto-clean limit. When a subscription ends, its cloud items stay until the user deletes them or asks us to delete them.
- Account records are deleted when we delete the account (see below).
- Billing records are kept for six years after someone stops being a customer, for tax and accounting law.
- Analytics events are kept for the retention period set in Google Analytics, at most 14 months. Error reports are kept for at most 90 days.
How to delete data
- One item: open the extension and click the delete button on the item.
- All items: open the extension menu and choose delete all. Do this in the cloud view too, to delete cloud items.
- Everything on a device: uninstall the extension. The browser deletes its local data. For a force-installed extension, an admin sets the policy to Block, uninstall from Chrome.
- The whole account and all cloud items: email [email protected] from the account's email address, or ask your school's admin to email us. We delete the account, its cloud data and our email records within 28 days. For a request from a school, we confirm it comes from an administrator at the school's own email domain. Paddle, our payment provider, keeps its own billing records under its privacy policy. Mobile app users can also delete their account in the app.
FERPA
Clipboard History Pro is a general productivity tool. It is not built to collect or manage education records. It stores what each user copies on that user's device. If a teacher copies student information, that text stays in the teacher's local history unless the teacher sends it to the cloud.
We do not claim any FERPA certification, and FERPA does not certify vendors. If your district wants to treat us as a "school official" under FERPA, we will work with you on a written agreement that sets out how we use and protect the data. We will review the SDPC National Data Privacy Agreement or your state's agreement on request. Email [email protected].
Children under 13 (COPPA)
Clipboard History Pro is not directed to children under 13, and our Privacy Policy says we do not provide services directly to children. If a school wants to use the extension with students under 13, contact us before you deploy. Under COPPA, a school can give consent on behalf of parents only for use in the school context. We will need to agree how that works with you first.
Local clipboard history needs no account and sends no clipboard text to us. Every device, including a student's, sends usage events with a random install ID and error reports. They contain no name, email or clipboard text. Cloud sync needs a Google sign-in. Admins can block that sign-in for student accounts in the Google Admin console (see the deployment guide).
Security
- Data between the extension and our servers travels over HTTPS.
- Database rules let each signed-in user read and write only their own cloud items.
- If we learn of a breach that affects your users' data, we will notify affected schools and users as the law requires.
Changes to this statement
If we change how the extension handles data, we will update this page and the date at the top. For material changes that affect school users, we will email the schools that have told us they use the extension.
Contact
Privacy: [email protected]
Support and district questions: [email protected]