Loading…
Security & Data Handling
Socioverse stores application data in a managed PostgreSQL database in Singapore (ap-southeast-1), encrypts Instagram access tokens at the application layer with AES-GCM, and enforces workspace isolation in the database itself through PostgreSQL Row Level Security rather than in application code.
Features
- Data residency: Singapore (ap-southeast-1) for the application database
- TLS 1.2+ in transit, encryption at rest, AES-GCM on Instagram tokens
- Row Level Security enforces tenant isolation at the database layer
- API keys scoped to one workspace and to named permission scopes
- Card details never touch Socioverse servers - handled by Dodo Payments and Razorpay
- Point-in-time database recovery from continuous backups
Frequently Asked Questions
- Where does Socioverse store my data?
- Application data is stored in a managed PostgreSQL database hosted by Supabase in the Singapore (ap-southeast-1) region. Uploaded media is served from a global CDN, and the web application is delivered by Vercel.
- How does Socioverse protect my Instagram access token?
- Tokens are encrypted at the application layer with AES-GCM before being written, using a key held only as a server-side secret. A database dump on its own does not yield working tokens. Socioverse never asks for your Instagram password.
- Is Socioverse SOC 2 or ISO 27001 certified?
- No. Socioverse does not currently hold a SOC 2 or ISO 27001 certification and has not commissioned an independent third-party penetration test. If your procurement requires either, ask before purchasing.
- How do I report a security vulnerability in Socioverse?
- Email support@socioverse.io with Security in the subject, including steps to reproduce. Reports are acknowledged within two business days.