WPPS SYNC PRO EXTENSION — Privacy Policy

Effective date: 11 October 2026
Operator: Saabas Technologies (“we,” “us,” or “our”)
Privacy contact: wppsextension@gmail.com

This Privacy Policy explains how WPPS SYNC PRO EXTENSION (“WPPS”) handles information when you use its image-syncing features for WordPress and Blogger and its Pinterest Studio pin-design tools. It covers the extension, our associated license-verification service, and the WhatsApp sales and support process described below. Services you connect to WPPS also have their own privacy policies.

1. What WPPS does

WPPS reads supported image prompts from blog posts, lets you copy those prompts, monitors a folder you select, converts supplied images to WebP, and uploads them into your blog workflow. It applies filenames and alt text prepared in your image placeholders. WordPress mode uses a compatible companion plugin. Blogger mode uses Google authorization, the Blogger API, and Cloudinary image hosting.

Pinterest Studio creates template-based pin designs from titles and images you provide or choose to extract from an article. You can edit text, colours, layouts and image crops, add optional call-to-action text and a website name, and download designs as WebP images or a ZIP archive. Pin rendering and editing take place locally in your browser using bundled templates and fonts; they do not send your content to an AI image-generation API. License verification and requested article/image downloads still require network connections.

WPPS does not create new background photographs using generative AI. If you paste prompts into Google Flow or another image-generation service, that service handles them under its own terms and privacy policy. Pinterest Studio does not connect to a Pinterest account or automatically publish or schedule pins; you decide whether and where to upload downloaded designs.

2. Information the extension handles

Connection settings and authentication

WPPS handles the WordPress site URL and API key you enter, your selected platform, Google OAuth client ID, and Cloudinary cloud name, unsigned upload preset, and optional folder name. When you connect Google, WPPS receives an access token and its expiration time and may retrieve your Blogger account profile, including its display name, to show connection status.

Google sign-in takes place through Google's authorization flow. WPPS does not ask for or receive your Google password. It does not require a Google OAuth client secret.

Blog content and image files

WPPS processes post and blog identifiers, supported article content and image placeholders, prompts, filenames, alt text, and images you provide. It reads files in the folder you select to detect new supported images and process them against the prompt queue. Folder watching operates while the side panel is open. Selecting a folder authorizes access to that folder; it does not give WPPS unrestricted access to every file on your computer.

Pinterest Studio content and article extraction

Pinterest Studio handles the titles, article URLs, call-to-action text, optional website name, filename preferences, brand colours, aspect ratios and template selections you enter. It also processes selected image files, image names or alt text, image dimensions, generated previews, and edits such as text size, position, colour and image cropping.

When you request extraction from an article URL, WPPS downloads that page and examines its HTML for image references. When you choose to use images from an open article tab, a bundled function reads image references, alt text and relevant page metadata. Page metadata is used to identify and exclude featured and social-preview images and their detected variants. This filtering depends on how the website marks its images and may not identify every featured image.

The extension downloads candidate images from the article's website or image hosts, which may include separate CDN domains. These hosts receive the requested URLs and ordinary network connection information, including your IP address. Pinterest Studio's direct article and image fetches omit browser credentials and the referrer header. WPPS does not send your WordPress API key, Google access token or license key with these extraction requests. Reading an already-open tab uses content loaded in that tab and does not change the website's own data practices.

Pin designs, input settings, source image copies and previews are saved locally as described in Section 6. Downloading a pin or ZIP archive saves it to your device; it does not send the design to Pinterest or to our licensing service.

Editor URLs and workflow state

When you request to load prompts, WPPS examines tab URLs in the current browser window to locate a supported blog editor, considering the active tab first. For WordPress, a bundled script reads the editor's post identifier. Pinterest Studio also checks tab URLs when you request images from an open article; it uses the active web tab or an available recent web tab in the current window when the active tab is not a web page. The extension does not use Chrome's history API to retrieve your historical browsing record.

