Protecting your data
- Access is checked: a signed-in account alone does not grant access to business records. Organization membership, product access and local workspace roles determine which actions are allowed.
- Connections are encrypted: public endpoints use encrypted transport. Protected stored service data uses the encryption controls of its owning AWS service.
- Development stays separate: development and production use separate identities, data, secrets and access rules.
- You can end browser sessions: account security controls let you request sign-out everywhere if a device is lost or account access is in doubt.
For an account access problem, contact support. For a suspected vulnerability or security concern, use the reporting contact below.
Identity and access
You can sign in with Google or email and password. When a person later signs in with Google using the same verified email address, the verified identity is attached to the same stable Zelikore account instead of creating a second person.
Product access is based on organization membership and the product entitlement. Each product then applies its own free or paid tier and local workspace roles. Service-to-service access uses short-lived, audience- and purpose-bound credentials; possession of a central account alone is not permission to change product data.
How product data is separated
The products exchange only the context and outcomes a workflow needs. Business records are not copied into other products as competing sources of truth, and execution state stays with the product that owns it.
Operations and environments
Development and production are isolated by environment-specific identities, data, secrets, queues, keys, logs, backups, and access rules within one AWS account. Public endpoints use encrypted transport. Protected service data uses the encryption controls provided by the owning AWS services.
This page describes the implemented security approach; it is not a claim of a third-party certification, compliance audit, uptime guarantee, or formal service-level agreement.
Report a security concern
Send a concise description, the affected product or URL, reproduction steps, and potential impact to engineering@zelikore.com. Do not include passwords, access tokens, private keys, or customer data in the first message.