Official authorization
Supported accounts are intended to connect through official OAuth or an equivalent provider flow. Socimie does not ask users to provide their native social-platform password.
Security & access
Powerful access should remain controlled access.
Socimie is designed around authorized connections, purpose-limited platform access, protected credentials, user control, and transparent data handling.
Permission discipline
Connections should request only the permissions needed for the functions a user enables. Scope, account eligibility and provider review remain visible constraints.
Credential and token handling
The data model contains a backend-only credential placeholder, but production token encryption, key management, rotation and sanitized provider-error handling are not implemented. They are launch requirements—not current claims.
Workspace isolation
Current application records are scoped to a workspace. API routes verify workspace membership and services repeat trusted workspace filters so caller input cannot replace the tenant boundary. Production authentication is still required before public access.
Data minimization
Socimie is designed to access and retain only data needed for enabled workflows, connection support, security, auditability and applicable obligations. Category-specific retention rules still require legal review.
Access revocation
A production release must let users disconnect supported accounts. Users can also revoke authorization through the provider; revocation should stop future access even when retained data needs a separate deletion request.
Data deletion
Users can request deletion of associated Socimie and connected-platform data. Verification may be required, and the response must not disclose whether an account exists.
Open data-deletion instructionsResponsible intelligence
Recommendations inform people. They do not silently take control.
Socimie keeps prediction, explanation and execution separate so consequential actions remain reviewable.
Recommendations are advisory and are not provider decisions.
No autonomous budget, publishing or policy mutation is implemented.
No raw-data resale, unrelated surveillance or sensitive-trait inference.
No scraping to bypass provider restrictions or API limits.
Security reporting
Report a suspected security issue.
Use the contact route and choose Security. Do not include passwords, access tokens or sensitive provider payloads in the initial message.
Security contact: security@socimie.com
Choose your next step
Bring connected intelligence under clear human control.
Compare capacity-led plans for secure, transparent social and advertising workflows.