ValueSERP · Privacy & Data
ValueSERP privacy & data
Read from ValueSERP's own page on 2026-11-10. 19 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: identifying
Identifiers, such as your name, email address, postal address, online identifier, account name, and phone numberRead from ValueSERP's own page on 2026-11-10
category: financial
Payment information such as your credit information, credit card, debit card, or bank account number, other financial information, or communications preferencesRead from ValueSERP's own page on 2026-11-10
category: behavioral
Internet or other electronic network activity information, including browsing history, search history, and information regarding a consumer’s interaction with an internet website, application, or advertisementRead from ValueSERP's own page on 2026-11-10
category: device
Device Information : We collect information about the computer or mobile device you use to access our Services, including the hardware model, operating system and version, and unique device identifiers.Read from ValueSERP's own page on 2026-11-10
Purposes
purpose: Provide, maintain, and improve services
Provide, maintain, and improve our offerings and servicesRead from ValueSERP's own page on 2026-11-10
purpose: Marketing communications
Communicate with you about products, services, offers, and events offered by Traject Data and othersRead from ValueSERP's own page on 2026-11-10
purpose: Fraud and illegal activity prevention
Detect, investigate and prevent fraudulent transactions and other illegal activities and protect the rights and property of Traject Data and othersRead from ValueSERP's own page on 2026-11-10
purpose: Legal compliance
Comply with our legal obligationsRead from ValueSERP's own page on 2026-11-10
Retention
scope: Account deletion
but note that we may retain certain information as required by law or for legitimate business purposes.Read from ValueSERP's own page on 2026-11-10
scope: Cached or archived copies
We may also retain cached or archived copies of information about you for a certain period of time.Read from ValueSERP's own page on 2026-11-10
Residency
region: United States
Traject Data is based in the United States and we process and store information in the U.S.Read from ValueSERP's own page on 2026-11-10
International transfers
mechanism: other
we and our service providers may transfer your information to, or store or access it in, jurisdictions that may not provide equivalent levels of data protection as your home jurisdiction.Read from ValueSERP's own page on 2026-11-10
Subprocessors
Data processing agreement
Deletion
route: email data@bytraject.com
If you wish to delete or deactivate your account, please email us at data@bytraject.comRead from ValueSERP's own page on 2026-11-10
Data subject rights
right: Access, correction, or deletion
You may update, correct or delete information about you at any time emailing us at data@bytraject.comRead from ValueSERP's own page on 2026-11-10
right: Know personal information (California)
You have the right to request that we provide details about the personal information we collect about youRead from ValueSERP's own page on 2026-11-10
right: Deletion (California)
You have the right to request that we delete the personal information we collect.Read from ValueSERP's own page on 2026-11-10
right: Object or restrict processing (EC residents)
You may also have the right to object to, or request that we restrict, certain processing.Read from ValueSERP's own page on 2026-11-10
right: Non-discrimination (California)
We will not discriminate against you for exercising your rights under this Privacy Policy and under California law.Read from ValueSERP's own page on 2026-11-10
Sale or sharing
stance: prohibited
We do not and will not sell personal information.Read from ValueSERP'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