Privacy Policy
What we collect, why, who else receives it, and the choices you have.
1Who we are and what this covers
VisionForgeX (“VisionForgeX”, “we”) runs ads on websites and in apps for the publishers who own them, and runs visionforgex.com. This policy explains the personal data we handle for:
- people who visit visionforgex.com, write to us, book a meeting or apply for a job;
- publishers, the people and businesses with a VisionForgeX account;
- people who visit a publisher’s website that carries our ad tag, or use an app that carries our SDK;
- publishers who use our WordPress plugin, “VisionForgeX – Ad Management & Yield”;
- partners who sign an agreement with us online.
For publishers, the Publisher Terms also apply; their section on data says the same as this page. A publisher’s own website and app have their own privacy policies, which the publisher is responsible for.
2Visiting visionforgex.com
| What | How we get it | What we use it for |
|---|---|---|
| Server records | Like every website, our servers and Cloudflare, which delivers our pages, record each request: the network address, the browser, the page and the time. | To deliver the site, keep it secure and find faults. |
| Analytics | When switched on, Google Analytics counts visits and the buttons people click. For visitors from the European Economic Area, the United Kingdom and Switzerland it starts with analytics and advertising storage denied, so Google counts those visits without cookies. | To see which pages help people and which do not. |
| The contact form | What you type: your name, email address, WhatsApp number if you give one, your site or company, your answers to the form’s questions and your message. Cloudflare’s check (Turnstile) may look at your browser to tell a person from a bot. | To answer you. Your message reaches our team’s inbox and email. |
| The free tools | The domain or page address you type into the ads.txt checker or the ad speed check. We fetch that site’s ads.txt, or ask Google’s PageSpeed Insights to load the page. We keep the address checked and a one-line result, not who asked; to limit how many checks one visitor runs in an hour we keep a scrambled form of the network address for an hour. The earnings calculator works in your browser: what you type in it is not sent to us. | To give you the result, keep the tools running for everyone, and see which sites might want our help. |
| Booking a meeting | Your name, email address and what you tell us about the meeting. The meeting is placed in our Google Calendar, with a Google Meet link. | To hold the meeting and send you its details. |
| Applying for a job | Your name, email address, phone number, location, a link you choose, your note, your answers and your CV. You tick a box allowing us to keep them. | To consider you for work with us. |
| A referral link | If you arrive through a partner’s referral link, a cookie remembers the partner’s code for a limited number of days. | To credit the partner if you sign up. |
3Publishers and their accounts
| What | How we get it | What we use it for |
|---|---|---|
| Your account | You give us your name, email address, a WhatsApp number if you choose, and a password, which we store only as a one-way hash. If you sign in with Google, we receive your Google account ID, name and profile picture. | To run your account and contact you about it, your sites and your payments. |
| Payment details | You give us bank, PayPal, Payoneer or wallet details. | To pay you. They go to the payment provider that sends the money. |
| Your sites and apps, and their numbers | The sites and apps you add, what you set in the dashboard, your public pages (which our servers fetch the way a search engine does, including ads.txt), and the ad numbers Google and our demand partners report. | To run and improve your ads, show you reports, work out what you are paid, and spot problems such as invalid traffic. |
| Your Google Ad Manager account | Through the access you give us. | To set up and manage the ads for your sites and apps and to read their reports. Nothing else. |
| Signing in | A session cookie while you are signed in (it lasts at most 24 hours). On the sign-in and sign-up pages, Cloudflare’s check (Turnstile) looks at your browser and network address to tell a person from a bot, and password-reset requests are limited by network address. Enterprise accounts that ask for a code at sign-in can remember a browser with a cookie. | To keep you signed in and your account safe. |
| Accepting the Publisher Terms | The version, the date and time, your network address and your browser, when you tick the box. | As the record that you agreed. |
| Messages | What you write to us, by email or WhatsApp. | To support you. |
4People who visit a publisher’s website
When you visit a website that carries our tag, the tag runs in your browser to show ads. We never learn who you are.
- What the tag sends us: the page address, basic browser and device details, the country your visit comes from, how far the page was scrolled, and whether an ad was shown and seen. Where the site uses partner demand or our human check, your network address and browser details are used to request a bid or to tell a person from a bot. Where a site’s human check uses Cloudflare’s check (Turnstile), Cloudflare looks at the browser and its network address for the same purpose.
- What the tag keeps in your browser: a few values in the browser’s own storage (not cookies): how recently a full-screen or rewarded ad was shown, which half of a layout test you are in, whether you passed the human check, and your country. They keep you from seeing too many ads and keep a test fair. Our tag sets no cookies of its own.
- What it never does: read what you type into forms, your accounts, passwords or payment details on the site. We do not build profiles of visitors and we do not sell visitor data.
- Google and other buyers who show ads on the site receive your browser’s request for an ad, and may set their own cookies, under their own policies. You can control Google’s ads personalisation at adssettings.google.com, and learn how Google uses data from sites that use its services at policies.google.com/technologies/partner-sites.
- The website’s owner is responsible for its privacy notice and for asking your consent where the law requires it.
5People who use an app with our SDK
The VisionForgeX SDK sends us the app’s key, a random identifier made for the installation (not the advertising ID, and not tied to a person), the app and SDK versions, the Android or iOS version, the device make and model, the country, and what happened to each ad (requested, filled, shown, clicked, closed or failed) with the value Google reports for it. We use this to serve and measure ads, run tests and spot problems. The Google Mobile Ads SDK in the app collects data of its own, such as the advertising ID, under Google’s policies. Where the app’s publisher has other ad networks or in-app bidding switched on with us, those networks’ own code in the app, and the buyers who bid, receive what an ad request needs under their own policies; our bid requests carry the ad slot, the app, the device’s general type, the country and the consent signals, never the advertising ID or the precise location. We do not build profiles of app users and we do not sell this data.
6Our WordPress plugin
The plugin “VisionForgeX – Ad Management & Yield” sends nothing until the site’s administrator clicks Connect with VisionForgeX. Then:
- when connecting, VisionForgeX receives the site’s address and name and its WordPress, PHP and plugin versions, and the site receives a key for itself alone;
- twice a day, the plugin asks VisionForgeX for the site’s tag and ads.txt lines;
- once a day and when the administrator runs the check, it sends the result of its site check (tag found, ads.txt complete, HTTPS) and the versions; we then fetch the site’s public ads.txt file ourselves.
The plugin sends no posts, users, visitors or other personal data. On the site’s pages, the tag works as described in section 4.
7Partners who sign an agreement online
To sign, you confirm your email address with a code we send. We keep your name, title and signature, and the network address and browser from which the agreement was opened and signed, with the signed agreement.
8Who else receives data
- Google: Ad Manager and Ad Exchange (ads and their reports), Analytics (when switched on), Google sign-in, Google Calendar and Meet (meetings), and Google’s AI service, which reads the text of publishers’ public pages for our ForgeAI tools. No visitor data is sent to the AI service.
- Cloudflare, which delivers our pages and our tag files, stores files, runs parts of our ad auction, the bot check on our forms and, on the sites that use it, the human check (Turnstile).
- The other ad buyers switched on for a site, and our Google MCM partner where one is involved.
- The companies that host our servers and send our email, and the payment provider that pays a publisher.
- Authorities, only where the law requires it.
Each receives only what it needs for its part. We do not sell personal data. These companies may process data in countries other than yours; we use them because they protect it to a recognised standard.
9How long we keep it
- Publisher accounts: while the account is open, and afterwards for as long as we need the records for accounts, tax and disputes.
- Messages and meeting bookings: as long as they are useful to answer you and to keep a record of what was agreed.
- Job applications: until you ask us to delete them, or we no longer need them to consider you.
- Signed agreements: for as long as the agreement and the law require.
- Ad and visit signals: kept as daily totals for reports; the detail behind them is kept only as long as it is needed to measure, test and check traffic.
- Sign-in sessions: end after at most 24 hours and are never in our backups.
10How we protect it
Every page and every call is sent over HTTPS. Passwords are stored only as one-way hashes, keys and secrets are encrypted at rest, our backups are encrypted, and only the people who need it for their work can reach personal data. Sign-in pages are protected against bots, and accounts can use Google sign-in; enterprise accounts can ask for a code at sign-in. No system is perfectly secure; if a breach puts your data at risk, we will tell you and the authorities as the law requires.
11Your choices and rights
- You can ask us for a copy of the personal data we hold about you, to correct it, to delete it, or to stop using it for a purpose; and, where we rely on your consent, withdraw it at any time.
- Publishers can see and change most of their details in the dashboard, and close their account by writing to us.
- Write to [email protected]. We may ask you to confirm who you are, and we answer within one month.
- Some data we must keep (for example payment records for tax), and we will tell you when that applies.
- If you are not happy with our answer, you can complain to the data protection authority where you live.
We rely on the agreement with a publisher to run their account and pay them; on our legitimate interest in running, securing and improving the service and in measuring ads; on consent where the law requires it (for example analytics cookies in Europe, which start switched off); and on legal obligations, such as keeping tax records.
12Children
VisionForgeX accounts are for adults (18 or over), and visionforgex.com is not meant for children. We do not knowingly collect personal data from children.
13Changes to this policy
When what we collect or how we use it changes, we change this page and its date. If the change matters to publishers, we also email them.
14Contact
Questions about privacy, or a request about your data: write to [email protected].