Storage and access
Your account, workspace content, access grants, and operational history are stored in Convex. The Core Edge service runs through Railway and processes content in memory to authenticate requests, retrieve records, and serve agents.
Core Edge does not currently provide end-to-end encryption. Slaytek Systems and relevant service providers may be technically able to access stored content when operating, supporting, securing, or debugging the service.
AI processing
When AI-backed summaries, embeddings, or semantic retrieval are enabled, record titles, content, and search queries may be sent through OpenRouter to a selected model provider. Do not put material into Core Edge if that processing boundary is unacceptable to you.
Do not store these
Do not store passwords, API keys, authentication tokens, payment-card data, health records, government identifiers, or other regulated or highly sensitive information. Core Edge is for operational context, not the nuclear launch codes. Especially not API keys disguised as launch codes.
Isolation and sharing
Accounts and spaces use stable internal identifiers, scoped permissions, and explicit sharing. Shared access can be read-only or writable and can be revoked. Closed-alpha product access remains approval-gated while isolation and fresh-account rehearsals continue.
Export and deletion
Markdown export exists for portable content, but it is not yet a complete export of every account, authentication, usage, and generated record. Account deletion is currently operator-assisted. Email [email protected] and we will identify the affected stores, explain retained backups or security records, and confirm what was completed.