SEVE · PRIVACY AND DATA
Delimited, traceable and eliminateable treatment.
Updated August 21, 2026.How data circulates
SEVE uses data to authenticate authorized people, execute decision-making cases, produce their artifacts and measure operational reliability. There is no behavioral advertising or sale of personal data on the product.
Authentication, authorisation and isolation of access
Data: e-mail, display name, paper, token only in hash.
Base: contractual execution and security of the service.
Addressees: Cloudflare as Backend.
Minimization: Crude token does not persist; sessions and invitations have expiration, revocation and limits of use.
Elimination: Automatic purge after expiration or revocation.
Execute, prove and rebuild the contracted decision-making case
Data: Case corpus, metadata, decisions, reports, audit trail.
Base: contractual execution and regular exercise of rights.
Addressees: Cloudflare as Backend.
Minimization: Objects are segregated by organization; access requires membership and permission by function.
Elimination: Organizational elimination erases R2 objects and D1 records ; prior informs exactly the range.
OCR and semantic compilation requested by the user
Data: document or image sent, extraction instruction.
Base: contractual execution.
Addressees: OpenAI only in OCR /Semantic flows enabled.
Minimization: Size and MIME are validated; external shipment occurs only in the corresponding functional flow.
Elimination: It follows the organizational elimination and the purge of the persisted object.
Measuring executionability and blind assessment failures
Data: count, total bytes, MIME families, status, output hash.
Base: legitimate interest in security and improvement of service.
Addressees: Cloudflare as Backend.
Minimization: Do not save file name, document text or document content.
Elimination: Automatic purge in 90 days.
Operational retention
- Temporary authentication and prevention of abuse: purge 30 days after expires_at.
- Temporary invitation and proof of authorisation: purge 90 days after expires_at.
- Operational reliability without documentary content: purge 90 days after COALESCE(completed_at, started_at).
- Prove service to the holder without indefinite retention: purge 365 days after resolved_at.
Records and objects of a case remain as necessary for execution and reconstruction contracted. The organizational elimination has prior reach, strong confirmation and coordinated removal of the D1 bank and the R2 safe.
Infrastructure and transfers
Cloudflare supports the execution, the D1 bank and the R2 vault. OpenAI receives files or instructions only in the OCR streams, semantic search or intelligence using these features. The other external connectors are triggered according to the requested function and maintain provenance on output.
When a flow configures international transfer, its operational release requires inventory of the recipient and destination, minimization, applicable mechanism, safeguards and provenance. The absence of the required proof keeps the flow suspended; isolated technical configuration is not treated as a legal instrument.
- Identify recipient, paper, country or region, data categories, purpose, duration and subprocessors of the external flow. Flow inventory linked to the resource and the version that actually executes it.
- Demonstrate the need for egress and limit fields, content, frequency and retention to a functional minimum. Load of data reduced to what the proven purpose requires.
- Link to the flow the applicable hypothesis and mechanism, with corresponding instrument or proof when required. Verifiable mechanism registered; interface text or isolated technical configuration does not replace the required instrument.
- Check the security, rights of the holder, disposal, incident, subcontracting and reversibility of the recipient. Safeguards and limits reconciled with current flow.
- Preserve the provenance of egress and suspend the flow when the required inventory, mechanism or safeguards are not demonstrated. Flow authorized by traceable evidence or kept inactive.
Response to security incident
A confirmed event goes through containment, risk assessment, communication when applicable, correction and retest in the same object. The technical record only preserves what is necessary for the calculation and does not extend access to the content treated.
- Confirm the event, preserve time, scope, correlation, hashes and evidence without expanding access to the content. Classified event and technical chain preserved with confidentiality, integrity, availability and authenticity evaluated.
- Repeal credentials or affected sessions, isolate the resource and interrupt the strictly necessary egress. Vector contained without erasing the evidence required for the verification.
- Evaluate the nature and categories of data, holders, extension, consequences and safeguards. Traceable decision on risk or relevant damage and on the incidence of the communication rite.
- Where applicable, prepare factual communication to ANPD and holders with verifiable scope, effects, measures and contact. Communication registered or motivated decision of non-incidence, without affirmation beyond the preserved proof.
- Fix the cause, repeat the affected tests and reconcile residual risk, version, commit and environment. Found corrected and retested on the same operational object.
Exercise your rights
This channel records confirmation and access, correction, portability, deletion, information on sharing, opposition and revocation. The protocol is in the administrative infrastructure of the SEVE itself.