Privacy policy.

Who to contact

Adsum Data is operated by Felix Dorn, 13 rue des Cordiers, 67115, Plobsheim.

For privacy questions, access requests, or a correction to a public record, write to api@adsumdata.com. Please describe the request without including an API key or unnecessary personal information.

Access requests and API accounts

If you email us, we receive your email address, the identity and organisation you choose to provide, your message, and ordinary email metadata. The contact page opens your own email application; it does not silently submit a web form.

For an API key, the service records a holder name, email address, key prefix and cryptographic digest, issue time, optional rate limit, revocation time, and an approximate last-use time. The database does not retain a recoverable copy of the full key. Revoking a key disables access; it does not automatically delete the account record or correspondence.

We use this information to respond to your request, administer access, investigate problems and abuse, and send service or data-change notices. Where applicable data-protection law requires a legal basis, responding to a request or providing agreed access is based on taking requested pre-contract steps or performing the agreement. Security and service administration rely on the legitimate interests of operating and protecting the service, subject to the rights and interests of affected people. Legal obligations may separately require particular records.

Location lookups

The API accepts a country plus either a postcode or selected latitude and longitude. A location can be personal information. Clients should send it only when needed and with the notices and authority required for their application.

The backend does not accept raw address text or Google place IDs and does not call a geocoding provider. A client application using Google Places handles address entry and selection in its own frontend. Google and that application may receive the typed address, selected place, and related technical information under their own policies. Only the postcode or selected coordinates should reach Adsum Data.

Lookup inputs travel in a POST body. The application is designed not to persist the raw input, echo it in responses, or include it in logs, traces, or metric labels. It uses a keyed fingerprint for lookup caching and diagnostic correlation. Cached answers contain the resolved geography and representatives, not the original postcode or point. Redaction is a technical safeguard; this notice does not describe a visit or lookup as anonymous.

Operational information and cookies

Application telemetry can include IP addresses, user-agent strings, request IDs, routes, status codes, timing, API-key identifiers, and operational outcomes. The redaction system removes supported sensitive fields, authorization values, request bodies, and URL query values from telemetry. IP addresses and user agents are intentionally available to service operators for diagnostics and abuse investigation. The production edge is configured without ordinary access logging.

The public site does not include advertising pixels, third-party analytics, or cross-site tracking cookies. Its fonts, styles and documentation scripts are served locally. The interactive API reference retains a key entered into its authorization control in page memory only, not in local storage. Restricted operator administration may use essential session and CSRF cookies.

Public representative information

The dataset contains public-role information collected from parliamentary registers and other declared sources: names, roles, parties, constituencies, public contact routes, source identifiers, and other published fields. Source provenance and reading times accompany records where available. Political affiliations are sensitive information under some privacy laws; making a source publicly accessible is not a blanket exemption from those laws.

The service uses published professional and public-role information to support representative discovery, civic participation, research, and public affairs. It does not build political profiles of people who perform lookups. Contact us about inaccurate, unnecessary, or unlawfully published information. Include the record or source URL and the correction requested. Historical source evidence and records may need to be considered separately from the currently served record.

Service providers, disclosure, and transfers

Information may be accessible to authorised operators and providers supporting hosting, storage, email, security, and service monitoring, as necessary for those functions. API customers receive the public representative information they request. Information may also be disclosed where legally required, to address misuse or security incidents, or to establish or defend legal claims.

The location and applicable arrangements for a particular customer’s processing should be confirmed during onboarding. Contact us for current hosting and service-provider details and, where applicable, the safeguards for processing outside your jurisdiction. Google Places used in a client frontend is governed by the client’s integration and Google’s terms; it is not a backend lookup service operated by Adsum Data.

Retention

Different records serve different purposes. Lookup results are held in short-lived caches. Operational telemetry is subject to the monitoring deployment’s configured expiry and log rotation. Key-holder and correspondence records remain available for account administration, support, security investigations, and applicable legal needs; there is no automatic account-erasure action when a key is revoked.

Published source evidence and some historical dataset records are retained for provenance, reproducibility, and corrections. They are distinct from user-submitted lookup input. Retention depends on the record’s purpose, account status, investigation needs, applicable law, and the actual storage configuration. Contact us for the schedule relevant to your proposed use and for deletion requests. Backups and retained evidence may require a separate review.

Your choices and rights

Depending on the law that applies, you may request access, correction, deletion, restriction, or portability of your personal information, or object to processing, including processing based on legitimate interests. If processing is based on consent, you may withdraw that consent without affecting earlier lawful processing. Rights have conditions and exceptions, including where records must be retained for legal obligations or claims.

Write to api@adsumdata.com. We may ask for proportionate information to verify that a request concerns you. You may also complain to the competent data-protection authority. For users of a separate customer application, contact that application about information it processes or sends to Google; Adsum Data cannot control its practices.

We do not use service-account or lookup information to make automated decisions producing legal or similarly significant effects about the individual making a lookup.

Changes

This notice may change as the product or its processing changes. The updated date identifies the current version. Material changes affecting key holders may also be communicated through the service contact details on record.