System status

1.Current status

2.If we are down and your deadline is not

What to do, in order:

1. Keep receiving complaints. Record them on your offline intake form - SOP-001 covers this.
2. Identify any case with a deadline inside the next few business days and prioritise it.
3. For anything approaching its deadline, submit directly through the FDA's own portal using your most recent downloaded dossier. Your SOP-010 offline submission checklist sets out the steps.
4. Record every action taken offline, with times, for entry once service is restored.
5. Ask us for the incident timeline afterwards - you may need it for your own records.

We are never your only route to submit a report. That is a design rule, not a disclaimer: any product that made itself the sole path to a regulatory filing would turn its own downtime into your compliance failure.

3.Backups and recovery

Backups run nightly. They are encrypted with AES-256 before they touch disk, and the encryption key is held separately from the backups themselves.

Restores are tested weekly, not assumed. A restoration test checks that the schema, the tenant-isolation policies, the audit history and its hash chain, and the attachment records all come back intact - not merely that the database starts.

We intend to improve the recovery point objective as the platform matures. A serious safety system should eventually target hourly, and we will not describe it as hourly before it is.

4.Incidents

No incidents to report. When there are, they will be listed here with what happened, who was affected, and what we changed - including the ones where the answer is uncomfortable.

Our severity levels, notification commitments and response times are set out in the Trust Centre.

5.Contact

For service questions, security reports or anything urgent:
etechflow0@gmail.com