Privacy policy

Who is responsible

For your account and organization settings, QuickPost is the controller. When an organization publishes a client’s content and the client decides the purpose, that organization is the controller and QuickPost processes the data on its instructions. The data processing addendum describes that second case.

Data we store

Name, email, password hash, locale, organization membership and roles. Post text and media you upload. Network account ids, public names and encrypted OAuth tokens. Support tickets. Billing references sent to the payment provider. Cookie choice. We do not store card numbers.

Why

To provide the account, publish the posts you submit, secure the service, bill a subscription, and answer tickets. Optional analytics cookies run only after consent and are not loaded in this version.

Google and YouTube

YouTube access is used to show the channel you connect and to upload the video you submit. Use of Google API data follows the Google API Services User Data Policy, including Limited Use. We do not sell Google user data or use it for ads.

Retention

Tokens stay until you disconnect the account or delete the user. Posts already live on a network until you delete them there. Security logs are kept for the period set on the plan. You can ask for export or deletion of the QuickPost account.

Your rights

Depending on where you live, you can ask to access, correct, delete, restrict, or export personal data, and you can object to some processing. California residents can ask what we hold and can ask us to delete it. We do not sell personal information and we do not share it for cross-context advertising. Canadian requests follow the same access and correction path. Contact the address below. You can also complain to your local authority.

Contact

Email the address shown in the app and on the review page for privacy requests. We may need to confirm you control the account before we delete it.