Beta Program

Eddy is a working product, not a prototype. Teams are using it to run real processes. But we are still shipping frequently, fixing bugs, and changing how things work. During beta:

• Features may change, be redesigned, or be removed.
• You may encounter bugs, rough edges, and incomplete functionality.
• Performance and availability are not guaranteed — there is no SLA.
• We will try to give you reasonable notice before removing something you have been actively using, but we cannot always promise this.

During the beta period, we ask that you do not process sensitive or special-category personal data through Eddy. This includes:

• health or medical records;
• financial data requiring PCI DSS or equivalent controls;
• trauma care, safeguarding, or child welfare records;
• biometric or genetic data;
• data relating to criminal offences or proceedings;
• any data that, if exposed, could cause serious harm to an individual.

The Acceptable Use Policy (section 2) already restricts certain categories of data. During beta, we go further: even where the AUP would permit sensitive data with safeguards (Tier 2), we strongly recommend you avoid it until the platform reaches general availability.

This is about prudence, not capability. Eddy's infrastructure is designed to handle structured process data securely. But during beta, the tooling around data subject rights, retention enforcement, and compliance automation is still maturing. Until those tools are fully in place, sensitive data carries operational risk that we do not think is appropriate for early adopters to take on.

Data you create during beta — Maps, Sessions, table data, uploaded files — is real production data stored on the same infrastructure we will use at general availability. We do not treat beta data as disposable.

If we ever need to make a change that would affect your existing data (a schema migration, a storage move, or a feature removal that impacts saved content), we will give you advance notice and, where possible, a migration path.

The data handling, retention, and deletion commitments in our Privacy Policy and Data Processing Addendum apply during beta. Your data is not in a lesser tier because you joined early.

Support during beta is provided on a best-effort basis. We do not guarantee response times. We are a small team and we prioritise issues by severity — data integrity and security issues come first.

If something breaks, tell us. Beta users who report issues help us build a better product. Reach us at hello@eddy.works.

There is no fixed end date for the beta period. Eddy is free to use during beta. When we are ready to move to general availability, we will notify you via the platform and email.

Your account, data, and Maps will carry over to general availability — there is no "reset." Features may evolve between now and then, but we do not expect to remove core functionality.

Pricing and plan tiers will be introduced when Eddy leaves beta. We will give you reasonable notice before any paid plans take effect.