Legal
Privacy Policy
What we collect, why, who sees it and how long we keep it.
Effective 15 November 2026.
Summary
ReachAgents is an advertising platform for AI agents, run by Vulture Labs, Inc. Brands pay to reach people through the personal AI agent they already use, and those people are paid for it. To do that we hold a small amount about each person: an email address from someone on our waitlist; an email address, a name, the outcome of an identity check and a broad description chosen from fixed lists from someone who takes part with an agent; and business and campaign details from an advertiser. Advertisers see counts and never learn who anyone is. We do not sell personal information, and we do not share it for cross-context behavioral advertising. ReachAgents is for adults 18 or older who live in the United States. Today it runs as a public sandbox with simulated money, and our main address takes a waitlist. To ask about your information or use your privacy rights, write to founders@vulturelabs.com.
Who we are and what this covers
Vulture Labs, Inc. ("Vulture Labs", "we", "us") operates ReachAgents at https://reachagents.com. We decide how the personal information described here is used, and we are responsible for it. There are three exceptions:
- some of the companies named in Who we share it with also use what they receive for purposes of their own;
- the company that provides your AI agent, and any app your agent uses to reach you, handle what they receive under their own terms;
- when an advertiser's site sends us an event through our conversion pixel, we handle it on the advertiser's behalf.
This policy covers:
- https://reachagents.com and its subdomains, which include the waitlist, the public sandbox, the documentation and the blog;
- the participant dashboard and the advertiser campaign manager;
- the connection AI agents use to reach us;
- the page a sponsored message opens on;
- the conversion pixel an advertiser can put on its own website;
- the emails we send, and the emails you send us.
It does not cover advertisers' own websites, the companies that provide AI agents, or what we hold about our own employees and contractors as workers.
"Personal information" means information that identifies you or can reasonably be linked to you. Our Terms of Service say what you and we agree to.
What we collect and why
This section is arranged by who you are to us. More than one part can apply to you.
If you join the waitlist
- Your email address, which you type into the form. We encrypt it before we store it, and keep a keyed hash beside it so that one address is on a list once.
- Which list you joined: people with an agent, or advertisers.
- One answer, if you give it: the agent you use, or what your business is called.
- When you joined, and whether our confirmation email was sent.
We use these to confirm that you are on the list, to email you when your place is ready, and to decide which agents to open for first. We keep no IP address with your entry. Joining makes no account: an address on the list cannot sign in. Only people on our team who handle support can read the list, and each reading is recorded.
If you visit our website
- Analytics, errors and speed. Our own analytics, and PostHog, measure how our pages are used, what goes wrong in your browser and how fast pages load. Which other analytics run depends on the address you are on. See Analytics.
- Logs. Our hosting provider records each request to our servers: your IP address, your browser's description of itself, the address requested and the page that sent you. Our own servers also write one line per request, with the kind of request, the route, the result and how long it took. We use logs to keep the service running and secure. The address of a sponsored message's link carries that link's code, so the code is in the hosting provider's log. Our own lines leave it out.
- Monitoring. Our own lines, and a timing of each request as it passes through our servers, go to Datadog, which we use to watch that the service works. With a request, Datadog receives its route, its result, how long it took and your browser's description of itself. It never receives the code in a link, anything in an address after a question mark, or your IP address. Where PostHog runs on your page, each request to our servers also carries PostHog's random identifier for your visit, so that a slow or failed request can be matched to it.
- Limits on repeated attempts. To slow down guessing and abuse, our servers count requests from each IP address for one minute, in memory only.
- Small settings in your browser. See Cookies and similar technologies.
Our blog and documentation collect nothing else. There are no comments, and nothing to sign up for on them.
If you have an account
- Email address and name. You give them when you sign up. If you ask your agent to set up your account, it gives us the email address you tell it. We encrypt both before we store them. We find your account by a keyed hash of your email address, not by the address itself.
- Sign-in codes. There is no password. We email you a six-digit code each time you sign in. A code works once, for 10 minutes. We keep it only as a one-way hash.
- Sign-ins. A cookie keeps you signed in on that browser for up to 30 days. We keep only a one-way hash of its value.
- What you use. Whether you take part, advertise or both, and when your account was created.
- A history of what was done in your account, such as a choice you made or a decision a person on our team took. It holds no email addresses and no codes, and it cannot be edited.
If you take part with an agent
Your agent's connection. When you connect an AI agent, we record:
- which agent it is, when it connected, and when and why it was disconnected;
- the credentials it uses, kept only as one-way hashes;
- if you connected it through an app's connector, that app's name and the addresses it asked us to return you to;
- if your agent reports an installation identifier, a keyed hash of it, so that one installation cannot earn for two accounts;
- its schedule, and whether its check-ins arrive on time;
- its check-ins: how many arrived each hour, any errors, and when it last checked in.
How your agent's calls go. Each time your agent calls us, we note which call it was, the kind of agent, whether it worked and how long it took, and tell PostHog and Datadog. Both receive it under a code we make from your agent's connection with a key only we hold, which does not identify you or the connection. Nothing your agent sent us or was told is part of it.
What your agent sends us about you. Only these:
- your description, chosen from our fixed lists;
- your limits;
- answers to checks on sponsored records, and notices that a record was removed, including whether you asked for it;
- which sponsored messages it skipped.
Your agent chooses your description from what it knows about you. What reaches us is only a choice from our lists. It never sends text from your conversations, your files or its memory, and we have no access to them.
Your description. Interests from a fixed list of 16 broad topics, one of six age bands, and your U.S. state. The list has no health, politics, religion or sexuality topics. Your agent can set it only after you agree to Match ads to me. If you withdraw that choice, we delete your description at once.
Your limits. How many sponsored messages you want in a day and in a week, quiet hours and your time zone, how many sponsored records your agent may keep at once, the longest it may keep one, and subjects never shown.
Your choices. Each time you agree to or withdraw Take part or Match ads to me, turn Let advertisers count visits on or off, or pause or resume, we record it with the time. We keep this as a history and do not change past entries.
Your identity check. Before anything is offered, we confirm that you are a real person, 18 or older, living in the United States, and that you have only one earning account.
- In the sandbox, the check is simulated. Nothing real is checked and no document or photo is collected.
- Where real money moves, Stripe runs the check. You show Stripe a photo ID and take a selfie, and Stripe asks for your consent before it uses your face to match you to your ID. We receive whether you were verified, whether you are 18 or older, whether you live in the United States and in which state, the reason if the check did not pass, and Stripe's reference for the check. To work these out, our systems briefly receive the name, date of birth and address Stripe read from your ID. We do not store them. From your name and date of birth we make a keyed, one-way value that lets us notice one person opening a second earning account, and then we ask Stripe to delete the verification data it holds for us. We never receive your ID, your photos or a measurement of your face.
We do not use the identity check to choose which ads you see.
The ads you receive. For each ad sent to your agent, we record what was sent, when, at what reward, and what happened:
- for a sponsored record: when it was delivered and stored, each check and its answer, each day earned or missed, and when it was removed;
- for a sponsored message: when your agent received it, whether it skipped it, and what our viewer recorded when its link was opened (see the next part).
We keep the text of each sponsored record, encrypted. It is the advertiser's content, not yours. We also record evidence we refused, such as a link opened in a second browser, and signals that an account may be misused.
Earnings, payouts and disputes. Each earning and where it stands, rewards that were not paid and why, holds, reversals, disputes you open (including what you write) and our written decisions, your payout methods (the provider's reference, a status and a short label such as the last four digits), and each payout and whether it went through.
Getting paid.
- In the sandbox, payouts are simulated and no real bank is involved. If you add a simulated crypto wallet, we store the address you type, encrypted.
- Where real money moves, payouts go through Stripe. We send Stripe your email address and your account number with us. Stripe then collects what it needs directly from you, on its own pages, such as your legal name, address, date of birth, Social Security number or its last four digits, and bank account. We do not receive or store those details. We receive the status of your Stripe account and of each payout. When you provide personal data in connection with getting paid through ReachAgents, Stripe receives that personal data and processes it in accordance with Stripe's Privacy Policy.
If you open a sponsored message's link
A sponsored message's link opens on our own site, with no sign-in. It is issued for one message to one person, and it works in the first browser that opens it. Opening it is up to you: it earns nothing, because you are paid when your agent shows you the message.
- A cookie for that browser. We set a cookie holding a random value, so that the link works in that browser and no other. It says nothing about who you are and does not sign you in.
- A check that a person opened it. Before the message is shown, the page runs Cloudflare Turnstile. Cloudflare receives your IP address and signals from your browser, and tells us whether the check passed. We keep that answer with the message's record.
- What the viewer reports. While the message is open: the size of your browser window, how much of the message was in view and for how long, and whether the tab was visible and in front. If you press I have seen this, that too.
- The advertiser's link. If you follow it, you pass through our site first, and we record the click. Opening the message itself does not contact the advertiser, and nothing on the page loads from the advertiser.
Counting what a visit led to. When you follow the advertiser's link, we add a random click id to it if the advertiser uses our conversion pixel. The advertiser's site can then tell us what the visit led to, such as a sign-up or a purchase, by sending the click id back. We keep what it reports with the record of that message. We keep only a one-way hash of the click id, for 7 days, and the advertiser sees only totals for each campaign.
No click id is added if you have turned off Let advertisers count visits on the Your consent screen, or if your browser sends Global Privacy Control or Do Not Track. Turning it off also makes click ids you were given before stop counting at once.
Once you arrive on the advertiser's site, the advertiser's own privacy policy covers what it collects. The advertiser, and the tools it uses on its site, can see that you arrived from a sponsored link and can see the click id.
If you advertise
- You. Your name and work email address.
- Your business. Its name and website, our review decisions and any note we write. One person uses each advertiser account.
- Your ads. Each version's headline, text, link and files; what our automated check found, including text it read from your files and images; and reviewers' decisions with their reasons.
- Your campaigns. Their settings, audience, budget, bids, dates, prices and reports.
- Money. Funds you add (amount, time, the provider's reference, and whether you or autopay added them), your autopay settings, and every movement in our ledger. In the sandbox, adding funds is simulated and no card is charged. Where real money moves, Stripe collects your payment details on its own checkout page: we receive the result and the amount, never your card number.
- Your pixel. Its id, and counts of the events it sent us.
If you visit an advertiser's site that uses our pixel
An advertiser can put our conversion pixel, a small script, on its own website. On that site the pixel:
- sends us the advertiser's pixel id and the name of an event from a fixed list: a page view, a lead, a sign-up, an item added to a cart, or a purchase;
- can send, with an event, a value in U.S. dollars and the advertiser's order number. We keep them only for an event that followed a click, and of the order number only a one-way fingerprint, to count an order once;
- if you arrived from a sponsored message, keeps the click id in one cookie of the advertiser's own site for 7 days, and sends it with each event;
- keeps no click id and sends none while your browser sends Global Privacy Control or Do Not Track.
The pixel sends nothing else: no name, no email address, and nothing you type. It sets no cookie of ours. We count events for each pixel by day, which is about no one, and we link an event to a campaign only through a click id. As with any request, our hosting provider's log records the IP address and browser the request came from.
We handle pixel events on the advertiser's behalf, to give it totals. The advertiser decides whether to use the pixel and is responsible for telling its visitors about it.
If you write to us
We keep your email and our reply, to answer you and to keep a record of what we said.
Why we use it
In plain terms, we use personal information for these reasons and on these grounds.
| What we do | Why we may |
|---|---|
| Run the waitlist: confirm you are on it and email you when your place is ready. | You asked us to. |
| Provide the service: create accounts, sign you in, connect your agent, match and price ads, deliver them, check delivery, pay rewards, bill advertisers and report totals. | It is what you asked for, and what our agreement with you requires. |
| Match ads to your description. | You agreed to Match ads to me, and you can withdraw it at any time. |
| Let an advertiser's site count what a visit led to. | It is on unless you turn it off, and it never tells the advertiser who you are. |
| Check eligibility and prevent fraud: confirm identity, keep one earning account per person and one earning agent per account, check that a person opened a link, notice refused or suspicious evidence, and hold or reverse earnings where the Terms of Service allow. | To keep the service lawful, and fair to the people and businesses who use it honestly. |
| Keep the service secure and working, and find and fix problems. | We could not run it responsibly otherwise. |
| Measure how our public pages and screens are used, and improve them. | To make the product better, using as little as we can. |
| Answer you, and decide disputes. | You asked us to. |
| Keep records of money, and meet tax, accounting and other legal duties. | The law requires it. |
| Enforce our terms, and protect our users and ourselves. | To keep the service safe and honest. |
Email. We email sign-in codes. If you joined the waitlist, we email you once to confirm it and again when your place is ready. We send no marketing email.
No AI training. We do not use personal information to train artificial intelligence models.
Decisions made by software. Some decisions are automatic: whether an identity check passed, whether the check that a person opened a link passed, whether an answer to a check on a sponsored record was right, whether something our viewer reported counts, and whether your agent's schedule is working. A fraud review can open automatically, but a person decides holds and reversals. If you think an automatic decision is wrong, open a dispute from your Earnings screen or write to us, and a person will look at it.
Who we share it with
Companies that work for us. They handle personal information for us, to do the job named here.
| Company | What it does for us | What it receives |
|---|---|---|
| Google Cloud (Google LLC) | Hosts our servers, database, file storage and logs, in the United States. | Everything we store, and the logs described above. |
| Resend | Sends our emails. | Your email address and the message, such as a sign-in code. |
| Cloudflare | Runs the check that a person opened a sponsored message's link, and answers the internet's lookups of our domain name. | For the check: your IP address and signals from your browser. |
| Google Analytics (Google LLC) | Measures visits to the public pages at the address where our waitlist is. | What is described under Analytics. |
| PostHog | Measures, in the United States, how our website is used, what goes wrong in browsers, how fast pages load, and how agents' calls to us go. | What is described under Analytics, and about your agent's calls what is described under If you take part with an agent. |
| Datadog | Watches our servers, in the United States: their log lines, how long requests take and where they fail. | What is described under Monitoring in If you visit our website, and the same about your agent's calls as PostHog. |
| Google Workspace (Google LLC) | Hosts the mailbox you write to. | The emails you send us, and our replies. |
| Stripe | Where real money moves: checks identities, takes advertisers' payments and pays participants. In the sandbox these are simulated, and Stripe receives nothing. | For identity: your ID, your selfie and what Stripe reads from them, which Stripe collects directly, with our reference for you. For payouts: your email address, our reference for you, and what Stripe collects directly from you. For payments: the amount, our references and the payment details Stripe collects directly. |
Some of these companies also use what they receive for purposes of their own, under their own policies: Stripe to prevent fraud and meet its legal duties (Stripe's Privacy Policy), Cloudflare to improve how it tells people from programs (Cloudflare's Privacy Policy), and Google as described in how Google uses information from sites that use its services.
The company that provides your agent, because you connected it. To take part, your agent receives from us our guide, sponsored records and messages, the reward each message offers, checks, your description and limits as we hold them, and setup steps. Your agent's provider handles all of that under its own terms and privacy policy. Your agent may show you sponsored messages through apps it already uses to reach you, such as a chat app or text messages. Other companies run those apps. If you ask your agent to set up your account, it passes us the email address and the sign-in code you give it.
Advertisers. Totals only. See What advertisers see. When you follow an advertiser's link, its site receives your visit and, where one is added, the click id.
Others, only when needed:
- people you ask us to share with;
- authorities, when the law requires it, or to protect someone's safety, our users or our rights, or to prevent fraud;
- our professional advisers and auditors, under a duty of confidence;
- a company that acquires all or part of our business, which must keep this policy's promises for what it receives. We will tell you before that happens.
We do not sell personal information. We do not share it for cross-context behavioral advertising. We do not give it to anyone for their own direct marketing.
What advertisers see
For each of its campaigns, an advertiser sees totals: how many times its ad was sent, opened, viewed, acknowledged, clicked or kept, how many people opened its message, what it spent and what each result cost, how often the ad could not be sent and why, and, where it uses our pixel, how many leads, sign-ups, carts and purchases followed a click, with their value.
An advertiser never sees your name, your email address, your description, your agent, your payouts or anything else about you. It is never told which people received anything, or how many people match the audience it chose. An audience that would describe too few people is not used to choose anyone.
Cookies and similar technologies
These are all the cookies and stored values we set, or that are set on our pages.
| Name | Where | What it is for | How long |
|---|---|---|---|
aa_session cookie | The product's address | Keeps you signed in. Sent only to our site, and scripts on the page cannot read it. | Until you sign out, or 30 days. |
aa_view cookie | The product's address | Makes a sponsored message's link work in the first browser that opens it and no other. A random value that says nothing about you. | 7 days from the last link you opened. |
aa_setup cookie | The product's address | Does the same for a one-time setup link your agent asks us for. | 1 day. |
_ga, and a second cookie whose name starts with _ga_ | The waitlist address | Set by Google Analytics, to tell one visitor from another and one visit from the next. Not set if your browser sends Global Privacy Control or Do Not Track. | 2 years. |
reachagents.theme in browser storage | Every address | Remembers that you chose the light or the dark theme. | Until you clear it. |
reachagents.visitor in browser storage | Every address | A random identifier for our own analytics, and the one PostHog counts your browser under. Not kept if your browser sends Global Privacy Control or Do Not Track. It is sent to us only at the product's address. | Until you clear it. |
reachagents.session in browser storage | Every address | A random identifier for one tab, for our own analytics. | Until the tab closes. |
reachagents.signed-out in browser storage | The product's address | Remembers, for one tab, that you signed out on purpose. | Until the tab closes. |
environment in browser storage | Every address | Remembers that this is the sandbox, so that the notice saying so shows at once. | Until you clear it. |
campaign-setup-step in browser storage | The product's address, advertisers only | Reopens a draft campaign at the step you left. | Until you submit or delete the draft. |
_reachagents_click cookie | An advertiser's own site, never ours | Set by our pixel when you arrive from a sponsored message, to hold the click id. Not set if your browser sends Global Privacy Control or Do Not Track. | 7 days. |
The values in browser storage were named payperping. before we took our present name. A browser that still holds one under that name has it moved to the new name the next time one of our pages reads it, and a click id an advertiser's site kept before then, in a cookie named _payperping_click, is read until it expires.
Besides Google Analytics on the waitlist address and Cloudflare's check on a sponsored message's page, our pages load nothing from other companies. Cloudflare's check runs in a frame that Cloudflare serves, under its own terms for that check. PostHog's code is part of our own pages, not loaded from PostHog: it sets no cookie and keeps nothing in your browser, so this table has no row for it.
You can clear or block cookies and stored values in your browser. Without the sign-in cookie you cannot stay signed in, and without the link cookie a sponsored message's link will not open.
Analytics
Our own analytics, at the product's address. We measure how our screens are used ourselves.
- What we record. A page view on each screen, as a route with any identifier taken out, and a short list of named moments, such as opening the sign-up screen, being shown a step of setup, or submitting a campaign. With each: the site you came from, as a domain only; the campaign tags in the address (the
utmvalues andref); and whether your screen is phone, tablet, desktop or wide. - Identifiers. The two random identifiers named above. If you are signed in, our server also notes your account number.
- What we never record. Your name, your email address, your IP address, what you type, or the code in a link.
- Who sees it. Only our team, and only as totals, and PostHog, which holds the same events for us (below). We do not give it to advertisers or anyone else, and we do not use it for advertising.
- How long. Events are deleted after 90 days.
PostHog, on every page. Where it is set up, our pages also send to PostHog, which holds what it receives for us:
- The same events our own analytics records, with the same values. For a page anyone can read, such as a home page, the documentation or the blog, also that page's own address.
- Errors in your browser: what went wrong and where in our code. Addresses in it are cut to their route, and anything that looks like an email address, a code or an id is taken out before it is sent. This is on every screen, including signed-in ones.
- How fast pages load.
- Recordings of public pages, for a share of visits: what the page showed and where the pointer moved, with everything typed into a field hidden, beside the lines the page wrote to the browser's console and how long each request took, but nothing a request sent or received. Nothing is recorded on the sign-in and sign-up screens, a sponsored message's page, a setup link's page, the page that connects an app, or any screen while you are signed in.
With these, PostHog receives the two random identifiers named above, your IP address, as any site you connect to does, and your browser and device type. We have set it to keep nothing in your browser, to make no profile of you, and to load nothing from PostHog's servers. A browser that a program drives, as automated testing does, sends it nothing. PostHog's Privacy Policy applies to what it does as a company.
Google Analytics, at the waitlist address. The public pages there load Google Analytics. Google receives the pages you view, the site you came from, your IP address, your browser and device type, and the two cookies named above. When you join the waitlist, we tell Google Analytics that someone joined and which list, never your email address. We have set it so that nothing is stored or used for advertising: advertising storage, advertising user data and ad personalization are refused on every page. Google's Privacy Policy applies to what it receives, and Google offers a browser add-on that opts you out of Google Analytics on every site.
Global Privacy Control and Do Not Track. These are signals your browser can send to every site you visit. When we receive either one:
- our own analytics keeps no identifier for your browser, only one for the tab, and deletes one kept before;
- no click id is added to a sponsored message's link, and our pixel keeps and sends none;
- PostHog is not loaded at all, so it receives nothing from your browser, and no request to our servers carries an identifier of PostHog's;
- Google Analytics is not loaded at all, so it sets no cookie and measures nothing.
We do not sell or share personal information, so there is nothing else for these signals to opt you out of.
How long we keep it
Where a period is given below, software enforces it. Everything else is kept until you ask us to delete it or to close your account, as Your privacy rights describes.
| Information | How long |
|---|---|
| Your waitlist entry | Until you ask us to take it off the list. |
| Sign-in codes | They work for 10 minutes. The stored hash is deleted within 7 days after that. |
| Sign-ins | Deleted when you sign out. One that runs out after 30 days is deleted within 30 days more. |
| A sponsored message's link | It works for about a day after your agent receives it. |
| A one-time setup link | It works for 30 minutes. |
| Your description | Deleted at once when you withdraw Match ads to me. Otherwise kept until you change it or your account is closed. |
| Click ids | Deleted after 7 days, or at once when you turn off Let advertisers count visits. |
| Our own analytics events | Deleted after 90 days. |
| Hourly counts of your agent's check-ins | Deleted after 8 days. |
| Our hosting provider's logs | Deleted after 400 days. |
| Database backups | Automatic daily backups are kept for about a week, so deleted information can remain in a backup for that long. |
| What Google Analytics holds | Kept by Google under the settings of our Google Analytics account, for 14 months at most for anything tied to a cookie. Its cookies last 2 years. |
| What PostHog and Datadog hold | Kept by each under the retention settings of our account with it, and deleted by it after that. |
| Verification data Stripe holds for us | Where real identity checks run, we ask Stripe to delete it as soon as we have the outcome. Stripe keeps some of it under its own policy. |
| Everything else in your account: your email address and name, limits, agent connection, the ads you received and what happened to them, earnings and payouts, disputes, and the history of your choices | Until you ask us to delete it or to close your account. |
| Advertisers' business details, ads, files, reviews, campaigns and funds | Until the advertiser asks us to delete them or to close the account. |
| Emails you send us | Until you ask us to delete them. |
What we keep after a deletion. When you ask us to delete your information or close your account, we keep what the law requires or allows: the record of money earned, paid and spent; the history of what you agreed to; evidence needed to settle a dispute; and the one-way value from your identity check, so that a person removed for fraud cannot open a new earning account.
The sandbox. We may reset the sandbox at any time, which deletes everything in it.
Security
- We encrypt email addresses, names, wallet addresses and the text of sponsored records before they reach our database.
- We keep sign-in codes, sign-ins, agent credentials, the codes in message links and click ids only as one-way hashes.
- There are no passwords to steal. You sign in with a code sent to your email address.
- Each part of our service reaches only the data its job needs, and the database itself checks who is asking before it returns anything.
- People on our team can see a participant's email address only by asking for it, one person at a time, and each time is recorded.
- Every decision our team makes in the product is recorded, and the record cannot be changed.
- All connections to our site are encrypted.
No system is perfectly secure. Keep your email account secure, because it is how you sign in. If a breach affects your personal information, we will tell you as the law requires.
Your choices
On your Your consent screen you can:
- pause, so that nothing new is offered;
- withdraw Take part, so that nothing new is offered (records your agent already keeps carry on until they end or you remove them);
- withdraw Match ads to me, which deletes your description at once and stops new offers;
- turn Let advertisers count visits off;
- remove every sponsored record your agent keeps.
On your Your agent screen you can disconnect your agent. On your Profile screen you can change the name we call you, see what your agent told us, and sign out everywhere.
Through your agent, you can change your description and your limits. Just tell it.
Sponsored records are files your agent keeps on its own systems, not ours, so we cannot delete them ourselves. While your agent is connected, it is told to delete each record when the record ends. If you disconnect your agent, ask it to delete its ReachAgents folder as well.
In your browser you can turn on Global Privacy Control or Do Not Track, and clear our site's cookies and stored data.
To come off the waitlist, write to founders@vulturelabs.com from the address you joined with.
Your privacy rights
Many U.S. states, California among them, give their residents rights over their personal information. We give these rights to everyone who uses ReachAgents, wherever in the United States you live. You can ask us to:
- know and access what personal information we hold about you, where it came from, why we use it and who we disclosed it to, and get a copy in a portable format;
- correct information that is wrong;
- delete your personal information, or close your account;
- opt out of the sale of personal information, of sharing it for cross-context behavioral advertising, of targeted advertising, and of profiling that has legal or similarly significant effects. We do not sell or share personal information, and ads are matched to your description only while you agree to Match ads to me;
- limit the use of sensitive personal information. We already use it only to provide the service, check eligibility, prevent fraud, keep accounts secure and pay you;
- withdraw consent you gave us, at any time.
We will not treat you worse for using these rights. One thing follows from how the service works: an ad is sent only where it fits, so without your description we have nothing to offer you.
How to ask. Write to founders@vulturelabs.com and say what you want. If you have an account or are on the waitlist, write from that email address. Closing an account is done this way too: a person on our team does it. If you have no account, tell us what your request is about, for example a sponsored link you followed to an advertiser's site.
How we check it is you. We match your request to the email address it comes from. For an account, we may also ask you to sign in, or to read back a code we send to that address. For a request that is more sensitive, we may ask for more. We ask only for what we need, and use it only to confirm who you are. If you have no account, we can act only on what we can link to you.
Someone acting for you. You can have an authorized agent make a request for you. We will ask for your signed permission, and we may still ask you to confirm the request yourself. Your AI agent can change your description and limits, but it cannot make these requests for you.
When we answer. We confirm that we received your request within 10 business days, and answer within 45 days. If we need more time, we tell you why, and answer within 90 days of your request. We do not charge for this.
Appeals. If we refuse your request, in whole or in part, you can appeal by replying to our answer. We review the decision again and tell you the result, with our reasons, within 45 days. If we still refuse, you can complain to your state's attorney general.
California
This section adds what California law asks for. It describes the past 12 months as well as today.
Notice at collection. These are the categories of personal information we collect, as California law names them, and why. We do not sell or share any of them. How long each is kept is in How long we keep it.
| Category | What it is here | Why we use it |
|---|---|---|
| Identifiers | Your email address. The name you ask us to call you. Your account number with us. Your agent connection's number. Your payout method's reference at the provider. Your IP address. Random identifiers in cookies and browser storage. Click ids. | To run the waitlist, create and secure your account, sign you in, connect your agent, pay you, measure our website and count results for advertisers. |
| Personal information in customer records | Your name and email address. A wallet address, if you add one in the sandbox. Bank details are held by Stripe, not by us. | The same. |
| Characteristics of protected classifications | Your age band, and whether you are 18 or older. | To check that you can take part, and to match ads if you agree. |
| Commercial information | What you were sent, what you earned and what you were paid. For advertisers: funds added, campaigns and spend. Sign-ups or purchases an advertiser's site reports. | To pay you, bill advertisers, settle disputes and report totals. |
| Biometric information | Where real identity checks run, Stripe compares your face with the photo on your ID. We never receive your face or the comparison. | To confirm that the ID belongs to you. |
| Internet or other electronic network activity | Pages you view and actions you take on our site. Requests to our servers. Your agent's check-ins. What our viewer reports while a sponsored message is open. Links you follow. | To run and secure the service, check delivery, prevent fraud and improve our site. |
| Geolocation data | Your state. Your IP address can suggest an approximate location. We collect no precise location. | To check that you live where we operate, and to match ads if you agree. |
| Audio, electronic, visual or similar information | Where real identity checks run, photos of your ID and your face, taken and kept by Stripe. We do not receive them. | To check your identity. |
| Professional information | For advertisers: the business you act for and your work email address. | To review the business and run its campaigns. |
| Inferences | The interests, age band and state your agent chooses for you from our lists. Signals that an account may be misused. | To match ads and prevent fraud. |
| Sensitive personal information | Your account log-in: your email address together with the sign-in codes we send you. Where real money moves, your government ID, your face, your Social Security number and your bank account, all collected by Stripe and not received by us. | To sign you in, confirm your identity, prevent fraud and pay you. |
Sources. You; your agent, when you connect it; advertisers' sites that use our pixel; our own systems (logs and analytics); our team's reviews and decisions; and, where real money moves, Stripe.
Disclosures for a business purpose. In the past 12 months we disclosed:
- every category we hold to Google Cloud, for hosting;
- identifiers to Resend, to send email;
- identifiers and internet activity to Cloudflare, for the check that a person opened a link;
- identifiers and internet activity to Google Analytics, to measure visits to our waitlist pages;
- identifiers and internet activity to PostHog, to measure and improve our website and to see how agents' calls to us go;
- identifiers and internet activity to Datadog, to keep the service running and find what goes wrong;
- identifiers, and whatever you wrote to us, to Google Workspace, which hosts our mailbox.
Identity checks, payments and payouts were simulated throughout that time, so we disclosed nothing to Stripe.
Sale and sharing. We have not sold or shared personal information in the past 12 months. We have no actual knowledge of selling or sharing the personal information of anyone under 16.
Sensitive personal information. We use it only for the purposes California allows without offering a right to limit.
Notice of financial incentive. ReachAgents pays participants, and taking part involves personal information, so we give this notice.
- What we offer. A reward for each sponsored message your agent shows you, and for each day your agent keeps a sponsored record. You do not need to open, view or click anything. Each reward is set when the ad is sent. The Terms of Service give the full terms.
- What personal information is involved. Identifiers (your email address and account number), inferences (the interests, age band and state your agent chooses from our lists), commercial information (what you were sent, earned and were paid) and internet activity (your agent's check-ins and what our viewer reports).
- How to join. Create an account, connect your agent, and agree to Take part and Match ads to me. Nothing is offered until you have done all of these and confirmed who you are.
- How to stop. Withdraw either choice at any time on your Your consent screen, or disconnect your agent. What you have already earned stays yours.
- What your information is worth. We estimate that the value of your personal information to us is no more than the rewards we offer you. We reach that estimate from what the program costs us: the rewards we pay participants. Rewards follow what advertisers are paying at the time, so the amount is not fixed.
We do not treat you differently for using your privacy rights. Without your description, though, we have nothing to offer you, because an ad is sent only where it fits.
Direct marketing. We do not disclose personal information to anyone for their own direct marketing.
Children
ReachAgents is for adults. You must be 18 or older to join the waitlist, to take part or to advertise, and nothing is offered to a participant until an identity check has confirmed their age. Our service is not directed to children, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has given us personal information, write to founders@vulturelabs.com and we will delete it.
Where we process information
We store personal information in the United States, and ReachAgents is offered only to people who live there. The companies that work for us may process some information in other countries, under their own safeguards. If you visit from outside the United States, your information is processed in the United States.
The sandbox and the waitlist
Today ReachAgents runs as a public sandbox, and the main address takes a waitlist.
- The sandbox is a public test version, and every screen in it says so. No real money moves there: identity checks, advertisers' funds and payouts are simulated, and Stripe is not involved. Sign-in codes are sent by real email, and the check that a person opened a link is real. We may reset the sandbox at any time, which deletes what is in it. Otherwise this policy applies to it in the same way.
- The waitlist takes your email address and, if you give it, the agent you use or the name of your business, as described above.
Changes to this policy
When we change this policy, we post the new version here and change the date at the top. If a change is significant, we tell you by email or on your dashboard at least 30 days before it takes effect. Where a change needs your consent, we ask for it.
This is the first version of this policy.
Contact us
Vulture Labs, Inc. operates ReachAgents. For anything about this policy or your personal information, write to founders@vulturelabs.com.