HeyPostForMeContinue with Google
Public policy

Privacy, without vague promises.

This policy explains the information HeyPostForMe handles, why it is needed, where it is kept, and how a person can disconnect a social account or request deletion.

Version 1.2 · effective 17 September 2026

Who operates HeyPostForMe

HeyPostForMe is operated by Mavlay, its registered parent enterprise in India. HeyPostForMe (“we”, “us”) provides a publishing desk at heypostforme.com. Questions about this policy or a data request can be sent to privacy@heypostforme.com.

Identity and sessions

Google supplies identity information needed to sign in: a stable account identifier, verified email address, display name, and profile image when available. HeyPostForMe creates its own opaque session and stores only its hash. A Google refresh token is not retained for product sign-in.

Publishing information

HeyPostForMe stores the work a user asks it to preserve: workspace membership, exact Unicode captions, immutable revisions, media references, selected covers, schedules, destination choices, delivery attempts, provider receipts, errors, retries, and audit events.

Instagram delegation

When a workspace owner connects Instagram, HeyPostForMe receives the professional account ID, username, account type, granted scopes, token expiry, and an access token. Tokens are encrypted and versioned on the server, never returned to the browser, and used only for the actions the account controller approved.

Facebook Pages status

Facebook Pages is not currently available as a HeyPostForMe publishing destination. HeyPostForMe does not currently ask customers to grant Page discovery or publishing access and does not offer a Facebook Page connection in the product.

The application contains a default-closed shared Meta lifecycle foundation for a possible future reviewed Facebook Pages connector. Before any such connector is offered, this policy and the connection journey must identify the exact permissions, selected Page information, encrypted credential custody, removal behavior, and deletion behavior that are actually released.

Threads delegation

HeyPostForMe requests threads_basic to identify the exact Threads profile a user connects and threads_content_publish to publish only the post or media that user explicitly sends or schedules. A reply chain additionally requires threads_manage_replies; ordinary publishing access is never treated as reply permission.

HeyPostForMe stores the profile ID, username, display name and profile image when supplied, granted scopes, token and grant expiry, an encrypted access token, and the post, media-container, status and reconciliation evidence needed to prevent duplicate publishing. An Instagram connection never substitutes for a Threads connection.

LinkedIn delegation

Connecting LinkedIn is separate from signing in to HeyPostForMe. HeyPostForMe requests openid and profile for LinkedIn's consent and current member identity, and w_member_social to publish only content that a user explicitly sends or schedules.

HeyPostForMe stores the confirmed member author identifier returned by LinkedIn's OpenID profile, display name and profile image when supplied, granted scopes, token expiry, an encrypted access token, and the post, image, video and status evidence needed to prevent duplicate publishing. It does not retain the LinkedIn email address and does not use this access to browse unrelated LinkedIn content.

YouTube delegation

Connecting YouTube is separate from signing in to HeyPostForMe. HeyPostForMe requests youtube.readonly to identify the exact channel selected during connection and to read the status, processing, and quality of videos that HeyPostForMe uploaded. It requests youtube.upload to upload only the video and optional thumbnail that a user explicitly schedules for that channel.

Only a workspace owner or admin can connect a YouTube channel. HeyPostForMe stores the channel ID, channel name and handle, the channel profile image when available, granted scopes, token type and access-token expiry, encrypted access and refresh tokens, uploaded video ID and link, and the processing or receipt evidence needed to show what happened. It does not use this access to browse, edit, or delete unrelated YouTube content, for advertising, to determine creditworthiness, or to train a general-purpose AI model.

The delegated access and refresh tokens are retained because a scheduled upload must still be authorized at the moment it runs. HeyPostForMe never initiates publishing without an explicit instruction from an authorized workspace user.

Media and infrastructure

Original media and generated variants are stored in a private, HeyPostForMe-isolated AWS S3 bucket. Short-lived signed URLs are used only for a specific upload, preview, or provider fetch and are not stored as permanent links. Product logic, registers, queues, and scheduling run on isolated Cloudflare resources, including D1.

Why information is used

  • Authenticate people and enforce workspace permissions.
  • Preserve and schedule the exact post a user authored.
  • Publish to explicitly selected social accounts.
  • Prevent duplicates, reconcile uncertain provider outcomes, and show a permanent delivery history.
  • Secure the service, enforce plan allowances, investigate failures, and meet legal obligations.

Services that receive limited information

Google processes product sign-in. Google and YouTube process a separately authorized YouTube connection, video upload, thumbnail upload, and exact-video readback. Meta processes separately authorized Instagram and Threads connection, publishing, and provider lifecycle requests when those destinations are available and a user connects one. Facebook Pages is not currently offered as a customer destination. LinkedIn processes its separately authorized member connection, media upload, publishing and exact-post readback when that destination is available and a user connects it. Cloudflare hosts the application runtime, encrypted delegated credentials, database, scheduling, and delivery coordination. AWS stores private media. Gumroad may process checkout and billing when a person chooses a paid plan; HeyPostForMe stores only normalized subscription evidence needed to apply the plan, not card details. These services handle information under their own terms and privacy notices.

