Trust center

Data & security

Last updated: September 3, 2026

Website safeguards

The public site uses HTTPS, strict transport security, a restrictive content security policy, clickjacking protection, limited browser permissions, and provider-level traffic protection. It intentionally avoids public forms, advertising trackers, and third-party analytics.

Payment design principles

Before accepting payments, Chronobyte Labs will use a dedicated payment provider, keep complete payment credentials out of its own systems, authenticate sensitive administrative access, restrict access by role, and maintain appropriate logging and abuse controls. The checkout will state which provider handles payment information.

Financial connectivity principles

If a future product connects to a bank or other financial institution, the connection will be consumer-permissioned and handled through a named connectivity provider. Before connection, users will be told:

• which data is requested, from which selected accounts, and why;
• which features require the data and how long access is intended to continue;
• which third party facilitates the connection; and
• how to request disconnection, revoke access, or request deletion where applicable.

We will request the minimum practical data and permissions for the disclosed purpose. Provider tokens and secrets will remain server-side and will not be exposed in browser code. Chronobyte Labs will not ask users to email or directly disclose their bank login credentials.

Incident and vulnerability reports

To report a suspected security issue, email hello@chronobytelabs.com with a concise description and safe reproduction steps. Do not include live credentials, card data, or unnecessary personal information, and do not disrupt systems or access data that is not yours.

No certification claim

This page describes the current website and design commitments. It does not claim that Chronobyte Labs is a bank, licensed financial institution, PCI assessor, or holder of a security certification.