Help

Support and contact

Support goes through the contact page. This site does not publish an email address, a phone number, or a response time.

Last updated · 7 min read

On this page

Support goes through the contact page. You pick a lane, you write the note, and you leave your own email. A person reads it and replies to that email. This site does not publish a Visor inbox, a phone number, or a response time.

How to reach Visor

Open Contact. The lanes match the work. There is no separate support portal, and Sign-in is not connected, so there is no account inbox to write into. There is no report to open on this website either. Counts for a verified publisher are issued with the account after the traffic check. They are not a screen on visor.host yet.

Which lane to pick
You are writing aboutLane on the form
A US chat app, a traffic check, or a live slotPublishers
A campaign, before any spendAdvertisers
An ad network or other demand buyerPartners
Access, deletion, or do-not-sellPrivacy
A press note. Not a staff interview.Press
A security or vulnerability reportThe form. Say security in the first line. There is no separate address.

The contact page says a person reads every note, and that the reply goes to the email you give. That is the path. No response time is published. There is no phone line to call.

Publishers do not need a call to apply. There is no waitlist. Demand partners, if the inventory fits, move to a call and a contract after a person reads the form. The form itself does not start ads and does not start bidding.

What to include

A useful note names the app and the symptom, then stops. It does not include the people who use the app. We do not need their personal data to see a broken slot, a bad ad, or a policy question.

What to put in the note, and what to leave out
IncludeLeave out
App name, as you use it with VisorA user’s name
Publisher ID, only if one has been issuedEmail addresses or phone numbers from your users
Page URL, or the screen name in the appPrecise location, payment data, or a government ID
Steps you took, in order, and what you expectedA raw transcript that contains those details
Time, with the time zone written outA cookie, an IDFA, or another advertising ID
Browser, device, and the app version you shipPasswords, access tokens, or session secrets
A screenshot of the ad or the empty slotA screenshot that shows a person’s identity

Write the time with a zone name or a UTC offset, for example America/New_York. A bare clock time is hard to line up with a report. If you do not have a publisher ID yet, say that the traffic check has not passed. Do not paste a placeholder and call it an ID.

Crop screenshots to the slot and the label. If the chat around the ad contains a name, an email, or a phone number, do not send that image. Describe the layout in words instead. The data list an app may send for matching is already short. A support note is not a reason to widen it.

  1. Read the public page that fits

    A blank slot is Troubleshooting. Money terms are Payments plus the agreement. A category question is the ad content policy.

  2. Say what you already ruled out

    For a missing ad: whether the check has passed, whether the session was in the US, whether the under-18 flag was off, and whether the response was empty.

  3. Send one note, on one lane

    Pick the lane on Contact. Put the facts from the table in the message. Leave your own email so the reply has somewhere to go.

Report a bad ad or a policy issue

Use the Publishers lane if the ad ran in your app. Use the Advertisers lane if you are reporting your own campaign, or a landing page you operate. Say “ad policy” in the first line so it is not read as a no-fill.

Include the words on the ad, the app name, the time with the time zone, and a screenshot of the ad itself. Name the category you believe it broke, if you know it. The full refused list is the ad content policy. Link that page and describe what you saw.

Do not send the user’s identity with the report. We can reject an ad or stop one that is already running. The policy says we do not owe a detailed forensic report when we stop fraud. We will say the reason we can share.

A publisher can also block alcohol, dating, health products, loans and other credit offers, and specific advertisers, and any brand or domain they name, without filing a report. Those blocks sit on top of the categories that never run. Controls and brand safety describes them. Filing a note does not change a block by itself.

Security and vulnerability reports

Send security reports through Contact. Put “security” in the first line. There is no separate security address on this site, and there is no phone. Trust points privacy and security notes to that same contact page.

  • What you observed, in plain language.
  • Where it happened: this website, or an app that uses Visor. Include the URL for a website issue.
  • The time, with the time zone.
  • Whether you believe other people’s data was exposed. Do not attach that data to show us.

Traffic to this site and to the ad endpoints should be encrypted in transit (HTTPS). A vulnerability note does not need a certificate number. The public security statement is on Data handling.

Privacy requests

Use the Privacy lane on Contact. Say “privacy request” in the message. Ask what we hold about a work contact you sent us, or ask us to delete it. The privacy policy is the source for those rights. This page is not a second policy, and it is not legal advice.

We do not sell personal information, and we do not share it for cross-context behavioral advertising. The do-not-sell page says there is no sale or share to opt out of. You can still write. We will not ask you to accept a tracking cookie in order to make the request.

A publisher’s own duties to their users stay with the publisher. Visor’s note path is for data Visor holds. Do not send us a user’s file so we can “look them up.” Matching does not use a name, an email, or a phone number, so that file is not a lookup key we want.

Company details

Visor is operated by Securax UG. The postal address, the register, and the VAT ID are below. The same facts are on the imprint. Trust links the product statements and the company record.

Operator
FieldDetail
OperatorSecurax UG
AddressRegensburger Str. 39, 85055 Ingolstadt, Germany
RegisterDistrict Court Ingolstadt, HRB 9040
VAT IDDE 323898666

There is no team page, and these docs do not name staff. Press notes go through the Press lane. They are not a request for a staff interview. Careers, when a role exists, are on Careers. A support note is the wrong place to ask for a named person.

Status

No status page is published. Do not look for an uptime board, a status hostname, or an incident RSS feed on this site. None of those is part of the public docs.

A locked page that will not open is not an incident. SDK, API, Matching, OpenRTB, and Webhooks stay closed until review, and sign-in is not connected yet. The body is not sent to the browser. Changelog is the public docs log. It does not report service health.

What support does not include

  • A response time. None is set.
  • A phone number or a published email address.
  • An error-code lookup. Troubleshooting does not list codes, because none are published.
  • A change to your revenue share. That number lives in the agreement.
  • That a locked page will open because you wrote to support. It opens after review, for a verified account, once sign-in exists.

Was something unclear? Contact support