Content for more than 9,000 brands is managed in Gain. We don't take that responsibility lightly.

Gain runs on Heroku and AWS, stores and processes all data in the United States, encrypts it in transit and at rest, and connects to the networks you publish to without ever storing your passwords. You rely on us to protect your data and the reputations of your brands and their customers. Here is exactly how we do it.

99.95%
average platform uptime
8M+
posts published through Gain
Zero
major security incidents to date
US
all data stored & processed stateside
Infrastructure

Gain's main infrastructure is hosted on Heroku, Salesforce's cloud application platform, which runs entirely within Amazon's secure AWS data centers. Gain also uses AWS directly, such as Amazon S3 for uploaded media. Those data centers are ISO 27001 and FISMA certified, with multiple layers of physical protection.

Managed network firewalls provide automatic DDoS mitigation, spoofing and sniffing protection, and automatic blocking of port-scanning attempts. Gain runs inside its own isolated cloud environment.

Data security

All of Gain's data is stored and processed in the United States. Some data may be cached briefly on a global content delivery network (CDN) for speed. Data is encrypted in transit with TLS 1.2 or higher everywhere, and our databases are encrypted at rest with AES-256.

Passwords are stored using the PBKDF2 algorithm with a SHA256 hash, individual random salting, and over a million hashing iterations.

Backups & recovery

Every database change is continuously backed up, so we can restore to any point in the last 7 days.

Daily, weekly and monthly backups are kept for 7 days, 8 weeks and 12 months, encrypted and stored only in the US. We run recovery drills at least every six months.

Privacy

When you cancel, Gain keeps your data for 12 months in case you reactivate, then deletes it. You can request complete deletion at any time, and we complete requests within 30 days.

We don't hand data to law enforcement unless a law, court order, or regulation compels us, or it's needed to establish or defend legal rights or protect someone's vital interests. To date, Gain has never received such an order.

Permissions

Our product architecture keeps content for different brands completely separate. Your client will never see another client's content, no matter how many brands you manage under one account.

Permission-based access covers everyone in your collaboration circle. You control what each person can see and do, per brand.

Sign-in

Every user can enable two-step verification for an extra layer of account protection. Login attempts are rate-limited against brute-force attacks, weak or common passwords are rejected, and you get an email whenever your password changes.

External reviewers can sign in with a short-lived, one-time-use link sent to their email, with no password needed.

Best practices

Gain follows web security best practices and is constantly tested against the latest vulnerabilities and attacks outlined in the OWASP Top Ten and others. Every code change is reviewed by a senior engineer, and automated dependency and secret scanning runs on all our code.

We run automated penetration tests at least every six months, and our bug bounty program routinely pays security researchers for responsible disclosures.

Access & personnel

Staff access to customer data is need-to-know and least-privilege, reviewed monthly. Multi-factor authentication is mandatory on every system our team uses.

Every work device is managed and encrypted, and all staff sign confidentiality agreements and complete security training each year.

API integrations

Connections to Instagram, YouTube, TikTok, Facebook, LinkedIn, X (Twitter), Threads, Pinterest and Google Business Profile use each network's official authentication APIs over OAuth 2.0, so Gain never sees your passwords. Access tokens stay in our encrypted database and never leave our servers.

We will never use social APIs in ways that violate the networks' terms of service.

Third parties & AI

Every provider that receives customer data is approved by our CTO, gets only the minimum data it needs, and is contractually barred from selling it.

Third-party AI services may not use your data to train their models, and our engineers' AI tools never see production data or credentials.

Payments

Gain uses Stripe for all billing and payment functions. Stripe is audited by a PCI-certified auditor and certified to PCI Service Provider Level 1, the most stringent level available in the payments industry.

No card data ever touches Gain's servers. We complete an annual PCI DSS self-assessment (v4.0.1) and can share our attestation on request.

Support & incident response

