SDKSPACE privacy information

## Account and session information

The production application uses Firebase email authentication and configured Google/GitHub sign-in handlers. Signed session cookies last six hours. The application uses account identifiers to separate chat history, usage quota and connected tools. Signing in with GitHub alone does not grant repository write access.

AI requests and history

Messages and supported attachments are sent through the server to the selected AI provider for processing. Search requests use the configured search integration. When chat history storage is enabled, finished signed-in chat exchanges are stored in Cloudflare D1 and are restricted to the account owner. Attachment files are not stored in history; attachment names may be retained. SDK generation requests do not save chat history through the website history handler.

Credentials and connected services

Provider secrets remain on the server. Separate GitHub code-tool connections can store encrypted connection credentials and perform the operations authorized by the connected account. Do not share passwords or API keys in messages. Third-party providers apply their own terms and privacy policies.

Your controls and limitations

Use the chat interface's available history deletion controls and sign out when finished. Contact the project via contact for questions without posting personal information publicly. This page describes the current implementation; it does not claim HIPAA certification, guaranteed deletion from third-party systems, or an unspecified retention period. About · Source