Security
How we keep your brand accounts safe
Vinixa connects to the accounts your business depends on. Here is exactly what we do to protect them — the practical measures in place today, described plainly.
Measures
What is in place
All traffic to Vinixa is served over HTTPS. Below are the safeguards built into the application itself.
Encrypted access tokens
Access tokens for your connected Facebook, Instagram and Canva accounts are encrypted with AES-256 before they are stored. Encryption keys are kept out of the database.
OAuth 2.0 connections
Meta and Canva accounts connect through their official OAuth 2.0 flows (Canva with PKCE). We never see or store your Meta or Canva passwords, and you can revoke access at any time.
Signed JWT sessions
Sessions use short-lived, signed JSON Web Tokens in httpOnly cookies, with rotating refresh tokens. Only a hash of each refresh token is stored, and reuse of an old token revokes the session.
CSRF protection
State-changing requests made with cookie sessions must carry a matching CSRF token, so other websites cannot act on your behalf.
Rate limiting
Sign-in, payment and general API endpoints are rate limited to slow down brute-force attempts and abuse, and to keep the service fair for everyone.
Verified webhooks
Incoming webhooks from Meta and Razorpay are accepted only when their cryptographic signature checks out against the shared secret.
Account isolation
Every request is scoped to the signed-in account. Access checks ensure you can only reach your own connected accounts, posts, media and analytics.
Data minimisation
We collect only what the product needs, never sell your data, and payment details are handled by Razorpay rather than stored on our servers.
Your controls
You stay in charge
- Disconnect Facebook, Instagram or Canva from Vinixa whenever you like.
- Revoke Vinixa’s access from your Meta or Canva account settings at any time.
- Optional error monitoring only runs if you choose “Accept” on our cookie banner.
- Request a copy or the full deletion of your data — see our Data Deletion Policy and Privacy Policy.
Found a vulnerability?
We take security reports seriously and appreciate responsible disclosure. Please include steps to reproduce, and give us reasonable time to fix the issue before sharing it publicly.