Information · privacy · security
Information Processing Policy
This page explains how Situation Card processes questions, cards, resources, snapshots, sharing, PDFs and technical traces.
Data controller
Situation Card is a service developed by IAAA+, a French simplified joint-stock company (SAS), SIREN 920 042 439, located at 14 rue Jean Perrin, 17000 La Rochelle, France.
Single contact address: contact@situationcard.com
General principle
Situation Card processes the information strictly needed to understand a situation, generate a card, provide resources, enable user-selected sharing, and protect the service.
By default, generations are measured through technical metadata. Full card content is stored only when a snapshot mode allows it.
Information processed
Depending on your use of the service, we may process: email address, language, submitted question, provided documents or URLs, generated cards, public sources consulted, public or restricted card status, generation traces, latency, errors, quality status, and user reactions attached to product layers.
We do not sell your data. We do not use it for targeted advertising.
Generations and metadata
Each generation may produce a technical event: date, language, domain, intent, resource status, quality status, latency, possible errors, and input size or hash.
This allows activity and quality to be measured without exposing raw text by default in the admin cockpit.
Card snapshots
A shared or exported card may be stored as a stable snapshot. A snapshot contains the validated card, its language, version, provenance, useful public sources, and privacy status.
A shared card exists in one snapshot language. Changing language means reading or creating a snapshot in that language. The PDF exports the snapshot language. The Share button never regenerates the card.
Public, restricted and private cards
A public card may be accessible by link or in public areas provided by the service. A restricted card is not intended to be publicly displayed in the Atlas. A private or sensitive card must not be turned into a public resource.
You remain responsible for the information you choose to make public or share.
Resources, URLs and Recherche+
When you provide a URL, or when a domain depends on external facts, Situation Card may query public sources or server-side search services. API keys are never exposed to the client.
Recherche+ is separate from the fast card: it looks for leads, weak signals, contradictions and possible evidence. Its results do not automatically become conclusions.
Documents and data you provide
You may share text, a URL, a document, an image, a spreadsheet or a dataset to clarify a situation.
You should only transmit content you are allowed to share. Sensitive, confidential, medical, legal, financial, minor-related or third-party information should be avoided, minimized or anonymized.
Situation Card should extract the minimum useful content, produce structured summaries or signals, and not expose raw private content in a public card. Private documents must not become public resources. Public sources may be cited as useful public sources.
Optional document retention
By default, raw documents you provide are not retained after processing. You may explicitly choose to keep them in your private space or with a private card.
A private retained document remains private. It is not exploitable by IAAA+ to train, enrich, benchmark, sell, profile or improve the service, unless you give separate, explicit and revocable consent.
Minimal technical metadata may be retained to operate the service: file type, size, hash, date, extraction status, owner and permissions. Raw content is excluded from exploitation by default.
Artificial intelligence models
Submitted information may be processed by artificial intelligence models to produce interpretation, Situation Card, Lecture, Approfondir, resources, or snapshot translations.
The interpretation reference may be ChatGPT / GPT today or another LLM tomorrow. Translations may use a specialized model. Providers should not receive more information than needed for the requested service.
Sensitive domains
Medical, legal, financial, administrative, social, minor-related or safety-related topics are handled with caution.
Situation Card provides structured analysis. It does not replace a lawyer, doctor, financial adviser, public authority or qualified professional. In an emergency or danger, contact the appropriate services.
Security and anti-abuse
Secrets and API keys are used server-side. Shared card reads should use cacheable snapshots and must not trigger AI models again.
The service may limit, slow down or block abusive use: spam, overload, attacks, prompt extraction attempts, abnormal volume, excessive cost, or requests threatening service availability.
Admin cockpit and CTO Watch
The admin cockpit is used to monitor quality, latency, errors, missing sources, cost thresholds, and technical alerts. It should prefer metadata and avoid exposing raw content.
CTO Watch may alert when a critical threshold is reached: p95 latency, error rate, fallback rate, provider errors, missing required sources, estimated hourly cost, or insufficient cache hit rate.
Retention and deletion
Technical metadata may be retained for service measurement. Snapshots may be retained according to their status: public, restricted, private, launch learning, or deletion.
You may request access, rectification, restriction or deletion of your personal data: contact@situationcard.com
Cookies
The site uses cookies required for the service to function: session, security, language preferences and technical measurement. No third-party advertising cookies are used.
Legal notice
Site publisher: IAAA+, French SAS, SIREN 920 042 439.
Registered office: 14 rue Jean Perrin, 17000 La Rochelle, France.
Publication director: JCA.
Published sites: situationcard.com and situationcard.fr.
Hosting: OVH SAS, 2 rue Kellermann, 59100 Roubaix, France, www.ovh.com.
Contact: contact@situationcard.com
Applicable law
This site and its contents are governed by French law. Any dispute relating to the use of the site falls under the jurisdiction of the competent French courts.
Last updated: May 10, 2026