Security and data

What leaves your environment. And what never does.

The free scheduler makes no calls outside your environment. Auto Schedule sends a pseudonymous copy of one period, and you can read it before the first run.

The data flow

Your rows stay yours. A run gets placeholders.

Three places, one direction each way. The answer comes back as a proposal, never as a write.

Your Dataverse

Your rows, your security roles, every edit saved to your table with who made it

Chrona service

A pseudonymous copy of the period: placeholders for ids, no personal names, no notes

Your board

The answer is a proposal. Nothing is written until you select Apply

Where it runs. The Chrona service is hosted in Microsoft Azure, Australia East, and traffic reaches it through Cloudflare. Run records are kept for 90 days for support and fair-use accounting.

Sign-in

The Chrona Portal signs you in with your own Microsoft Entra ID account. There are no Chrona passwords. The scheduler itself needs no sign-in at all.

What a run sends

The rows in the period with ids and names replaced by placeholders: shift times, breaks and assignments; each person's skills, contract hours and rate, unavailable times without the reason, and preferred times; the agreement rules, the scheduler's name and who ran it. No personal names, no titles, no notes, no contact details, no unrelated records. The Auto Schedule dialog shows the exact payload before the first run.

What a run writes

Nothing on its own. The answer arrives as a proposal on the board. Drop what you disagree with, then select Apply. Every write goes to your table under your user.

Security roles stay in force

The scheduler reads and writes through your model-driven app, so Dataverse security roles, teams and business units apply to every row it shows and every edit it saves.

When Chrona is unreachable

Viewing, manual rostering, editing, publishing and Generate keep working on your own data. Auto Schedule pauses; after 24 hours the scheduler bar says so, with Retry. No data is locked.

How paid features are switched on

From a signed entitlement session the Chrona service issues to your environment, refreshed about hourly with a 14-day hard expiry. Silence never switches anything off. Only an explicit lapsed claim does, after a grace period.

Straight answers

Ask for the facts. Not for badges.

What a security review will want to know, answered as it stands today.

Does Chrona hold a security certification?

No. Chrona has no SOC 2 or ISO 27001 certification. Nothing on this site should be read as one.

Where is data hosted?

Your data stays in your Dataverse environment and region. The Chrona service that runs Auto Schedule is hosted in Microsoft Azure, Australia East.

Can I see what is sent before I connect?

Yes. The Auto Schedule dialog shows the exact payload of a real run before the first one. Try a free sample run uses sample data.

How do I remove everything?

Take Chrona Scheduler off the views that use it and delete the managed solution; the platform removes it cleanly. To close a connected environment or a Chrona Portal account, email support@chrona365.com.

Security reports

Found a security problem? Tell us first.

Email support@chrona365.com with “Security” in the subject. We confirm we have it and keep you updated until it is fixed.

What to include

  • What you found, and where: the page, the address or the package version.
  • The steps to reproduce it.
  • What someone could do with it.

In scope

chrona365.com and its subdomains, the Chrona service that runs Auto Schedule, and the Chrona packages for Power Platform.

Power Platform and Dataverse belong to Microsoft: report those to the Microsoft Security Response Center.

Test safely

  • Use only your own account and environment.
  • Never read, change or delete anyone else’s data.
  • Do not disrupt the service.

We do not run a paid bug bounty.

Ask us anything this page does not answer.

We answer security questions by email, in writing, with the facts as they stand.