Security
How DeepShare Connector protects your connections and the apps that use them.
Narrow access
We ask each provider for the least access a connection needs, and today that is read-only: we never ask to write. Of what a service returns, only a short list of fields is passed to apps, such as an event’s title and times or a message’s sender, subject, date and preview. Full message bodies and attachments are never requested.
Two services, kept apart
The part of DeepShare Connector that the internet reaches never holds the tokens for your connected services. They live in a separate service that publishes no public port, in an encrypted database. Each service has its own database account that can read only its own data.
Encryption
- All traffic to DeepShare Connector uses HTTPS.
- Connection tokens, and the details in your activity record, are encrypted at rest with a key the web-facing service doesn’t have. The key can be rotated without downtime.
- Tokens we give apps, and sign-in sessions, are stored only as hashes.
Apps
- Only apps we have registered can ask to link, and each link is your explicit approval of one app.
- Apps use the standard OAuth 2.0 authorization code flow with PKCE. Their access tokens expire after an hour, and refresh tokens are single-use: reusing one ends the grant.
- You can revoke an app at any time and its tokens stop working immediately.
Safeguards in the service
- Strict content security policy, no third-party scripts, and cookies marked secure and HTTP-only.
- Requests that change something must come from our own pages.
- Every request an app makes is recorded before it is carried out.
- Per-person limits prevent a single account or a misbehaving app from overloading the service.
Reporting a vulnerability
If you find a security problem, please tell us at shi@aitok.ai before making it public. We will acknowledge your report and keep you informed.