PolygonScan · Privacy & Data
PolygonScan privacy & data
Read from PolygonScan's own page on 2026-11-10. 21 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: both
PolygonScan acting as a data controller and data processorRead from PolygonScan's own page on 2026-11-10
Data categories
category: identifying
personal information that links back to an individual, e.g., name, gender, date of birth, and other personal identification numbersRead from PolygonScan's own page on 2026-11-10
category: contact
contact information, e.g., address, phone number and email addressRead from PolygonScan's own page on 2026-11-10
category: device
technical information, e.g., IP address for API services, browser type, device type, operating system, log data, API access logsRead from PolygonScan's own page on 2026-11-10
category: behavioral
usage and behavioural data, e.g. browsing activity on our platform, search queries, access times, referral sourcesRead from PolygonScan's own page on 2026-11-10
Purposes
purpose: provide and perform services
to enable us to provide and perform our services to youRead from PolygonScan's own page on 2026-11-10
purpose: business development and marketing analysis
for business development purposes such as statistical and marketing analysis, systems testing, maintenance and developmentRead from PolygonScan's own page on 2026-11-10
purpose: marketing communications
to communicate offers, product, services and information on products and activitiesRead from PolygonScan's own page on 2026-11-10
purpose: legal compliance
to comply with any legal or regulatory requirementsRead from PolygonScan's own page on 2026-11-10
Retention
scope: raw web server site visit logsperiod: 5 days
all raw web server site visit logs are retained for a minimum of 5 days only and then purged on an automated scheduled basisRead from PolygonScan's own page on 2026-11-10
scope: inactive dataperiod: 24-month period
prepare a disposal schedule for inactive data to be automatically purged within a 24-month periodRead from PolygonScan's own page on 2026-11-10
scope: data breach recordsperiod: at least 2 years
We will maintain a record of all data breaches for at least 2 years from the date of notificationRead from PolygonScan's own page on 2026-11-10
Residency
The page states nothing on this.
International transfers
mechanism: other
we will implement organisational and technical measures by only transferring to Third Party Sites where the target location is compliant with data protection legislation or have the same or comparable data protection lawsRead from PolygonScan's own page on 2026-11-10
Subprocessors
Data processing agreement
Deletion
route: request or no longer required
PolygonScan shall take all reasonable steps to ensure that all Personal Data is destroyed or permanently deleted when either requested or no longer required for the PurposeRead from PolygonScan's own page on 2026-11-10
Data subject rights
right: access
request access to and to request correction of your Personal DataRead from PolygonScan's own page on 2026-11-10
right: withdraw consent
to revoke or withdraw your consent to the processing of your Personal DataRead from PolygonScan's own page on 2026-11-10
right: restrict processing
to restrict or limit the processing of your Personal DataRead from PolygonScan's own page on 2026-11-10
right: erasure
to erase your Personal Data from all of our databasesRead from PolygonScan's own page on 2026-11-10
right: portability
to request a copy of your Personal Data in a structured, commonly used, and machine-readable formatRead from PolygonScan's own page on 2026-11-10
right: opt-out of marketing
to opt-out of receiving direct marketing materials at any timeRead from PolygonScan's own page on 2026-11-10
Sale or sharing
stance: conditional
We will not trade or sell your Personal Data to third parties without your consent.Read from PolygonScan'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