Back to Home
Amplypost

Privacy and data use

Privacy Policy

for Amplypost

Last Updated: October 2, 2026

Thank you for using Amplypost ("we," "us," or "our"). This Privacy Policy outlines how we collect, use, share and retain your personal information when you use our website located at https://amplypost.com (the "Website"), our connected services, and the Amplypost plugin in ChatGPT or another connected AI client.

Read about ChatGPT tool data, data retention and your controls below.

1

ChatGPT and Connected AI Clients

This policy covers the Amplypost plugin in ChatGPT and other AI clients connected to Amplypost. When you authorize a connection, Amplypost associates it with your account and stores authorization and permission records. Read permission allows the client to retrieve account information, connected accounts, posts and saved hashtags. Publish permission allows media uploads and immediate or scheduled publishing. Optional offline access lets the client renew access without asking you to sign in each time.

Amplypost receives the arguments and selected attachments sent with a tool request, together with authorization information. The tools do not request your full ChatGPT conversation history. Tool results are sent back to OpenAI or the AI client you connected so it can answer your request. If you grant the optional identity and email permissions, identity responses can also include your email address and email verification status.

Data used by each tool

get_current_user

Received: Your authorized Amplypost connection; no additional input fields.

Returned and why: Your Amplypost user ID, organization ID and timezone, to identify the account used for the request.

list_connected_accounts

Received: Your authorized Amplypost connection; no additional input fields.

Returned and why: Connected account IDs, platforms, names, usernames, profile pictures, permission scopes, platform settings, connection status, token expiry information and record dates, to select publishing destinations. Social platform token values are not returned.

list_hashtags

Received: An optional platform filter.

Returned and why: Saved hashtag IDs, titles, hashtag text, platforms and record dates, to reuse your saved hashtags.

list_posts

Received: Pagination and optional status, platform, post type, account, group and creation-date filters.

Returned and why: Post and group IDs, platforms, post types, story flags, statuses, schedules, timezones, publication and record dates, plus pagination, to find posts and check progress.

get_post

Received: The Amplypost post ID you want to retrieve.

Returned and why: Post content, caption, media URLs and metadata, destination account ID, account name and profile picture, published URL, schedule, timezone, status, publishing attempts, errors and record dates, to inspect the post and its outcome.

upload_media

Received: The selected image or video attachment, its download URL and file ID, and optional filename and media type. Amplypost downloads and stores the file for publishing.

Returned and why: A public media URL, media and file types, file size, dimensions and video duration when applicable, to preview the file and attach it to a post.

create_post

Received: Selected account IDs and platforms, captions, media URLs and metadata, story options, platform-specific publishing settings, and an optional scheduled date and timezone. Platform settings can include titles, descriptions, tags, links, alternative text, audience and interaction choices.

Returned and why: A queue acknowledgement, group and post IDs, stored post content and media references, destination accounts, schedules, statuses and publishing records. These results confirm queuing; publication happens separately.

Uploaded media is accessible by public link

Uploading an attachment copies it to Amplypost media storage. Anyone with the resulting URL can access the file, even before a post is published. Publishing sends your selected content and settings to the destination social platforms. Avoid uploading files that must remain private.

Sign in and connect social accounts through Amplypost's authorization pages. Do not put passwords, sign-in codes, API keys or payment card details into tool inputs. The tools do not need these details to create posts.

2

Information We Collect

Account and service data

We collect the following personal information from you:

  • Name: We collect your name to personalize your experience and communicate with you effectively.
  • Email: We collect your email address to send you important information regarding your account, updates, and communication.
  • Account and workspace information: User and organization IDs, workspace membership, timezone, sign-in and verification records help us authenticate you and keep your organization's content accessible to authorized users.
  • Billing information: Subscription status, payment references and transaction records help us manage your plan and billing. Payment checkout is handled by our payment provider.
  • Connected social accounts: We store platform account IDs, names, usernames, profile pictures, permissions, connection settings and authorization tokens to access the accounts you connect and publish your posts.
  • Content and publishing records: We process captions, saved hashtags, images, videos, media URLs and metadata, destination accounts, platform settings, schedules, timezones, publishing results and errors to prepare, schedule and manage posts.
  • Social media analytics: We retrieve account and post performance data from supported connected platforms to display analytics in your dashboard.
  • Support messages: We use information you send to support to investigate issues and respond to your requests.

