spintax-net · Privacy & Data

spintax-net privacy & data

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

Role

The page states nothing on this.

Data categories

category: communication
We receive the message content in order to answer it.
Read from spintax-net's own page on 2026-11-10
category: behavioral
Nothing about it is stored on our side.
Read from spintax-net's own page on 2026-11-10

Purposes

purpose: Answer Telegram bot messages
We receive the message content in order to answer it.
Read from spintax-net's own page on 2026-11-10
purpose: Support correspondence
Where we process the little data that does reach us — support correspondence — we take reasonable steps to protect it in line with applicable law.
Read from spintax-net's own page on 2026-11-10

Retention

scope: Telegram bot messages
The bot keeps no database. It is a stateless service
Read from spintax-net's own page on 2026-11-10
scope: Messages sent to us
beyond any message you send us yourself, which we keep only as long as the conversation needs.
Read from spintax-net's own page on 2026-11-10

Residency

The page states nothing on this.

International transfers

The page states nothing on this.

Subprocessors

Data processing agreement

Deletion

route: Delete data in the product; contact page for messages sent to us
deleting it in the product deletes it, and uninstalling takes the rest.
Read from spintax-net's own page on 2026-11-10

Data subject rights

right: access, correct, delete, export or object
Depending on where you live you may have the right to access, correct, delete, export or object to the processing of your personal data.
Read from spintax-net's own page on 2026-11-10

Sale or sharing

stance: prohibited
We do not sell or rent your data.
Read from spintax-net'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