InkpostPrivacy Policy
This policy explains what data the Inkpost browser extension (“the extension”) accesses, why, where it is stored and who receives it. The extension is developed by an independent developer (“we”, “us”). Questions: pashahorolskij4@gmail.com.
Summary
- Articles are processed locally in your browser. We don’t run any server that receives your data, and we never see it.
- No analytics, advertising or tracking. We don’t sell or rent data.
- Data leaves your browser only to do what you asked for: Google sends the email with the book from your Gmail account, PocketBook delivers it to your reader, and websites serve the article’s images.
- The extension can send email from your Gmail account. It cannot read your email.
What the extension accesses and why
The page you choose to send
When you click the extension icon or press its keyboard shortcut, the extension reads the page in the current tab: its address, title, author, site name, publication date, language, text and images. It uses them only to build the EPUB book. The extension does not read other tabs or pages you haven’t chosen, and it does not run on the sites you visit.
Article images
To put images in the book, the extension downloads them directly from the websites that host them. For images hosted on other domains it may ask for optional permission to access all websites. It uses this permission only to download article images, and you can refuse it. Some sites serve images only when the request carries the article address, so while downloading, the extension sends that address in the Referer header. These websites receive the same information as when you view the page in your browser: your IP address, the image address and the article address.
Your Google account
When you click Sign in with Google and agree, Google grants the extension two permissions:
- Send email on your behalf (
https://www.googleapis.com/auth/gmail.send). Used only to send the book you chose, or a test message when you click Test send, to the Send‑to‑PocketBook address you entered in the settings. - Your email address (
https://www.googleapis.com/auth/userinfo.email). Used to show which account is connected and as a sign‑in hint, so the extension can renew access without asking you again.
The extension does not ask for and has no access to reading, searching, changing or deleting your email, contacts, files or any other Google data. Google issues it a short‑lived access token, valid for about an hour. The extension has no refresh token and no client secret.
Settings
Your Send‑to‑PocketBook address and preferences: image options, the email subject template and whether to add a link to the original.
Where the data is stored
Everything is stored in your browser on your device. We have no copy.
| Data | Where | How long |
|---|---|---|
| Settings, including the Send‑to‑PocketBook address | Browser sync storage. If Chrome sync is on, the browser syncs it between your devices through your Google account. | Until you change them or remove the extension |
| Email address of the connected Google account | Local browser storage | Until you sign out or remove the extension |
| Google access token | Session storage, in memory only | About an hour; deleted when you sign out or close the browser |
| Article content, your edits in the preview, send status | Session storage, in memory only | Until you close the browser; entries older than 12 hours are also removed automatically |
| Built EPUB files | The extension’s database (IndexedDB) on your device | Removed once older than 12 hours, at the next browser start or the next article you process |
Who receives data
- Google, to sign you in, check the token and send the email through the Gmail API. The email contains the EPUB file, the article title as the subject (you can change the template) and a line with the link to the original article. It is sent from your Gmail account, so a copy stays in your Sent folder. Google processes this data under the Google Privacy Policy.
- PocketBook. The email goes to the Send‑to‑PocketBook address you entered. PocketBook processes it under its own privacy policy and delivers the book to your reader.
- Websites hosting the article’s images, as described above.
We don’t share data with anyone else. We don’t sell data, don’t use or transfer it for advertising, and don’t use or transfer it to determine creditworthiness or for lending purposes.
Google API Services User Data Policy
Inkpost’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- data received from Google APIs is used only to provide the features you see in the extension: sending the book you chose and showing which account is connected;
- it is transferred to others only as needed for that: the email with the book goes to the address you entered;
- it is not used for advertising, including personalized, retargeted or interest‑based advertising;
- no human reads it: it never reaches us;
- it is not used to develop, improve or train generalized AI or machine learning models.
The extension’s handling of data also complies with the Chrome Web Store Developer Program Policies, including the Limited Use requirements.
Permissions
| Permission | Why |
|---|---|
activeTab, scripting | Read the article in the tab where you clicked the icon or pressed the shortcut. |
storage | Keep the settings, the connected account address and the temporary data listed above. |
identity | Open the Google sign‑in window. |
offscreen | Convert the article to the XHTML that EPUB requires and render SVG images. The extension’s background script cannot parse HTML by itself. |
notifications | Report the result when the extension menu closes before the book is built or sent. |
declarativeNetRequestWithHostAccess | Add the article address (Referer) to the extension’s own image requests. |
declarativeContent | Enable the icon only on pages that look like articles. |
Access to gmail.googleapis.com and oauth2.googleapis.com | Send the email, check and revoke the token. |
| Optional access to all websites | Download article images hosted on other domains. Requested only when needed; you can refuse. |
Your choices
- Click Sign out in the extension’s settings: the token and the account address are deleted from the browser, and the extension asks Google to revoke the token.
- Revoke the extension’s access at any time in your Google Account.
- Remove the extension: the browser deletes all data it stored, settings included.
- Emails already sent stay in your Gmail Sent folder, and books stay in PocketBook, until you delete them there.
Since we hold no data about you, there is nothing for us to export or delete, but you are welcome to contact us with any question.
Security
All requests go over HTTPS. The access token is kept in session memory only and is never written to disk. The extension contains no client secret and does not load or run code from the internet.
Children
The extension is not directed at children under 13, and we don’t knowingly collect data from them.
Changes to this policy
If the way the extension handles data changes, we will update this page and the date at the top before releasing the new version of the extension.