01 Policy

Privacy policy

Version 1.0 · Last updated

This is Visor’s public privacy policy. It covers the ad network and this website. The users we monetize are in the United States. If a signed agreement adds a data term, that signed term controls the commercial relationship. These pages stay the public description of our data boundaries.

Who is responsible

Securax UG, Regensburger Str. 39, 85055 Ingolstadt, Germany, operates Visor and this website and is responsible for the processing described here. Register: District Court Ingolstadt, HRB 9040. Privacy requests go through the contact form.

What we use

Matching takes anonymized user data and local session data. Local session data means the context of the chat that is open now. A classifier uses that to choose the ad. Anonymized means the data is not labeled with a person’s identity. Pseudonymized means a direct identifier, such as an account email, is replaced with a stand-in value before matching. The stand-in is not the person’s name, email, or phone number.

  • Topic and context of the current chat.
  • Anonymized in-app behavior, such as which parts of the app someone uses.
  • Device type: phone, tablet, or computer.
  • Country. On this network that country is the United States.
  • A pseudonymous identifier, if the app sends one.
  • Counts of ad views, and clicks when a person activates an ad, in aggregate.

What we never want, and do not use for matching

  • Name, email address, or phone number.
  • Precise location, such as GPS or a street address.
  • Government IDs, payment card numbers, or passwords.
  • Third-party cookies.
  • Browsing history from other websites.
  • A profile that follows a person across the web.
  • Personal information sold or shared with advertisers.

If a user types their own email or phone number into the chat, that text is inside the message. Publishers can send a topic summary instead of the raw transcript. We say this so the integration can be designed honestly. We do not claim conversation text can never contain a detail a person volunteered.

Cookieless, and not cross-site

We do not set third-party advertising cookies, and we do not track people from site to site. Cookie-based ad tech stores an identifier in the browser and reads it on other sites. Matching here stays inside the chat app. This marketing site also does not run a third-party advertising cookie or a third-party analytics tag as shipped.

How anonymization works, at the level we can say in public

Direct identifiers are removed or replaced before they are used to classify an ad. The classifier then sees anonymized signals plus the current session. It does not see a name. The exact transformation is part of the method. Approved partners can read it under a strict NDA. NDA means a non-disclosure agreement. We will not invent a diagram of hashes, salts, or keys on this page.

We do not sell or share personal information

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. We do not sell personal information. We do not share it that way. Advertisers and demand partners get delivery and spend in US dollars, not a list of people.

Other US state laws, including Colorado, Virginia, Connecticut, and Texas, draw similar lines around sale and targeted advertising. We design the product so a publisher can meet those duties. We do not hold a certification badge for any of them. This page is not legal advice.

Do not sell or share my personal information

There is no sale or share to opt out of, because we do not sell or share personal information. You can still ask what we hold about a work contact you sent us, and you can ask us to delete it. Use the contact page. Say “privacy request” in the message. We will not ask you to accept a tracking cookie in order to make that request.

GDPR, as a secondary note

GDPR is the European Union privacy law. This network monetizes users in the United States only, so US law is the frame that matters here. We still collect less rather than more, and we do not sell personal data. If you operate a separate product with users in Europe, say so before you integrate. This network is not that product.

Under 18, and children under 13

A publisher can mark an account as under 18. We then do not request an ad. Apps directed at children under 13 are not a fit. Do not send us a child’s name, birth date, or other personal information. We do not ask for a birth date in order to match an ad.

How long we keep records

We keep records we need to pay publishers, bill advertisers, prevent fraud, and meet accounting duties. We do 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. We do not keep personal data in order to sell it. We do not keep it in order to build a cross-site profile.

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. We have not listed a SOC 2 report or an ISO certificate here, because we will not claim an audit we are not showing.

Requests from people

A person, or a publisher acting for their users, can ask us to confirm, correct, or delete personal information we actually hold. Most matching data is not identified to a named person. Work emails sent through our forms are. Use the contact page. We may need to confirm you control that email before we change a record.

Changes

When this policy changes, we change the “Last updated” date on the page. If a change affects a signed customer, the agreement says how we notify them.