Security and privacy at eWasl
Your privacy and security come first
Learn how account connections, access-token protection, workspace permissions and data handling work in eWasl.
Account and data protection
Controls for access to accounts, media and external actions.
Access-token protection
Stored social-platform tokens use server-side AES-256-GCM encryption.
- HTTPS connections to the website
- Access tokens kept out of public pages
- Server-side decryption when a platform action needs it
- Separate authorization for private media
Sign-in and sessions
Account and permission checks precede access to private data.
- OAuth for platforms that support it
- Expiring sessions
- Old-session invalidation after password changes
- Revocable API keys and delegated connections
Workspace permissions
Access depends on membership, role and permitted brands.
- Selected-workspace checks
- Member roles and permissions
- Brand-scoped data access
- Account management and deletion settings
Service providers
eWasl uses cloud services to run the application and store data and media.
- Supabase database and authentication
- Cloudflare R2 for migrated media
- Private media originals with authorized access
- Stripe payment processing
Control connections and actions
Review permissions before connecting an application, and revoke access when it is no longer needed.
Account linking
Social platforms grant access through their authorization screens where OAuth is supported.
API keys
Choose permissions when creating a key and revoke it from settings.
AI applications
ChatGPT and Claude connections use separate OAuth resources and scoped permissions.
Action approval
Publishing, replies and moderation through connectors require a separate approval of the exact action.
Data handling and protection
See the privacy policy for details about data use, service providers and retention.
Data collection
The service uses account data, content and media you provide, usage data and platform connection information. Accounts connect through the method each platform supports, and stored access tokens are encrypted on the server.
Data storage
Application data is stored in Supabase and migrated media in Cloudflare R2. Some legacy references and objects remain during the transition. Stripe processes payments; we may retain invoice and subscription identifiers, without full card numbers.
Data sharing
Data needed to carry out your request goes to the services used for that action, such as social platforms for publishing and AI model providers for generation. Review the privacy policy and requested permissions before enabling a connection.
Security FAQs
QHow does eWasl protect my data?
We use HTTPS for the website, server-side encryption for platform tokens, and account and workspace-membership checks before access to private data.
QCan I delete my data?
You can request account deletion from settings. The privacy policy explains retention and exceptions; you may also need to revoke application access on connected platforms.
QHow do you handle social-platform access tokens?
Stored tokens are encrypted on the server and used for authorized functions. You can disconnect accounts and revoke eWasl access on the social platform.
QDoes eWasl hold independent security certifications?
We do not currently present independent security-audit certifications. Internal reviews and tests are not external certification.
Start your journey with eWasl
Review the privacy policy and permissions, then connect the accounts you want to manage.