Privacy policy
Last updated 17 November 2026
This policy explains how Pinpoint Online ("we", "us") handles personal data in VEGA, the software service at https://vegai.online for advertising and marketing agencies. It covers the people who use VEGA, the clients and contacts whose details agencies keep in it, and visitors to its public pages. Questions: mabuadas@pinpoint.online.
1. Who is responsible
The agencies' data. Each company that uses VEGA decides what it stores about its own clients, contacts, leads and staff. For that data the company is the controller and we are its processor: we handle it only to run VEGA for that company, on its instructions. If your details are in an agency's VEGA space, contact that agency first; we will help it answer you.
Our own data. For account details, billing, support and security records we are the controller.
2. What we collect
Account details: name, email address, job title, role, password (stored only as a bcrypt hash, never in readable form), language preference and the companies you belong to.
What a company puts into VEGA: clients and their contacts, leads and opportunities, tasks, projects, timesheets, files, messages and comments, estimates, invoices and other finance records, people and payroll records, briefs and AI studio outputs, and brand material such as logos and guidelines.
Messages handled for a company: emails, SMS, WhatsApp messages and call recordings sent or received through the channels the company connects, and replies to its web forms.
Connected ad accounts: when a company connects Google Ads, Google Analytics or Meta ads, see section 5.
Website forms: when you book a demo or send a message on https://vegai.online, the name, email, company, phone and message you enter, the page and campaign that brought you, and a one-way hash of your network address (for spam limits).
Billing: the company's billing name, address, tax number and email, its plan and its invoices. Card details are entered on our payment providers' own pages; VEGA never receives or stores the card number.
Security and usage records: sign-in times, an audit log of important changes (who changed what, when), the address and browser of a request where needed to protect the service, and a delivery log for platform email that keeps a one-way hash of the recipient's address, not the address itself.
3. Why we use it
to provide VEGA: sign-in, the features each company switches on, and sending the email, SMS and WhatsApp messages a company asks it to send (performance of our contract with the company);
to keep VEGA secure, prevent abuse and keep an audit trail (our legitimate interest, and the companies' own record-keeping);
to bill for paid plans and keep tax records (contract and legal obligation);
to answer support requests and tell account owners about important changes (contract and legitimate interest).
We do not sell personal data, we do not use it for advertising, and we do not use a company's content to train AI models.
4. AI features
When someone in a company runs an AI feature, the material it needs (a brief, a client profile, post text, lead emails or messages to summarise, reference images such as a logo) is sent to the AI provider that handles the request. That is either a provider the company connected with its own key, or the provider the platform supplies: Ollama (text), OpenAI, Google Gemini or Higgsfield (images and video). Each provider processes the material under its own terms and privacy policy. For Higgsfield, reference images are first uploaded to a temporary address so the provider can read them, and Higgsfield keeps its results for 7 days. The results come back into the company's VEGA space.
5. Google and Meta data
A company can connect its Google Ads, Google Analytics and Meta (Facebook and Instagram) advertising accounts, and its Facebook Pages and Instagram accounts, so VEGA can show campaign and page performance in its reports.
Google: we ask for the scopes
adwords,analytics.readonly,openidandemail. VEGA reads campaign, ad group, ad, asset group and search term details and their performance metrics, and Analytics reports. It does not create, change or delete anything in the connected accounts.Meta: we ask for
ads_readand, optionally,business_management. VEGA reads the ad accounts you choose, their campaigns, ad sets, ads (including the ad text, images and links) and their insights, and the names of the businesses they belong to. It does not create, change or delete anything.Facebook Pages and Instagram accounts (optional): if you also allow
pages_show_list,pages_read_engagement,read_insights,instagram_basicandinstagram_manage_insights, VEGA reads the Pages and the Instagram professional accounts your login manages: their names, follower counts and daily figures (views, reach, engagement), and their posts with the caption, date, link and figures. It does not read comments, messages or the names of people who interact with them, and it does not post, reply, change or delete anything. Page access tokens are used for a moment to read the figures and are never stored.The access tokens are stored encrypted (AES-256-GCM) and used only for the company that connected them. The data is shown only to people in that company who are allowed to see reports. It is never sold, never used for advertising and never shared with anyone else.
VEGA's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting and deleting this data. In VEGA, go to Settings → Integrations, open the ad connection and choose Disconnect. This deletes the stored tokens straight away; tick the option to also revoke access and we withdraw it at Google or Meta as well. You can also remove VEGA at any time from your Google account (myaccount.google.com → Security → Third-party connections) or Facebook (Settings → Business integrations). When you remove VEGA in Facebook, or ask Meta to delete your data, Meta tells us and we delete the tokens, your Facebook user id and name and the granted permissions at once, in every company where you signed in (how this works). To have the ad, Page and Instagram data already copied into VEGA deleted, email mabuadas@pinpoint.online from the account owner's address; we delete it within 30 days and confirm by email.
6. Who else processes data
We use these service providers, each only for the purpose shown:
| Provider | Purpose |
|---|---|
| Hostinger | the server VEGA runs on, its database and stored files |
| Resend, or the company's own email server | sending email |
| Twilio | SMS, WhatsApp and voice, only when a company connects its own Twilio account |
| Network International, Stripe | taking card payments for paid plans |
| Ollama, OpenAI, Google (Gemini), Higgsfield | AI text, image and video generation (section 4) |
| Google, Meta | the ad accounts a company connects (section 5) |
| Google, Meta, LinkedIn, TikTok, Microsoft (Clarity) | measuring visits and ads on the public website (for Meta and Google, also sign-up and payment events); Google's tag without cookies until you choose, everything else only after you accept cookies (section 7) |
| Serper, Google PageSpeed | web search and page-speed checks, only with the company's own key |
| Browser push services (Google, Apple, Mozilla) | delivering notifications you switched on: a title, a short line and a link, never client work |
A company can also send its own data to systems it chooses through webhooks it sets up. We may disclose data when the law requires it, and always tell the company affected unless the law forbids it. Some of these providers work outside the country you are in, including in the United States; where the law requires it, we rely on appropriate safeguards such as standard contractual clauses.
7. Cookies and tracking
Inside the app. VEGA uses one cookie for signed-in people, vega_session, which keeps you signed in. It is strictly necessary, cannot be read by scripts, and lasts until you sign out or for up to a year (the platform default). Platform administrators have a second sign-in cookie for the administration area. There are no analytics, advertising or tracking cookies or scripts inside the app, with two exceptions: the page shown right after a new company is created and the page you come back to after paying an invoice load Google's tag, to tell Google Analytics and Google Ads about that sign-up or payment, under the same consent rules as the website (below). Its offline support (service worker) stores only the app's own static files on your device, never your data.
On the public website (https://vegai.online). A cookie, vega_consent, remembers whether you accepted or rejected cookies.
Google (Google Analytics, Google Ads and Google Tag Manager) uses Google's "consent mode". Its tag loads on every page, but until you accept it neither sets nor reads cookies and sends Google only cookieless signals: that a page was viewed or a form was sent, the time, your browser type, the page you came from, whether you arrived from an ad (the ad's click id itself is removed) and a random number for the page view — no cookie and no identifier that recognises you. Like any request from your browser, it reaches Google from your IP address. Google uses these signals to estimate how many visits and conversions our ads bring. If you accept, the tag uses its cookies (
_ga,_gcl_au) as usual; if you reject, it stays in that cookieless state.Everything else — the Meta Pixel, the LinkedIn Insight Tag, the TikTok Pixel and Microsoft Clarity, plus
vega_src, which remembers the campaign that brought you so a later form shows its source — loads only if you accept.
You can change your choice at any time from "Cookie settings" at the bottom of any website page. The cookie policy lists each cookie and how long it lasts.
When you accept cookies and then pay an invoice, the payment keeps your browser's Google Analytics id (from the _ga cookie). When the invoice is paid, our server reports the purchase to Google Analytics with that id — the invoice's number, amount, currency and plan modules, nothing else about you — even if you never come back from the payment page. The id is kept with the payment only until the purchase has been reported, and for at most 72 hours after the payment (a payment that is never completed loses it after 7 days). Without your consent nothing is kept and nothing is reported from our server. On the sign-up and payment pages above, if you accepted cookies, Google Ads also receives your email address hashed (SHA-256) so it can match the sign-up or payment to an ad click ("enhanced conversions"); the hash is made on our server, and your email address itself is never sent to Google.
When you accept cookies, we also share website, sign-up and payment events (such as a demo request, a new account or a paid invoice) with Meta directly from our server through its Conversions API, so that Meta can measure our ads; without your consent we send Meta nothing. Your email address, phone number, name, country and account id are hashed (SHA-256) before they are sent. Your IP address, your browser's user agent and the identifiers in Meta's own cookies (_fbp, _fbc) are sent as they are, because Meta requires them in that form. When you start a payment, these details are kept with the payment only until the purchase has been reported to Meta, and for at most 7 days.
Marketing emails that a company sends through VEGA can contain open and click tracking links and always an unsubscribe link; those are the company's campaigns, and it decides whether to send them.
8. Security
encrypted connections (HTTPS) everywhere;
each company's records separated by row-level security in the database, so one company cannot read another's;
passwords stored as bcrypt hashes; keys and tokens for connected services encrypted at rest;
files served only to signed-in people with access, or through share links that expire and can be revoked;
nightly backups, checked by a restore drill when they are made.
No system is perfectly secure. If a breach affects your personal data, we will tell the companies concerned and the authorities where the law requires it, without undue delay.
9. How long we keep data
Company data: for as long as the company uses VEGA. When a company space is closed it is kept for a grace period (currently 30 days) so a mistaken closure can be undone, then permanently deleted. The final export prepared for the owner is deleted 30 days after that.
Audit log: 2 years. Email delivery log: 180 days.
Data exports: downloadable for 7 days.
Details kept for reporting a purchase to Meta and Google (section 7, only with your consent): until the purchase is reported — for Google at most 72 hours after the payment, otherwise at most 7 days; copies in backups follow the backup rule below.
Backups: the last 14 nightly backups; older ones are overwritten.
Billing records: as long as tax law requires.
10. Your rights
Depending on where you live, you may have the right to access your personal data, correct it, delete it, restrict or object to its use, receive it in a portable format, and complain to your data protection authority.
If an agency holds your details in VEGA, ask that agency; it can export, correct or erase them, and we help it do so.
For your own VEGA account or anything else in this policy, email mabuadas@pinpoint.online. We answer within 30 days.
A company owner can export all of the company's data at any time from Settings.
11. Children
VEGA is a business tool and is not meant for anyone under 16. We do not knowingly collect children's data.
12. Changes
We will update this policy when VEGA changes. The date at the top shows the latest version, and we tell account owners about material changes before they apply.
13. Contact
Pinpoint Online
Email: mabuadas@pinpoint.online
See also the terms of service.