No public evidenceToskr and GDPR
CertReports found no public GDPR evidence for Toskr as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Issued or listed
- 1 Dec 2017
- Scope
- For end users, we collect two types of information, data that users provide directly to us included in the account registration process, and automatically collected, non-personal information, which includes information gathered as users use the relaytxt.io website. When users register an account on Relaytxt.io, we ask users to provide a unique email address, first and last name, phone number, and a password. It is retained for the life of a user's account. • Users' first and last names are stored within the user record and utilized for display purposes within communications with texting contacts or the administration of a texting program for identification purposes. It is never released to a texting contact without the user's knowledge. • Users' phone numbers are stored within a user record for use within the app to call a user when using the calling feature, but is not made available directly to texting contacts. It is also available to an organization’s texting administrators. • Users’ email addresses are used as your login user name and is stored within your user record. We use this email address to send information about a user's account, notifications about texting assignments, and password reset notifications. It is also viewable by an organization’s texting administrators. We offer users opportunities to engage in conversations with texting contacts that are publicly available to those contacts and the administrators of a users organization’s texting program. If a user signs up for one of our email newsletters, we will send the user the newsletter that you requested. We may use the information that we collect to fulfill user requests for services and information. For example, we may use user contact information to respond to customer service requests. For admins, we collect two types of information, data that admins provide directly to us included in the administration processes, and automatically collected, non-personal information, which includes information gathered as you use relaytxt.io website. When admins upload a group of contacts on Relaytxt.io, the data within is retained for the life of an admin’s account. It is never released to other organizations or used for purposes outside of support and maintenance of an organization’s account. All data uploaded is available to any user account with the administrator level of access via GUI and exports. Any information added to a script is available to any user account that is assigned those contacts within an organization. • Contact first and last name is stored within an organization’s contact records and utilized for display purposes within communications with texting contacts or the administration of a texting program for identification purposes. • Contact phone number is stored within an organization’s contact record for use within the app to facilitate texts and phone calls. • Custom fields are stored within an organization’s contact records. We use these admin defined and populated data attributes to populate administrator created scripts. It is also viewable by an organization’s texting administrators. To prevent unauthorized access, maintain data accuracy and ensure the appropriate use of information, we have put in place commercially reasonable physical, technical and administrative controls to protect users and admins’ information. Other than explicitly mentioned in our privacy policy, we do not share, trade, disclose, or sell any personal information of any user or admin to any 3rd parties for any purposes, including advertising.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Toskr, Inc.: Inactive | Live pagesha256 8d00a2fc60 |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is Toskr GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags) whose GDPR row is verified or vendor-stated, ranked by similarity.
No same-category vendor has GDPR evidence in the index yet.