WPPS stores prompt queues, copied-prompt status, and related workflow identifiers locally so the interface can maintain your progress. It does not include general keystroke, mouse-movement, or browsing-behavior analytics.

Licensing and installation identifiers

WPPS handles your license key, license status, and a randomly generated installation identifier. It sends the license key and installation identifier to our Supabase-hosted license-verification service to check authorization and help prevent unauthorized license use. A valid license is required to access Pinterest Studio. Verification may occur when the tool opens, when it becomes active again, and periodically while it is in use. The installation identifier is generated by the extension; it is not a hardware serial number read from your device.

IP addresses and planned licensing checks

The current extension sends the license key and a randomly generated installation identifier in its license-verification request. It does not look up or include a separate IP-address field in that request. Receiving servers and hosting providers can still see the connection IP address and may retain ordinary service or security logs under their own policies.

IP-based license verification is a future plan and is not active. If introduced, we intend to use IP addresses associated with license-verification requests to validate license use, investigate unauthorized sharing, and prevent abuse. Before activating this feature, we will update this policy to explain the information collected, its use, and retention, and provide any notice or obtain any consent required. We do not plan to use this feature for precise GPS tracking or advertising profiles.

Separately, internet connections make an IP address available to the receiving service. Third-party services used by the extension may process connection information under their own privacy policies; this is distinct from our planned IP-based licensing feature.

WhatsApp purchases and manual payments

We currently sell licenses directly through WhatsApp. When you contact us to purchase a license, we receive your WhatsApp phone number, profile information visible to us, and the messages you send. We share payment instructions, confirm your payment, and create a license key for you.

This process may involve your name, the license or plan requested, payment amount, payment date, transaction reference, payment status, and any receipt or payment screenshot you provide. The bank or payment service used may also show us payer details. Please share only the information needed to confirm payment, and redact unrelated balances or transactions from screenshots. We do not ask for banking passwords, card security codes, or one-time verification codes.

We use these records to communicate with you, verify purchases, issue and manage licenses, resolve payment or license problems, and maintain necessary sales records. When necessary, we associate a purchase with its issued license key and related license-verification records.

The Chrome extension itself has no payment checkout and does not read WhatsApp conversations or collect payment receipts from your browser. Purchase information is provided separately through WhatsApp or the payment service you use. WhatsApp and your bank or payment provider handle information under their own privacy policies.

Support requests

If you contact us, we receive the information you choose to send, such as your email address, description of the issue, and relevant screenshots. Do not send passwords, access tokens, or API keys in support messages.

3. How information is used

We use information to provide the image-syncing and pin-design workflows you request, authenticate connected services, retrieve prompts and article images, upload and place blog images, render and edit pin designs, save drafts and downloads locally, preserve workflow settings, verify purchases, issue and manage licenses, prevent license abuse, and respond to support and privacy requests.

We do not sell personal data, use extension data for targeted advertising, build unrelated browsing profiles, or use it to determine creditworthiness or lending eligibility.

4. Where information goes

The extension code does not send article text, image prompts, source image files, pin titles, brand colours or completed pin designs to our licensing endpoint. These are handled locally or by the source and destination services used for the requested workflow. WPPS does not upload your Pinterest Studio drafts to an operator-managed cloud design service.

Other disclosures are limited to providing or improving these user-facing features, investigating security or abuse, complying with applicable law, or a business transfer where permitted and subject to appropriate notice, safeguards and any required prior consent. The additional Google user data restrictions in Section 5 continue to apply.

5. Google user data and Limited Use

WPPS's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. WPPS handles extension user data consistently with the Chrome Web Store User Data Policy, including Limited Use requirements.

Google user data is used to provide the visible Blogger features requested by the user. This data is not sold, used for advertising, or used to train generalized artificial-intelligence models. Pinterest Studio does not require Google sign-in or Pinterest account authorization. Human access to protected user data is limited to circumstances permitted by the applicable Limited Use requirements, such as specific user consent for support, security investigations, or legal obligations.

