Known limits
Ce contenu n’est pas encore disponible dans votre langue.
The Privacy area is new. These are its known limits today, with a way to work around each one.
| Limit | What it means | Workaround |
|---|---|---|
| Law names and citations are in English | On the French interface, law names, rules and citations (for example Act 843 s.35(10)) still show in English. They come from SpeculaPro’s law table, not from the translations | Read them as references; the deadlines and dates themselves follow the interface language |
| Legal holds take an ID, not a search | To hold a case, customer or report you type its ID, found in the address of its page | Open the case, customer or report, copy the ID from the browser’s address bar, and paste it |
| No people picker for the DPO or breach tasks | The DPO is a name and an email typed into Registers → Settings; breach tasks can be assigned through the API but not chosen from a list on screen | Type the DPO’s details. Write who owns a task in its title until a picker arrives |
| A stuck write in the analytics store (only with the optional analytics store) | If the analytics store hangs for more than 10 minutes while writing during a purge or an erasure, the rows it was writing can stay in the analytics copy | Ask your administrator to run speculapro analytics backfill afterwards. See The analytics store |
| Case notes and evidence files stay until the erasure itself | When an erasure is carried out, the customer’s closed cases are cleared too: the title, what investigators wrote and every evidence file. Nothing is cleared earlier. While an erasure waits (an open case, a legal hold, or a retention period still running), the comments and files stay as they are. The audit log is not rewritten either: its entries for those cases (a comment’s text, a file’s name) stay until the audit log’s own retention removes them by whole months | Tell the person when the erasure will be carried out, which the request shows. A file added by mistake can be removed from an open case by the person who added it or by someone with cases.approve |
| Only an erasure on request clears a customer’s cases | The clearing of closed cases happens when an erasure request is carried out, and only for cases about the customer or their accounts. A customer removed by the retention purge alone keeps the title and comments on closed cases that stay because of a report; only the files filed with no report are removed. Cases about a counterparty or a device are not cleared | Record an erasure request for the customer when the cases must be cleared too. Keep personal details about third parties out of comments |
| Traces of AI assistant reviews and summaries outlast an erasure | An erasure on request deletes the AI assistant’s reviews of the customer’s alerts, its summaries of their cases and its narrative drafts for reports made from those cases (the text, and the masked request and answer). Two things stay: the audit log’s ai.alert_review, ai.case_summary and ai.narrative_draft entries, which keep the model and the token counts (and, for a review, the recommendation; for a case summary, the suggestion) but no text, and any copy the model’s provider keeps, which SpeculaPro can’t reach. A customer removed by the retention purge alone keeps their alerts’ reviews and their cases’ summaries until the alerts and cases are deleted. Narrative drafts are deleted when their report leaves draft, so only a report still being written holds one. The assistant’s tuning suggestions for rules are not touched by an erasure: they are built from a rule’s definition and counts, with no customer in them, though a figure for an outcome that only one alert had is that one subject’s figure, unnamed |
Take the provider’s retention terms into account before switching the assistant on. See Registers: the AI assistant |
| The provider’s AI assistant records outlive the workspace | On the hosted service the provider keeps counts of a workspace’s AI assistant calls and tokens, the calls it added for a month, and each request for more calls with the note an administrator wrote and the ID of the person who asked (shown to nobody). These rows are not deleted with the workspace, by retention or by an erasure, and have no retention period. They hold no customer data unless a note was written with some in it | Keep customer details out of the note. After a workspace is deleted the rows can be read and removed only in the database, by the operator |
| Rule hits on alerts keep their explanations | A pseudonymised decision loses each rule’s explanation and feature values (live and shadow), the risk model’s reasons, its customer reference and the note on its feedback. Rule hits on alerts are a separate record: they keep the rule’s explanation, which can quote a figure about the customer (14 times the customer’s 30-day average), and the model’s reasons, until the alert’s own retention period removes them | Set the Alerts and cases period no longer than you need. See Risk models |