Privacy policy
Last updated November 13, 2026
Pressetter is a Google Docs add-on that typesets manuscripts into book files, and this website, pressetter.com. Pressetter is operated by Terrence McCann (“we”). This policy explains what information Pressetter handles, why, and what we do with it. The short version: we use your manuscript only to make your book files, we don’t keep it, and we don’t sell or share your information for advertising.
What the add-on accesses in Google
When you install Pressetter, Google asks you to allow these permissions. Each is used only as described:
- View and manage the document you open Pressetter in (documents.currentonly). Pressetter reads the text, headings, formatting, footnotes and images of the open document to check and typeset it. It never edits your document, and it can’t see your other documents.
- Create files in your Google Drive (drive.file). Pressetter saves the PDF and EPUB it makes to your Drive. This permission only covers files Pressetter itself creates; it can’t see or change anything else in your Drive.
- Display the sidebar (script.container.ui) and connect to an external service (script.external_request), which is our typesetting server, described below.
The manuscript check
The free check runs entirely inside Google’s Apps Script service. Your manuscript isn’t sent to us when you run it.
Exporting
When you choose Export, Pressetter sends the content of your manuscript (text, formatting, footnotes and images), the book details you entered (such as title, author and ISBN) and your layout settings to our typesetting server, over an encrypted connection. The server runs on Google Cloud Run in the United States. It lays out your book in memory and returns the finished files, which are saved to your Google Drive.
We don’t store your manuscript or the files made from it. Nothing from your manuscript is written to disk or to logs, and no person at Pressetter reads it. Like most web services, our hosting keeps short-lived technical logs of each request (time, IP address, response status and size) for security and troubleshooting; these logs don’t contain your manuscript.
What is saved, and where
- In your document, as Google Docs add-on properties: your book details and layout settings, and, for a single-book license, the activation code that ties the license to that document.
- In your Google account, as add-on user properties: your license key, so you don’t have to paste it each time.
- With your purchase in Stripe, for a single-book license: the anonymous document code described below and the book’s title, which tie the license to that book.
You can clear these by removing the add-on, or by deleting your license key in the Export tab.
Licenses and payments
Payments are processed by Stripe; we never see your card details. We receive your name, email address and order details from Stripe to deliver your license key, provide support and honor refunds. Stripe’s own privacy policy applies to the checkout. We email your license key to you through Cloudflare’s email service.
When you export with a license key, our server looks up the purchase with Stripe to confirm it’s paid and hasn’t been refunded. For a single-book license it also records, with that purchase, an anonymous identifier for the document (a one-way code derived from the document’s id, which can’t be used to find or open your document) and the book’s title.
This website
pressetter.com uses no cookies, no analytics and no advertising trackers. Its fonts are served from our own site. Our web host keeps standard request logs.
Google user data
Pressetter’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide Pressetter’s features to you. We don’t sell it, use it for advertising, or let anyone read it, except where you ask us to for support, where needed for security, or where the law requires.
Pressetter does not use Google Workspace APIs or any Google user data, including the content of your documents, to develop, improve or train generalized or non-personalized AI or machine-learning models, and does not transfer that data to anyone else for that purpose.
How we protect your data
We treat your manuscript and other Google user data as sensitive, and protect it with these safeguards:
- Encryption in transit. Every connection that carries your data is encrypted with HTTPS (TLS): from the add-on to our typesetting server, from our server to Stripe when checking a license and to Cloudflare when emailing your key, and to pressetter.com. We don’t accept unencrypted connections.
- Encryption at rest. The only information Pressetter keeps (your book details, layout settings and license key, saved as add-on properties) is stored inside Google’s own infrastructure in your document and Google account, where Google encrypts it at rest. Our hosting providers (Google Cloud and Cloudflare) and Stripe also encrypt the data they hold at rest.
- No storage of your manuscript. The typesetting server processes each export in memory and discards it as soon as the files are returned. Your manuscript and the finished files are never written to disk, a database or logs, so there is no stored copy to be exposed.
- Minimum access. The add-on requests only the narrowest Google permissions it needs: the one document it is opened in, and only the Drive files it creates. It can’t see your other documents or the rest of your Drive.
- Anonymized identifiers. Where a single-book license needs to recognize a document, we use a one-way hash of the document’s id rather than the id itself.
- Restricted access. Only the operator of Pressetter can access our server, hosting, email and payment accounts. These accounts are protected by strong passwords and 2-step verification, and server secrets such as API keys are kept in the hosting provider’s protected configuration, not in our code.
- Request limits. The server rejects malformed or oversized requests, and checks license keys with Stripe over an encrypted connection before producing full files.
- Incident response. If we ever learn of a security incident affecting your information, we will act promptly to contain it and notify affected users, and the relevant authorities where required by law.
No method of transmission or storage is completely secure, but we design Pressetter to hold as little of your data as possible and to protect what it handles.
Sharing
We share information only with the services that run Pressetter (Google Cloud for hosting, Cloudflare for our website and email, Stripe for payments), or when required by law. We don’t sell personal information.
Your choices
You can stop using Pressetter at any time by removing it in Google Docs (Extensions, Add-ons, Manage add-ons), and revoke its access in your Google Account under Security, Third-party access. To ask what we hold about you, or to have it deleted, email support@pressetter.com.
Children
Pressetter isn’t directed at children under 13, and we don’t knowingly collect their information.
Changes
If we change this policy, we’ll update the date at the top. If a change affects how we use your manuscript or Google data, we’ll say so on this website and in the add-on before it takes effect.