Pelyr · Privacy & Data

Pelyr privacy & data

Read from Pelyr's own page on 2026-11-10. 28 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

value: controller
The controller within the meaning of Art. 4(7) GDPR is: Dr. Zürner GmbH
Read from Pelyr's own page on 2026-11-10

Data categories

category: identifying
GitHub user ID and login name
Read from Pelyr's own page on 2026-11-10
category: contact
Email address, message content
Read from Pelyr's own page on 2026-11-10
category: device
IP address, timestamp, requested address with its parameters, HTTP status, referrer, user agent
Read from Pelyr's own page on 2026-11-10
category: behavioral
Page, referrer, country, device/browser type, scroll depth and time on the page
Read from Pelyr's own page on 2026-11-10
category: financial
Paddle customer and subscription identifiers and the plans, individually agreed prices, interval and status of each of your subscriptions
Read from Pelyr's own page on 2026-11-10
category: location
the position your receiver reports over HTTPS
Read from Pelyr's own page on 2026-11-10

Purposes

purpose: account and sign-in
Art. 6(1)(b) — performance of the user relationship
Read from Pelyr's own page on 2026-11-10
purpose: IT security and abuse protection
Art. 6(1)(f) — legitimate interest in IT security
Read from Pelyr's own page on 2026-11-10
purpose: reach measurement
Art. 6(1)(f) — legitimate interest in reach measurement
Read from Pelyr's own page on 2026-11-10
purpose: maritime data provision
Art. 6(1)(f) — legitimate interest in providing publicly broadcast maritime data
Read from Pelyr's own page on 2026-11-10

Retention

scope: Reverse proxy access logs and service logsperiod: 14 days
the access logs of our reverse proxy and the logs our services write on their servers are deleted after 14 days
Read from Pelyr's own page on 2026-11-10
scope: Sentry error reportsperiod: 30 days
error reports at Sentry after 30 days
Read from Pelyr's own page on 2026-11-10
scope: Account dataperiod: Until the account is deleted
Until the account is deleted — see below
Read from Pelyr's own page on 2026-11-10
scope: Sign-in session
it ends when you sign out or after 30 days at the latest
Read from Pelyr's own page on 2026-11-10
scope: Reach measurement (Plausible)period: Without a time limit
Plausible keeps these records without a time limit
Read from Pelyr's own page on 2026-11-10
scope: Cancellation and withdrawal declarationsperiod: 3 years after receipt
3 years after receipt or, where we recorded the end of the contract, 3 years after that end if it is later
Read from Pelyr's own page on 2026-11-10

Residency

region: Frankfurt, Germany (EU)
Frankfurt, Germany (EU)
Read from Pelyr's own page on 2026-11-10
region: EU
EU; support access from the USA is possible
Read from Pelyr's own page on 2026-11-10

International transfers

mechanism: SCC
Transfers to them take place on the basis of the European Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR)
Read from Pelyr's own page on 2026-11-10
mechanism: DPF
where applicable on the provider’s certification under the EU–US Data Privacy Framework
Read from Pelyr's own page on 2026-11-10
mechanism: adequacy
rely on the European Commission’s adequacy decision for the United Kingdom (Art. 45 GDPR)
Read from Pelyr's own page on 2026-11-10

Subprocessors

The following providers process personal data on our behalf as processors under Art. 28 GDPR:
Read from Pelyr's own page on 2026-11-10

Data processing agreement

available: true
Cloudflare, Inc. — Privacy · DPA
Read from Pelyr's own page on 2026-11-10

Deletion

route: Direct account deletion in the account, or request using the section 1 contact details
An account that has no contributor station attached can be deleted by you directly, and that deletion is immediate.
Read from Pelyr's own page on 2026-11-10

Data subject rights

right: Object to legitimate-interest processing
If you are affected, you may object to this processing at any time on grounds relating to your particular situation (Art. 21 GDPR)
Read from Pelyr's own page on 2026-11-10
right: Access to station data
If you ask us under Art. 15 GDPR whether we hold such a recording of your station, we will tell you, as we do for any other data.
Read from Pelyr's own page on 2026-11-10

Sale or sharing

stance: prohibited
We do not sell data about our users.
Read from Pelyr's own page on 2026-11-10

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page