Privacy policy

What Pluckr does

Pluckr is an add-on for Google Docs and Google Slides. It gets the images from the document where you open its sidebar.

• In Docs, Pluckr reads inline images.
• In Slides, Pluckr reads the pictures on slides. This includes grouped pictures.

Pluckr shows a preview, a name, the dimensions, and the file size of each image. You can copy, download, or rename each image. You can also convert it to AVIF, WebP, JPEG, or PNG.

Your browser converts and resizes the images. Apps Script reads the image data of the document. When you ask for it, Apps Script also makes a ZIP file of the original images.

Pluckr also has four optional features. Each feature runs only when you choose it:

• Export alt text files.
• Export the document as Markdown.
• Edit the alt text of an image.
• Optimize the images of the document. Optimize replaces the images in the open document with smaller copies.

Pluckr is free for up to 50 images for each Google account, in total. Pro is a one-time purchase. To find out if you bought it, Pluckr asks Google for an identity token for your account. Pluckr sends the token to its license service. The license service replies if a paid license exists for your account.

Information Pluckr accesses

• Images in the current document. After you choose to scan or refresh a scan, Apps Script reads the inline images in the body of the document. This includes images in tables and in document tabs. Apps Script reads the image bytes, file type, and dimensions of each image. It also reads the alt text (title and description) and the link address of each image. Pluckr uses this data to show and export the images. Pluckr does not extract floating images or images in headers, footers, or footnotes at this time.
• Pictures in the current presentation. In Google Slides, after you choose to scan or refresh a scan, Apps Script reads the pictures on each slide. This includes pictures inside groups.
• Document text and structure (Markdown export only). Pluckr reads this data only if you tick the Markdown option. Apps Script reads the text, headings, lists, tables, links, and basic formatting of each document tab. Apps Script sends this data to the sidebar. The sidebar builds the content.md file in your browser. Pluckr does not read this data if you do not choose the option.
• Alt text changes (only when you choose them). If you press Save to Doc on the alt text of an image, Pluckr writes that text to the image. Pluckr changes nothing else.
• Optimize changes (only when you choose them). If you confirm the optimize step, Pluckr replaces the images in the open document with smaller JPEG or PNG copies. Pluckr replaces the images one by one. Each copy keeps the size that the image already has on the page. Each copy also keeps the alt text and the link of the image. Pluckr does not change anything else in the document.
• Backup. We recommend that you make a copy of the document first. Google Docs version history can restore the earlier version.
• Document name. Apps Script uses the name of the document to name the ZIP file of original images.
• Google account identity and email. When you open Pluckr, it asks Google for an identity token. The token contains your Google account ID. Pluckr asks for the email scope, so the token also contains your email address. Pluckr uses the account ID and the email address only to check and record your license.
• License and purchase record. Pluckr’s license service stores your Google account ID and your email address. It also stores if you have a paid license and the date of purchase. It stores the order and customer references from Polar. For the free plan, it also stores a SHA-256 hash (a one-way fingerprint) of each image that you copy or download, with your account ID. It uses the hashes only to count your 50 free images. A hash does not show the image, and the license service never receives the image. It records the time when your Google account agreed to the Privacy Policy and the Terms before checkout. It does not store document content or your identity token.
• Authorization. Pluckr asks for access to the current document. It asks for permission to show a sidebar in Google Docs and Google Slides. It also asks for your Google account identity and email to check your license. For Save to Drive, it asks for access only to the Drive files that Pluckr creates. The manifest uses the documents.currentonly, presentations.currentonly, script.container.ui, drive.file, openid and userinfo.email scopes. Pluckr does not ask for access to browse all of your Google Drive.

How document data is handled and shared

Apps Script reads the image bytes from the current document. It sends them to the sidebar for previews and for conversion in your browser. When you ask for a ZIP file of originals, Apps Script makes the archive. It then sends the archive to the sidebar.

Google Docs and Apps Script process the image data. Google LLC operates them. This is necessary to give you the features of Pluckr.

Pluckr does not send document images or document text to a separate Pluckr server. Pluckr does not give them to other companies or people. Pluckr sends only your identity token to the license service. On the free plan, it also sends the SHA-256 hash of each image that you choose to copy or download. A hash is a one-way fingerprint. It does not contain the image or any text from your document.

When you download a file, Pluckr sends it to your device at your request. When you click Copy, Pluckr writes the image to the clipboard of your device. Google can process data under its own terms and privacy practices.

We do none of these things with Google user data:

• We do not sell it.
• We do not use it for advertising.
• We do not allow human review of document images.
• We do not train AI or machine-learning models with it.
• We do not share it for purposes that are not related to the image extraction and export features of Pluckr.

Website hosting providers and content-delivery providers can receive ordinary connection information when you visit docpluckr.com. The section Website and third-party services describes this. These providers do not receive document image data through Pluckr.

Files saved to your Google Drive

Save to Drive is a Pro feature. Pluckr uses it only when you choose it. Apps Script then creates a folder named after your file in your My Drive, and saves the files that you selected in that folder. Google Drive stores the files. Pluckr’s servers do not receive them.

The drive.file scope lets Pluckr reach only the files and folders that it creates. Pluckr stores the ID of the folder in the properties of your document, so that a second save uses the same folder. If a file with the same name is in the folder, Pluckr replaces that file.

The files stay in your Google Drive until you delete them. Pluckr does not delete them for you.

License checks and purchases

Pluckr is a one-time purchase. Polar processes the payments. When you buy, Polar collects your payment and billing details. Polar uses its own privacy policy for this data. Pluckr does not receive or store your card number.