HeyPostForMe uses information received from Google APIs only to provide the visible YouTube connection, publishing, status, and receipt features a user requests. This use follows the Google API Services User Data Policy, including its Limited Use requirements. Google's own handling is described in the Google Privacy Policy.

Sharing, transfer and disclosure of Google user data

HeyPostForMe does not sell or rent Google user data. It does not disclose Google user data for advertising, retargeting, credit assessment, or data-broker services, and it does not use Google user data to develop or train generalized artificial-intelligence or machine-learning models.

Google user data is disclosed only as necessary to provide or secure the features a person asked for:

  • Cloudflare, Inc. is HeyPostForMe's application-hosting, database, queue, and delivery-coordination provider. It processes limited Google identity information, encrypted YouTube OAuth credentials, channel metadata, and operational records in that capacity.
  • Google and YouTube receive authorization requests, API requests, and the video and associated metadata that a person explicitly directs HeyPostForMe to publish.
  • Information may be disclosed where reasonably necessary to investigate abuse or a security incident, protect the service or the people who use it, or comply with applicable law. Any such disclosure is limited to what that purpose requires.

Amazon Web Services stores media that a person uploads directly to HeyPostForMe for publishing; it does not receive Google OAuth credentials. Gumroad processes billing when a person chooses a paid plan; it does not receive Google OAuth credentials or YouTube account information. HeyPostForMe does not disclose Google OAuth credentials or Google-derived account metadata to Meta or Instagram.

HeyPostForMe does not otherwise transfer or disclose Google user data to third parties.

How sensitive data is protected

HeyPostForMe protects Google user data with HTTPS/TLS while it is in transit. YouTube OAuth access and refresh tokens are encrypted at the application layer using AES-256-GCM before storage. Every ciphertext uses a fresh initialization vector and is cryptographically bound to its record purpose. Credentials are stored with a key-version identifier to support controlled key rotation. The encryption key is stored separately from the encrypted credentials as a restricted Cloudflare Worker secret; it is not held in the database and is not present in source control.

Provider credentials are never returned to the browser. Application logging is designed to exclude OAuth access and refresh tokens, and operational failure records are limited to information needed to diagnose and reconcile delivery without storing those credentials. HeyPostForMe's own product sessions are opaque and stored only as hashes.

Access to connected-channel controls is enforced through an authenticated HeyPostForMe session and workspace role: only a workspace owner or admin can connect, confirm, or manage a YouTube channel. HeyPostForMe requests only the permissions the visible user-facing functionality needs, and does not request Gmail, Drive, Calendar, or Contacts access.

Media a person uploads is held in private storage and reached only through short-lived, purpose-specific signed URLs rather than durable public links. Disconnecting a YouTube channel makes its stored delegated credentials unusable, and eligible Google-derived data is deleted or irreversibly redacted through the documented deletion process, subject to the narrowly required security, fraud, billing, and legal records described under Retention.

Retention

Active account, content, media, and delegated-connection data is retained while needed to provide HeyPostForMe. A YouTube disconnect immediately deletes or irreversibly redacts the local credentials, scopes, channel identity, and provider-derived receipt details for that connection. One encrypted token may be held only while HeyPostForMe attempts or reconciles Google grant revocation. It is erased after confirmation, a definitive failure, the bounded retry limit, or no later than the seven-day revocation deadline. User-authored Posts and provider-free schedule and attempt history remain so a user can audit what happened. A separate HeyPostForMe account-deletion request starts a seven-day safety hold and can be cancelled during that window. The current account-deletion workflow records and lists the held request but does not automatically execute when the hold ends. A request is not reported as completed unless a reviewed deletion process performs and records it. When deletion is completed, narrowly required security, billing, fraud, and legal evidence may be retained only for the period required by the applicable purpose or law.

Control and deletion

A workspace owner or admin can disconnect a social account. Disconnecting closes usable local provider access, revokes the stored scopes, and stops future publishing after active work is resolved. Content already published at a social platform remains under that account's controls. Removing HeyPostForMe through Threads sends a signed deauthorization request; a separate signed Meta data-deletion request removes the matching provider-derived account data and returns a confirmation code and status link. Facebook Pages is not currently connectable. Removing HeyPostForMe in Instagram also sends a signed provider deletion request whose signature is verified before its delegated credential, scopes and Meta-derived account fields are removed.

Disconnecting YouTube additionally removes its local Authorized Data and attempts to revoke the Google grant when that can be done safely. The connection truthfully shows whether provider revocation completed, is in progress, or requires manual removal from Google Account security settings. Videos already uploaded to YouTube are not silently deleted. A signed-in person can submit and cancel a separate HeyPostForMe deletion request during the safety hold.

Open the data-deletion instructions and controls.