Website, session and device data

Session records may include your IP address and browser information. Cookies and browser storage support sign-in and preferences. Our website also uses DataFast, Google Analytics when configured, and the TikTok Pixel for page-view measurement, usage analysis and marketing measurement. These services may receive IP addresses, browser and device information, page URLs, referrers, cookie identifiers and visit events. This information can be personal data. Browser settings can block cookies and tracking requests; blocking essential cookies can prevent sign-in.

3

Purpose of Data Collection

We use the information described above to authenticate users, enforce account permissions, manage subscriptions, store and publish content, show publishing status and analytics, provide support, troubleshoot failures and protect the service. Website measurement helps us understand usage and marketing performance. When you use AI text generation in the website, we send your prompt, post type and any existing caption you supply to Google Gemini to generate or improve text. The generated text is returned to you and becomes post content if you use it.

4

YouTube API Services

Amplypost uses YouTube API Services to enable cross-posting functionality to YouTube. By using our service to interact with YouTube, you are also subject to the YouTube Terms of Service.

5

Google Privacy Policy

As we use YouTube API Services, your data may also be subject to Google's Privacy Policy. For more information on how Google collects and processes data, please refer to the Google Privacy Policy.

6

Google User Data Retention and Deletion

Amplypost retains Google user data only for as long as necessary to provide the services requested by the user, such as connecting a YouTube channel and publishing or managing scheduled content.

When a user disconnects their Google account from Amplypost, we delete stored Google OAuth access and refresh tokens associated with that connection and cease accessing the user's Google account.

Users may also request deletion of their Google-related data by contacting us at support@amplypost.com. Upon receiving a valid deletion request, we will delete the associated Google user data from our active systems within 30 days, except where retention is required by law or necessary for legitimate security, fraud-prevention, or compliance purposes.

Deleting an Amplypost account will also result in deletion of Google user data associated with that account, subject to the same limited legal and security exceptions.

Amplypost does not sell Google user data or use Google user data for advertising purposes.

7

Data Sharing

Data is disclosed to the following recipients for the features you use:

  • Connected platforms: the social networks you select receive content, media and publishing settings to publish and manage posts. Canva processes design browsing and export requests when connected.
  • OpenAI or another connected AI client: receives the tool results described in the ChatGPT section below when you use the integration.
  • Storage and infrastructure providers: process application records and requests to host and operate Amplypost. Cloudflare R2 stores uploaded media.
  • Billing and email providers: Dodo Payments processes subscription checkout and billing; Amazon Simple Email Service processes recipient addresses and message content for account and service emails.
  • AI and website measurement providers: Google Gemini processes requested text generation; DataFast, Google Analytics and TikTok receive the website measurement data described above.
  • People with access: authorized members of your Amplypost organization can access shared workspace content. Published posts are visible to their platform audience. Anyone with a public media URL can access that file.

Recipients operating their own services, including OpenAI and social platforms, handle their copies under their own policies and account settings.

8

Children's Privacy

Amplypost is not intended for children, and we do not collect any data from children.

9

Updates to the Privacy Policy

We may update this Privacy Policy from time to time. Users will be notified of any changes via email.

10

Contact Information

If you have any questions, concerns, or requests related to this Privacy Policy, you can contact us at:

11

Data Protection Mechanisms

We take the protection of your sensitive data seriously and have implemented the following security measure:

a) Encryption

Your Google OAuth access keys are encrypted using industry-standard encryption protocols both in transit and at rest.

While we implement this security measure to protect your sensitive information, please be aware that no method of transmission over the Internet or method of electronic storage is 100% secure. We strive to use commercially acceptable means to protect your personal information, but we cannot guarantee its absolute security.

12

Canva Integration and Customer Data

When you connect Canva, Amplypost uses the permissions you grant to display your available designs and, where authorized, your Canva display name. Design information may include design IDs, titles, thumbnails, page counts, editor links, and supported export formats. When you choose to add a design, we export the selected pages in your chosen format and import the resulting images or videos for use in your Amplypost posts.

