ContentApp connects to your brand's social media accounts and holds the posts, images and videos you create. Here is how we protect your account, your content and your connections.
All traffic uses TLS (HTTPS), and your account data and media are encrypted at rest on Cloudflare's storage.
You sign in with your Google account, protected by Google's own security, including two-step verification if you use it. ContentApp never sees or stores a password.
Each social account is connected through the platform's own sign-in and permission screen, so ContentApp never sees your social media passwords. Posts are published only when you choose, and you can disconnect any account at any time.
Your prompts, posts, images and videos are used only to deliver your results. ContentApp does not use them to train AI models, and we never sell your data.
On team plans, the owner controls who joins, admins manage members and connections, and members create and post. Each item records who created it, and removed items go to a Recycle Bin rather than disappearing.
When our team opens an account to help a user, the access is time-limited, shown on screen with a banner, and written to an audit log.
Your data is stored in Cloudflare's Asia-Pacific region (Singapore) and served over its global network, with DDoS protection, a web application firewall and continuous monitoring.
Billing is processed by Stripe, a PCI DSS Level 1 provider. We never see or store your card details.
We follow the Singapore Personal Data Protection Act. Our Privacy Policy explains what we collect and why, and a Data Processing Agreement forms part of our Terms of Service.
ContentApp is hosted on Cloudflare, which maintains independent, audited security certifications, including SOC 2 Type II and ISO 27001. Payments are processed by Stripe (PCI DSS Level 1).
AI generation uses selected providers for text, images and video, and posts are delivered to LinkedIn, X, Instagram, Facebook and TikTok through our publishing partner, Post for Me; YouTube uploads go directly through Google's YouTube Data API. When you generate content, your prompt is sent only to the provider that creates the result.
The complete list of sub-processors, with the purpose and location of each, is published in Schedule 1 of our Terms of Service.