Privacy and data
Data handling, GDPR and CCPA
This page maps a Visor ad request onto GDPR and the California privacy laws. It is not legal advice, and the privacy policy is the source.
On this page
This page summarizes how data moves when a US chat app asks Visor for an ad, and how that summary sits next to GDPR and the California privacy laws. The privacy policy is the source. This page is not legal advice. It does not assign a role your counsel has to accept, and it does not quote a retention period the policy does not publish.
Who is who
Five parties show up in a request. Only one of them operates Visor. The people in the chat app are in the United States. The company that operates Visor is in Germany. Those two facts are both true, and the rest of this page keeps them separate.
| Party | Role |
|---|---|
| The person | Uses the chat app in the United States. They do not open a Visor account to see an ad. |
| The publisher | Owns the app. Decides when to request an ad. Sends only the allowed data. Writes the app’s own privacy notice. |
| Visor, operated by Securax UG | Runs the network. Receives the request, returns one ad or nothing, counts views and clicks, bills and pays in US dollars. |
| The advertiser | Pays a CPM for ad views. Receives aggregate reporting of delivery and spend, not a file of people. |
| A demand partner | Brings bids. Receives the public context set, not personal data about the person. Exact fields are not on this site. |
This page does not call the publisher a controller and Visor a processor, or the reverse. Those GDPR words are not in the public privacy policy. A data processing agreement is not published. See the pending note further down. Do not treat this table as a role assignment under any statute.
The operator
Visor is operated by Securax UG, Regensburger Str. 39, 85055 Ingolstadt, Germany. Register: District Court Ingolstadt, HRB 9040. VAT ID DE 323898666. Securax UG is the company responsible for the processing the privacy policy describes. Privacy requests go through the contact page. The imprint is the short company record. The trust center links the same facts.
The ad traffic is US-only. Securax UG being in Germany does not make the inventory European, and US inventory does not move the company out of Germany. Say so before you integrate if you operate a separate product with users in Europe. The privacy policy says this network is not that product.
What is sent, why, and who sees it
The publisher sends a request after the model has answered. The allowed contents are the current conversation or a short topic summary, anonymized in-app signals, device type, country, an under-18 flag, and a pseudonymous identifier. Privacy defines each one. The table is the same list, with the purpose and who sees it. It is not a payload schema. Field names beyond this list are not public. Name, email, phone, and street address come off before matching. Topic, intent, length, device, and a US region bucket stay. That kept set is not a second list of fields to send. We do not sell personal data. The SDK sets no cookie.
| What is sent | Purpose | Who sees it |
|---|---|---|
| Current conversation, or a short topic summary | Give the ad a topic that fits this chat. | The publisher sends it to Visor. A demand partner does not receive the raw chat. |
| Anonymized in-app signals | Context from this app, such as which parts of the app someone uses. | Visor. Not a history of other sites, and not a cross-app profile. |
| Device type | Phone, tablet, or computer, as the privacy policy defines device type. | Visor. The public demand description says device class, not a device identifier. |
| Country | Confirm the request is for a person in the United States. | Visor, and a demand partner. The live value is the United States. Not GPS. |
| Under-18 flag | Keep an ad off an account the publisher marks as under 18. | Visor. It is a flag, not a birth date, and not a child’s name. |
| Pseudonymous identifier, if the app sends one | A stand-in for the app’s own reference. Not a way to name the person. | Visor, if it is sent. It is not a name, an email, or a phone number. It is not on the public demand set. |
| Ad views and clicks, in aggregate | Count delivery, bill advertisers, and pay publishers, in US dollars. | Visor’s reporting. Advertisers see views, clicks, and US dollar amounts, not a list of people. |
A demand partner, on the public description, can receive country (the United States), device class, topic, and intent. That is not a named audience. Name, email, phone, precise location, a cookie, and the raw chat stay off that request. “Intent” in that sentence is the demand description. It is not a field a publisher sends. The publisher’s list is the table above.
Forms on this website
A work email sent through a form on this site is personal data about a contact, not about a person in a chat app. The privacy policy covers it. A person can ask Visor to confirm, correct, or delete personal information Visor actually holds. Use the contact page and say “privacy request.” Most matching data is not identified to a named person. A work email is. The cookie notice says form answers stay in the browser until an endpoint is connected. That fact is about this marketing site. It is not a description of the ad request.
Retention
The privacy policy says Visor keeps records it needs to pay publishers, bill advertisers, prevent fraud, and meet accounting duties. It says Visor does not publish one retention clock for every record type, because a payment record and a bid log are not the same. The signed agreement states the schedule for that relationship. Visor does not keep personal data in order to sell it, and it does not keep it in order to build a cross-site profile.
The privacy policy does not list a number of days for each record type.
GDPR
GDPR is the European Union privacy law. Securax UG is a company in Germany, in the Union, so GDPR applies to processing that company carries out. The ad traffic on this network is in the United States.
The privacy policy’s GDPR section says US law is the frame that matters here, because the network monetizes users in the United States only. It says Visor does not sell personal data. It also says: if you operate a separate product with users in Europe, say so before you integrate. This network is not that product. Do not point European users at this integration and describe it as an EU product. The public policy does not name a lawful basis, a standard contractual clause, or a representative.
- GDPR applies to processing Securax UG carries out, because the company is established in Germany.
- The people this network monetizes are in the United States.
- The privacy policy treats US law as the frame for that traffic.
CCPA and CPRA
Under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), “sell” and “share” have specific meanings. Share includes disclosing personal information for cross-context behavioral advertising. Visor does not sell personal information. Visor does not share it that way.
Do not sell or share says the same thing in short form. There is no sale or share to opt out of, because Visor does not do either one. Advertisers get delivery and spend in US dollars, not a list of people. A person can still ask what Visor holds about a work contact, or ask for deletion, through the contact page. Visor will not ask them to accept a tracking cookie in order to make that request.
Other US state laws
Other US state laws, including Colorado, Virginia, Connecticut, and Texas, draw similar lines around sale and targeted advertising. The privacy policy says Visor designs the product so a publisher can meet those duties. It also says Visor does not hold a certification badge for any of them.
Your duties as the app that people use can be broader than Visor’s duties as the ad network. The product boundary is what you can rely on here: we do not sell personal data, there is no sale or share of personal information for cross-context behavioral advertising, the SDK sets no cookie, and there is no list of people in the advertiser’s report. Your notice, your users, and your counsel sit on your side of that line. The summary of what to say is on Privacy.
Children
The Children’s Online Privacy Protection Act (COPPA) is the US federal law for online services directed at children under 13. Apps directed at children under 13 are not a fit for this network. Do not send a child’s name, birth date, or other personal information. Visor does not ask for a birth date in order to match an ad.
A publisher can mark an account as under 18, and Visor then does not request an ad. That flag is for accounts inside an app that is otherwise a fit. It does not bring a children’s app onto the network. The ad content policy refuses ads aimed at anyone under 18, and it refuses apps directed at children under 13. The publisher guidelines refuse apps that cannot exclude accounts marked under 18. Do not send a birth date to prove the flag. Send the flag, or do not request.
Data processing agreement
A public data processing agreement is not published. The policies do not offer one on request. Commercial data terms that exist are in the signed agreement. The privacy policy says that if a signed agreement adds a data term, that signed term controls the commercial relationship.
Subprocessors
No subprocessors are published. The trust center will name a vendor, with its purpose and region, when one processes personal data. None are listed there today.
Security
Traffic to this site and to the ad endpoints should be encrypted in transit (HTTPS). Access to publisher and advertiser records is limited to people who need it for the job. Visor has not published a SOC 2 report or an ISO certificate.
There is no published uptime figure, no published penetration-test date, and no bug-bounty table.
Vulnerability reports
Send a vulnerability report through the contact page. The trust center points privacy and security notes to that page, and it says to choose Privacy. A person reads the note. We do not publish a security email address, a phone number, or a response time. Do not include a person’s chat contents, a name, or a credential you do not need in order to describe the issue.
Describe the problem and the area of the product. Support is the path for publisher and advertiser questions that are not vulnerabilities.
What to read as the source
Use the privacy policy for rights, retention as far as it is published, sale and share, children, and security. Use the cookie notice for cookies. Use the do-not-sell page for the California opt-out statement. Use the imprint for the company record. Use your agreement for any data term you signed. Use this page as the map between those documents and the ad request. If the map and the policy disagree, follow the policy and tell us through the contact page.
Questions
Is this legal advice?
Does GDPR apply, if the users are in the US?
Do you sell personal information under the CCPA?
Where are the retention periods?
Can I request a data processing agreement from the contact page?
Who are the subprocessors?
- Privacy policyThe source. Rights, retention as published, sale and share, children, security.
- Do not sell or shareNo sale, and no share for cross-context behavioral advertising.
- Trust centerControls, the company record, and the empty subprocessor list.
- Privacy and cookieless operationThe allowed signals, the never-use list, and what a report does not say.