Data retention policy

We retain your Canva connection details and encrypted authorization tokens while your account remains connected, so you can browse and import designs without reconnecting each time. We store export records, including design IDs, formats, and references to imported media, to process your selections and avoid duplicate imports when you retry.

Imported images and videos are stored separately from your Canva connection for use in drafts, scheduled posts, and published content. Disconnecting Canva does not automatically remove these files or content you have already added to Amplypost.

Data archival and removal policy

You can disconnect Canva from your connected accounts in Amplypost. On successful disconnection, we remove the stored Canva connection, access and refresh tokens, and associated export records. This ends Amplypost's access through that connection. Removing an Amplypost user account also removes its associated Canva connection and export records from our database.

To request removal of imported Canva media or other customer data, contact support@amplypost.com. We verify requests before processing them to protect your account. Please identify whether you want to remove your Canva connection, imported files, or your Amplypost account. Any data that must be retained for legal or security reasons is subject to those obligations.

Disconnecting Canva or removing data from Amplypost does not delete your original Canva designs or posts already published to social media. Those copies must be managed on the relevant platform. Copies cached or downloaded outside Amplypost may remain available independently.

Data storage policy

Canva connection and export records are stored in our server-side database and associated with your Amplypost account. Canva access and refresh tokens are encrypted using AES-256-GCM before database storage. The encryption key is supplied through server configuration separately from the stored token values. Canva API requests and export downloads use HTTPS, and integration requests require an authenticated Amplypost session.

Imported images and videos are stored in Cloudflare R2 object storage and served through Amplypost's media URLs for previews and publishing. These media URLs are accessible to anyone who has the link. Files may also be held temporarily on our server while an import is processed; unsuccessful imports can leave temporary files pending cleanup. Canva tokens are handled by the backend and are not returned to the asset picker.

13

How Long Data Is Kept

  • Account and content records: account, workspace, connected-account, post and saved-hashtag records are retained to operate your account and provide publishing history. Successful account deletion removes these records from the active database, together with authentication sessions, plugin authorizations and account billing records.
  • Plugin access: an issued access token expires after 15 minutes. Refresh access and consent records support continued use while authorized. Token expiry ends that token's use; it does not delete posts, media or other account data. Revoking refresh access does not immediately invalidate an already issued access token, which can remain valid until expiry.
  • Uploaded media: files are stored separately from database records and do not automatically expire through the upload feature. Disconnecting ChatGPT, deleting a post or deleting your account does not automatically remove the stored file. Contact support with the media URLs to request removal. Plugin media responses allow caching for up to one year; cached or downloaded copies can remain after removal from storage.
  • Temporary plugin uploads: the upload process removes its temporary server files when processing finishes or fails. The uploaded copy in media storage remains as described above.
  • Google and Canva data: the integration-specific retention and removal rules in this policy also apply.

Deletion from Amplypost does not remove copies already sent to OpenAI, other AI clients, payment providers or social platforms. Their retention policies and controls apply to those copies. Disconnecting a client does not cancel posts already queued in Amplypost.

14

Your Choices and Data Requests

  • Choose what to send: select only the content, attachments and destination accounts needed for your request. Review the permissions on the authorization screen before connecting an AI client.
  • Disconnect integrations: remove the Amplypost connection in your AI client and disconnect social platforms in Amplypost's Connected accounts. You can also revoke authorization through the relevant platform. For help revoking plugin access, contact support.
  • Manage your account: update your name in Settings. The organization owner can use Delete account there to remove the organization and its users, workspaces and database records. This affects everyone in the organization. Deletion may require a retry if publication is in progress or subscription cancellation fails.
  • Request access, correction or removal: email support@amplypost.com from your account email. Identify the account and the records or media URLs involved. We verify requests to protect account data. Organization members who cannot delete the organization can contact support about their own information.
  • Control website tracking: use your browser's cookie and tracking controls. These controls apply to the website; disconnecting the ChatGPT plugin does not change website cookies.
  • Manage copies elsewhere: use the relevant AI client or social platform's controls for its chat history, published posts and stored copies.

Questions About Your Data?

Contact support@amplypost.com for privacy questions and data requests.