6. Storage, retention, and security

Connection settings, API keys, license information, prompt queues, and copied-prompt state are stored using Chrome's local extension storage. Google access tokens are stored in Chrome session storage with expiration information; expired tokens are not reused for authorization. Changing or clearing the configured OAuth client ID clears the cached Google token.

Pinterest Studio saves the current draft in local IndexedDB storage within the extension. This includes input settings, titles, the entered article URL, optional website and call-to-action text, brand colours, template choices, aspect ratios, source image copies, generated pin data, previews and edits. This allows the draft to reopen without re-entering the content. The extension saves prepared image copies rather than modifying your original source files. Media entries no longer referenced by the saved draft are removed during subsequent successful saves.

Downloaded WebP images and ZIP archives are separate files on your device. They remain until you delete them yourself and may be handled by any backup or sync software you have configured.

Local information can remain until it is overwritten, removed, or cleared by uninstalling the extension. Clearing ordinary browsing history does not necessarily clear extension storage. WPPS does not provide a separate encrypted credential vault.

Our fixed Google, Cloudinary, and Supabase endpoints use HTTPS. WordPress requests use the site URL configured by the user; configure an HTTPS URL to protect API credentials and uploads in transit. No storage or transmission method can guarantee absolute security.

Our server-side retention schedule: We retain license records and installation identifiers for as long as necessary to administer the license and address associated security or support matters. WhatsApp sales conversations, payment confirmations, and support records are retained only as long as needed to fulfill purchases, resolve inquiries or disputes, prevent abuse, and meet applicable accounting or legal obligations. When those purposes no longer apply, we delete or anonymize records we control. Where records remain in backups, they are removed through the applicable backup lifecycle and are not used for ordinary business purposes. IP-based license checks are not currently implemented by the extension; any future dedicated IP-based licensing feature will have its data use and retention disclosed before activation. Hosting-provider connection logs are separate from that planned feature.

Content uploaded to your WordPress site, Blogger, or Cloudinary remains subject to your actions and those services' retention policies. Removing WPPS does not delete uploaded images, blog posts, Google consent grants, or records retained by the license service.

7. Your choices and deletion requests

You may stop folder monitoring by closing the side panel, change connection settings, revoke the WordPress API key through your site, remove Google access through your Google account permissions, or uninstall WPPS to remove its local extension data. Clearing the OAuth client ID only clears the cached token; it does not itself revoke Google's authorization grant.

In Pinterest Studio, use the source-image clearing control to clear source images and generated pins from the current draft. This does not reset all text and design preferences, so edit those fields separately as needed. Uninstalling the extension removes its local extension storage, including the Pinterest Studio draft. Downloaded WebP and ZIP files must be deleted separately from your device. Closing Pinterest Studio does not, by itself, delete the saved draft.

Manage or delete uploaded images and posts in the relevant WordPress, Blogger, or Cloudinary account. For license-service records, WhatsApp purchase records, payment confirmations, or support information we control, contact wppsextension@gmail.com. We may request limited information to verify ownership before completing a request. Depending on applicable law, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of your personal information. Deleting a WhatsApp message or uninstalling WPPS does not automatically delete sales or license records held separately by us or transaction records held by your payment provider. Some records may need to be retained for legal, accounting, payment-dispute, or security reasons; we will explain applicable limitations.

8. Processing locations

Connected services and hosting providers may process information in countries different from your own. The location and protections for information processed by those providers depend on your service configuration and their terms. Contact us for information about the processing of licensing records we control.

9. Changes and contact

We will update this policy when our data practices change and revise its effective date. Where required, we will provide additional notice or request consent before materially changing how information is collected or used.

For privacy questions or data requests, contact:

Saabas Technologies
wppsextension@gmail.com