Pan Card Centre AutoPost

Privacy Policy

This policy describes the private AutoPost tool used for Pan Card Centre social publishing. It does not describe the separate PAN application assistance service or documents that customers may send through WhatsApp.

Information accessed

The application requests access only to support those account discovery, verification and publishing functions. It does not request or process PAN applicant documents, PAN numbers, payment details, or customer application data.

Information stored and use

Server-side records can include OAuth access and refresh tokens, granted scopes, account and location identifiers and names, the selected destination, and connection timestamps. Publishing records can include the scheduled date, topic, channel status, provider post identifiers and links, and error or recovery details. The tool does not request a Google email address or general Google profile data.

Authorization records and publishing records are stored in a Cloudflare D1 database for use by the private dashboard and approved publishing workflow. Provider client credentials are configured as Cloudflare Pages secrets; missing credentials must be supplied by the account owner through Cloudflare before provider connections can be used. OAuth tokens are encrypted by the application before they are stored, and token values are not returned to the browser. No automatic expiry of publishing history is configured; it remains in the connected database until the operator removes it.

Sharing

When publishing is enabled, the selected platform receives the post text and media needed to publish and displays them according to that platform’s settings. Google and Meta process account connections and content under their own terms and privacy notices. Cloudflare hosts the website, functions and connected D1 database. If the operator configures an external failure-alert webhook, it receives the scheduled date and a failure or recovery summary; the application is designed not to include OAuth tokens or client secrets in those alerts. No advertising profile is created by AutoPost.

Retention, revocation and deletion

An administrator can use Disconnect Meta or Disconnect Google accounts in the protected dashboard. This removes the corresponding locally stored authorization records and attempts to revoke the provider grant. Google revocation applies to all OAuth scopes previously granted to this project, so the Google action removes both YouTube and Business Profile authorization records. If the dashboard cannot confirm provider revocation, the account owner should also remove the app from the provider account’s security or connected-app settings. Disconnecting does not erase publishing history; the site operator must separately remove that history from the connected Cloudflare D1 database.

Revoking access in a provider account prevents future authorization but does not by itself remove records already stored by this application. For help with AutoPost data, contact Pan Card Centre at 8328177065 on WhatsApp.

Contact and scope

Pan Card Centre operates this private tool for its own social accounts. For questions about this policy or AutoPost data, contact Pan Card Centre through the number above. This policy is specific to AutoPost and does not replace the privacy notices of Google, Meta, Cloudflare or WhatsApp.