Wikilect
Security
Wikilect is designed to protect OAuth tokens and customer data used in AI workflows.
Token protection
OAuth refresh tokens are stored encrypted at rest, never exposed in the user interface, and must not be written to application logs. Access is limited to backend services that need the token to perform an authorized customer workflow.
Access controls and auditability
Administrative and support access should be role-based, limited to authorized personnel, and auditable. Sensitive actions such as consent, token refresh, revocation, message sending, document updates, and support access should be logged without exposing raw OAuth tokens.
Data in transit and at rest
Wikilect uses secure transport for communications with Google APIs and customer-facing services. Customer data and integration secrets should be protected at rest using appropriate technical and organizational controls.
Restricted-scope data
When Wikilect processes Gmail or broad Drive data, that data is treated as sensitive Google user data. It is used only for authorized user-facing features and is subject to Limited Use, access control, retention, and deletion requirements.
Security contact
For security questions or vulnerability reports, contact info@wikilect.com. Do not send OAuth tokens, passwords, or other secrets by email.