KeepingUp
Security

Trust through bounded access.

KeepingUp is designed around personal information and treats account isolation, clear assistant permissions, and predictable tools as core product requirements.

Account isolation

Every authenticated identity maps to one account. Data access is filtered by that account before records are read or changed, and identifiers from another account do not grant access.

Connected tools cannot create users, issue credentials, change plan ownership, or grant themselves additional permissions.

Assistant authorization

KeepingUp uses OAuth 2.1, dynamic client registration, and PKCE. Read access is required for a connection, while update access is presented separately and can be declined. Authorization records can be revoked without changing the underlying account password.

Users should connect only clients they recognize and grant only the access needed for their intended workflow.

Data and transport safeguards

Traffic is encrypted with HTTPS. Credentials are stored using one-way password hashing, request schemas constrain accepted data, and failure results are marked as errors rather than ordinary tool output.

We monitor operational failures and maintain recovery controls. No service can eliminate every risk, so important information should not rely on KeepingUp as its sole copy.

Responsible disclosure

If you discover a vulnerability, suspected cross-account access, unexpected authorization behavior, or another security concern, email security@keepingup.io. Include the affected endpoint, expected and observed behavior, and only the minimum evidence needed.

Please avoid accessing another person’s records, modifying data beyond your own test account, disrupting availability, or disclosing credentials. We will review good-faith reports and coordinate an appropriate response.