To start your checkout, Pluckr’s license service gives Polar your Google account ID and your email address. Polar uses the account ID as your customer reference.

When your payment succeeds, Polar tells the license service that the order is paid. Polar sends the order reference, the customer reference, and your email address. The license service uses them to record your license against your Google account.

If Polar refunds your payment, Polar tells the license service. The license service then turns off your license.

Convex hosts Pluckr’s license service. Each time you open Pluckr, the license service makes sure that your Google identity token is valid. It uses the public keys of Google for this. It then looks up the license for your account.

The license service uses your account ID and email address only for these purposes:

• to make sure that you have a paid license
• to give purchase support and refunds
• to stop misuse of licenses

We do not sell this information. We do not use it for advertising. We do not share it for purposes that are not related to Pluckr. Convex and Polar process it for us. They use their own terms and privacy policies.

Data protection

Pluckr uses these safeguards for the data that it accesses:

• Limited access. The manifest asks for the documents.currentonly and presentations.currentonly scopes. These scopes limit access to the one document or presentation where you use Pluckr. The script.container.ui scope shows the sidebar. The openid and userinfo.email scopes identify your license. Google authorization controls access. You can revoke it in the permissions of your Google Account.
• Encryption in transit. Image data moves between Google Docs, Apps Script, and the sidebar through the Apps Script service of Google. Connections to Google services use HTTPS/TLS. Google manages the service and the infrastructure safeguards. See the encryption-in-transit documentation of Google.
• Temporary processing. Pluckr holds image data and conversion results in memory while it prepares a scan, preview, conversion, or download. Pluckr does not write document image bytes to persistent storage or to application logs. Pluckr does not keep a separate copy after the operation ends.
• Identity checks. The license service accepts only identity tokens that Google signed for Pluckr. It does not store the token. Requests to the license service use HTTPS.
• Server-side license check. Before the server code of Pluckr reads document images, it needs a short-lived license confirmation. The license service signs the confirmation. The confirmation belongs to your Google account.
• License data storage. Convex stores the license records. Convex encrypts data in transit (TLS) and at rest. Only the Pluckr developer has access to the license database. Pluckr keeps service credentials as protected server settings. The credentials are never in Pluckr itself. Pluckr accepts payment notifications from Polar only if their cryptographic signature is valid.
• No separate image store. Pluckr does not make a persistent server-side copy of document images. Pluckr does not add a separate encryption layer to them. The security and data-handling practices of Google govern how Google processes data in its services.

These measures describe the current Pluckr implementation. They do not make Pluckr responsible for the independent infrastructure, security controls, or retention practices of Google.

Retention and deletion

Pluckr does not keep document images after the operation that you ask for. Image previews and conversion results stay in the memory of the sidebar while Pluckr needs them. Pluckr makes the ZIP file of originals only for the download that you ask for. When you close the sidebar, Pluckr releases its memory data.

Files that you download stay on your device until you delete them. Google has its own operational retention, if any. Google policies govern it. To stop future access, uninstall Pluckr and revoke its authorization in the settings of your Google Account.

Pluckr keeps your license record while your license is active. Pluckr also keeps the record of a refunded purchase. Pluckr keeps both until you ask us to delete the record.

The license record contains your Google account ID, your email address, the license status, and the purchase date. It also contains the order and customer references from Polar. It contains the time when you agreed to the policy and the terms. On the free plan, it also contains the hashes of the images that you used, up to 50. Pluckr keeps them until you ask us to delete them, so that your 50 free images stay counted.

To delete your record, email support@docpluckr.com. When we delete it, your license ends. We cannot restore it without proof of purchase. Polar keeps payment and tax records for the period that the law sets. Polar uses its own policy for this.

Website and third-party services

Google hosts Pluckr and the Apps Script runtime. Convex hosts the license service of Pluckr. Polar processes payments, as this policy describes above.

Cloudflare hosts the docpluckr.com website. The website loads some scripts from content-delivery networks. Webflow is one example.

When you visit the website, these providers can receive ordinary connection information. This includes your IP address, your browser details, and the URLs that you request. They use their own policies for this data. Pluckr does not use the add-on to show advertising or to do behavioral analytics.

Google API Services and Limited Use

Pluckr’s use of information that it receives from Google APIs adheres to the Google API Services User Data Policy. This includes the Limited Use requirements.

Pluckr uses Google user data only to:

• give the image-extraction and export features that you ask for
• check and record your license

Pluckr never uses your Google account ID and email address for advertising. Pluckr never sells them. Humans do not read them, except in three cases: with your consent, for security, or to obey the law.

We give them only to our service providers, Convex and Polar. They need them to give these features.

In full: Pluckr shares your Google account ID and email address with Convex (license storage) and with Polar (checkout and payment records). Pluckr shares them with no one else. Pluckr shares document images and content with no one other than Google.

Revoking access

You can revoke the authorization of Pluckr in the permissions of your Google Account. You can also uninstall Pluckr from Google Docs. Or you can choose Log out in the menu of Pluckr. Log out revokes the authorization.

After you revoke access, Pluckr does not have access to the current document. Pluckr does not delete your license record. To delete it, email support@docpluckr.com.

Changes to this policy

We will change the “Last updated” date when we change this policy. If a change affects how Pluckr handles Google user data, we will describe the new practices here.

Terms of Use

Our Terms of Use also govern your use of Pluckr.

Contact

Email support@docpluckr.com with questions or privacy requests.