Pre-launch draft

Privacy

Last updated: September 16, 2026

This is a product-development draft and has not completed legal review. It describes the data flows implemented today so they can be reviewed; it is not yet a final privacy notice. New paid plans stay closed until this notice and the Terms are approved.

Public website

The public pages do not use analytics, advertising, tracking pixels, or third-party cookies, and they have no sign-up or waitlist form. Your Light/Dark/System theme choice is stored only in your own browser.

Console sign-in

Signing in to the GraphMem console uses Google identity through auth.sezer.ai. The console stores a single opaque, HttpOnly session cookie that refers to a server-side session; access tokens are kept on the server and are not readable by page scripts. Disconnecting removes that session.

Memory content

Memory records and relationships are created by the agents you connect to GraphMem over MCP and are stored by the GraphMem service for your authorized organization and project. The console reads bounded, read-only views of that data for the signed-in session.

Billing

Paid plans are not open. When they are, payment details will be handled by the payment processor through the Sezer Labs control plane; this website will not receive card numbers.

Service operation

Servers may record request outcomes and timing so the service can be operated and debugged. Tokens, cookies, and memory content are not written to those timing records.

Still to be finalized in legal review

The legal entity responsible for the service and its contact details.
Retention periods, deletion and export requests, and user rights.
The list of subprocessors and where data is processed.
Governing law and the effective date of the final notice.

Security

GraphMem separates identity, application, and storage boundaries. No internet service can promise absolute security; controls and incident procedures will be documented before launch. See the security overview.