Security
How we protect your data
Relay Port holds the keys to your Instagram accounts, so we keep what we store small and protect it. This page says what is in place today and what is not.
Access tokens
- Instagram access tokens are encrypted at rest with AES-256-GCM, using versioned keys so a key can be replaced without losing access.
- Tokens are stored apart from other data and are never returned by our API.
- Disconnecting an account deletes its token immediately.
Instagram access
- You connect an account through Instagram API with Unified Login, and Meta shows you its own consent screen.
- We ask for two permissions only: instagram_basic to read the basic profile, and instagram_content_publish to publish content.
- Callbacks from Meta are signed, and we verify the signature before we act on them.
Your media
- Uploaded images and videos live in private storage.
- When Instagram needs to fetch a file to publish it, we serve it through a signed link that expires.
Accounts and workspaces
- API keys are stored only as hashes and are shown once, when you create them.
- Passwords are stored as salted, peppered hashes.
- All traffic uses HTTPS.
- Each workspace's data lives in its own sharded store, and requests are scoped to the caller's workspace.
Retention and deletion
- How long each kind of data is kept is listed in section 7 of the privacy policy.
- You can delete a connected account, delete the content of the whole workspace with Delete my data, or ask by email.
Sub-processors
- The companies we use to run the service, what each one does and where, are on the sub-processors page.
What we do not have yet
- We do not have a SOC 2 report.
- We do not have ISO 27001 certification.
- We do not offer single sign-on (SSO) yet.
Report a vulnerability
If you think you have found a security problem, email us with the steps to reproduce it. Please give us a reasonable time to fix it before you share it publicly, and do not access data that is not yours.
Email the security teamsecurity@relayport.dev