If we discover a breach, we alert customers immediately on our status page, contact account owners directly, and post constant public updates. Affected users are notified of any serious personal-data breach within 72 hours, and every incident ends with a full root-cause report. To date, Gain has had no major security incidents.

Our support team is available for live help and expedited solutions.

Reliability, battle-tested.

Over 13 years of real-world experience under load. We scale Gain horizontally as traffic grows and monitor performance under heavy load constantly, so it stays responsive no matter how many people are on it.

Check live system status any time at status.gainapp.com.

Over 125,000 posts published per month
More than 8 million posts sent to social networks to date. Some single accounts handle over 6,000 posts a month, with thousands of users under one account.
Every post pre-checked before it publishes
Content is automatically validated against each network's specs, so errors surface before publishing rather than after.
Failed posts retry automatically
If a post fails, you're notified with a direct link to it, and Gain retries automatically up to three times within ten minutes.
99.95% average uptime
Maintenance downtime is communicated weeks in advance. Enterprise customers get SLAs guaranteeing reliability and support levels — ask our support team.
Facebook native scheduling, optionally
For Facebook you can publish through Gain's engine or hand scheduling to Facebook's own. Edits made in Gain still flow through to Facebook's scheduler. Gain also checks that Facebook publishes on time, and retries from Gain's side if it doesn't.

Your approval record is part of your security posture.

A lot of content risk has nothing to do with hackers. It comes from content that publishes before sign-off, or a file that reaches the public without clearing legal review. Gain handles this in the structure of the product: content publishes only after it clears its approval workflow, and every decision is time-stamped and downloadable.

Teams that need sign-off before publishing keep that record as their audit trail. See how the record works →

What auditors ask · what Gain answers
"Who approved this?"
The named approver, with a time stamp.
"Did they approve what actually went live?"
Approvals attach to the exact content that was reviewed. If someone edits it after approval, the workflow starts again.
"Could it have published without sign-off?"
Publishing is gated on the workflow, so content cannot go out until it clears approval.
"Can we have it in writing?"
The full history exports as a time-stamped report, for a single item or an entire client.

Quick answers

All of Gain's data is stored and processed in the United States, hosted on Heroku within Amazon Web Services data centers. Those data centers are ISO 27001 and FISMA certified, with multiple layers of physical protection. Some data may be cached briefly on a global content delivery network (CDN) for speed.

Yes. Every user can enable two-step verification (also called two-factor authentication) for an extra layer of protection. It comes alongside permission-based access for everyone in your collaboration circle, and complete separation between brands. SSO is available on the Enterprise plan.

No. Connections to Instagram, YouTube, TikTok, Facebook, LinkedIn, X (Twitter) and the rest use each network's official OAuth 2.0 authentication. Gain never sees or stores those passwords and will never ask you for them directly.

User passwords are stored using the PBKDF2 algorithm with a SHA256 hash, individual random salting, and over a million hashing iterations. Nobody at Gain can read them.

Yes. When you cancel, Gain keeps your data for 12 months in case you reactivate, then deletes it. You can request complete deletion at any time at privacy@gainapp.com or by online request form at gainapp.com/privacy-request, and we complete requests within 30 days. See the Privacy Policy for retention details.

To date, Gain has had no major security incidents and has never received an order for customer data from a law enforcement organization. We only hand over data where a law, court order, or regulation compels us, to establish or defend legal rights, or to protect someone's vital interests. If a serious breach of personal data ever happens, we commit to notifying affected users within 72 hours.

Gain's infrastructure runs in AWS data centers certified to ISO 27001 and FISMA, and Gain completes an annual PCI DSS self-assessment. For Gain's own compliance documentation, download the Security and Reliability Overview, or contact us any time with security-related questions. We actually like talking about this.

Want the nitty-gritty?

Download the full Security and Reliability Overview, or write to us — we actually like talking about this.

Download PDF

Enterprise requirements? Covered.

SSO login, uptime SLAs, contract billing, volume plans, and approval training for your stakeholders all come with the Enterprise plan.