Encrypted database content
Plaintext memory is embedded before encryption. The database stores encrypted content while the embedding vector remains available for similarity search. Only selected top results are decrypted for an authorized request.
Security built into memory operations
Protect company context before it becomes an answer
MemBytes applies organization, role, scope and namespace checks around memory storage and retrieval, with application-level encryption for memory content and auditable activity.
How MemBytes limits exposure
Security depends on application controls, hosting configuration, operational practices and the customer's own access decisions. These product controls form the application layer.
Tenant and scope isolation
Memory records carry organization and ownership context. Retrieval is restricted to the requestor's company and authorized global, departmental, shared or personal scope.
Connector control
Connector credentials and tokens are used only for configured sync operations. Customers can disable a source, stop backfill, disconnect authorization and clear connector data.
Customer deletion controls
Administrators can delete imported memories, connector-synced memories, uploaded attachments, connector accounts and workspace data through dedicated controls.
AI data boundary
MemBytes sends only the selected content needed for an explicit embedding, summarization or chat operation. Full encrypted memory collections are not sent for every question.
Operational responsibility
Production security also requires protected configuration secrets, HTTPS, secure database access, backups, monitoring, updates, least-privilege administrator access and incident response.
Questions about security or data handling?
Contact MemBytes before connecting production business records.