Privacy and legal notice

The operator identified in the legal notice controls account, support, security and billing data. Contact: contact@struct20022.cloud. For customer address files, Struct20022 acts on the professional customer’s instructions under the DPA; that customer must inform the people concerned and establish a lawful basis.

Account identifiers, email, optional name, preferences and usage records support the contract. Quotes use your professional details and message for requested pre-contractual steps; support relies on the contract or legitimate interest. IP addresses and technical events protect the service (legitimate interest). Billing records support contractual and accounting obligations. Required fields are necessary for the requested service. Registration is not consent to marketing. No solely automated decision with legal effects is made.

Local structuring does not send the address to an external service. Completion, including the public demo, may send it to Google Maps; validation sends it to the selected official source. Remove unnecessary names, bank details, sensitive data and unrelated columns before upload. Column detection may send opaque column IDs, generic semantic hints and masked statistical profiles to OpenRouter and a model provider, not raw row values. Routing requires no provider data retention or training collection; local detection is used if no compatible route exists.

Supabase provides authentication, database and private storage in eu-west-1 (Ireland); the application host is identified in the legal notice. Email providers handle authentication/support; Stripe will handle payments when enabled. Google Maps has its own contractual role and privacy terms and is not described as our exclusive processor. Some providers may process outside the EEA; exclusive EU processing is not guaranteed. Ask for the applicable countries, agreements and transfer safeguards before enabling an external option.

Source files are deleted from working storage when the job finishes. Results expire after 24 hours by default (account setting: 0–365 days); new download links are then refused and daily physical purging follows. Previously issued links can remain valid until their own expiry. Completion caches are scoped to the job. Technical history includes dates, counts, credits and possibly filenames. Keep personal data out of filenames and headers.

Account data is kept while needed for the account, then deleted or restricted subject to disputes and legal duties. Support messages remain for handling the request and any applicable limitation period. Accounting documents: ten years from the relevant financial year’s end. Contract evidence: the relationship and applicable limitation period, generally five years for French B2B claims. Provider backups follow separate retention cycles; immediate erasure from all backups is not promised.

You may request access, correction, erasure, restriction and portability where applicable, and object to processing based on legitimate interest. Consent to any separate optional processing can be withdrawn. Acknowledging this policy is not general consent. Email the contact above; proportionate identity checks may be needed. Response within one month, extendable by two months for complex or numerous requests with reasons given in the first month. For customer files, contact the customer first. You may complain to the CNIL or your competent supervisory authority.

Only necessary session, language, login and demo-counter storage is used. Persistent marketing attribution has been removed and its old local entry is deleted on visit. Future non-essential tracking requires a prior choice and easy refusal/withdrawal. The linked French documents contain the full contractual terms, DPA and archived privacy notice.