An honest word on “anonymous”
Identity-minimizing, not zero-knowledge.
Privacy is the product here, so we would rather be precise than sound impressive. Rbundle is identity-minimizing, not zero-knowledge. We collect the least we can, we do not store a Buyer's identity or contact details against an account, and we cannot leak what we do not hold — but a sign-in email exists, and ordinary server logs exist. This policy sets out exactly what we hold and what we do not.
Anonymity also runs in one direction. Providers are not anonymous: a firm that proposes is named and visible to the Buyer considering it.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
What we collect from Buyers
A sign-in email, banded business attributes, your answers, and ordinary technical data.
- A sign-in email address, used for magic-link sign-in and for notifications. It is never shown to Providers.
- Business attributes needed to scope and price work — entity type, size band, industry, states of operation, revenue band where it genuinely changes a quote. These are held in bands rather than exact figures wherever a band will do.
- Your answers to the Common RFP, including free-text answers, and your stated preferences. These are stored under a pseudonymous account identifier rather than a name.
- Your answers to short, optional surveys we show at a few moments, such as sending your first Request. They are stored apart from your account, with the service and the month but never the Request, and any comment you add is read only by our staff. Because they are not linked to your account, we do not look them up or delete them by account later, so leave anything that identifies you out of a comment.
- Your IP address and basic diagnostic data — errors, request logs — used to operate the service and to prevent fraud and abuse.
We do not store, for a Buyer: legal or trading name, individual names, street address, phone number, EIN or other direct identifiers. This is enforced in the schema, not only in policy: the data model is scanned so that no table owned by a Buyer account can carry an identity field. Outside an account, we keep a name or email you give us in three places: a message you choose to send us and a call you choose to book with us, both described in "When you write to us", and a provider's scoping form you fill in, which we hold for 7 days in case the email to that provider fails, then delete.
While you are signed out, a Request you are building is held in your own browser and is not written to our servers. Asking us to add a service does record that request, because there would be no point otherwise. Joining a waitlist needs an account, because the waitlist is attached to one.
What we collect from Providers
Firm identity. Providers are meant to be identifiable.
From a Provider we collect firm identity and contact details (its legal name, entity type, state of formation, address, main phone and website, if it has one), the services and jurisdictions the firm offers, seat and member information for the firm's users (including each user's name, title and phone number), and the Proposals it submits together with the documents attached to them. None of this is anonymised, because a Buyer must be able to see who is proposing.
- Your answers to short, optional surveys we show at a few moments, such as sending your first proposal. They are stored apart from your account and your firm, with the service and the month but never the Request, and any comment you add is read only by our staff. Because they are not linked to your account, we do not look them up or delete them by account later, so leave anything that identifies you out of a comment.
The one moment identity is exchanged
At selection, to one firm, and not into our database.
When a Buyer selects a Proposal, the Buyer enters the contact details needed to begin work. Those details pass through to that single selected Provider. They are not written to our database, our logs or our analytics. Providers that were not selected are told only that the Buyer chose elsewhere.
There is one exception and it is opt-in and off by default. A Buyer sending a Request directly to Providers it names may choose to identify itself to those Providers up front. Where a Buyer chooses that, the contact information is stored in a single dedicated record scoped to that invitation, and nowhere else.
One thing we cannot do: once a Provider has your identity, deleting it from our systems removes it from our custody, not from theirs.
How we use information
To run the marketplace, route work correctly, stop abuse, and understand the market in aggregate.
- To deliver the service: build and send Requests, route them to eligible Providers, deliver Proposals, and send the notifications that go with each step.
- To prevent fraud, abuse and violations of the Terms, and to keep the Marketplace secure.
- To provide support, including looking up a Request by its code.
- To understand, in aggregate, what the market asks for and what it is offered — which services are requested, at what price and turnaround, and with what outcome.
We keep what you tell us and what the marketplace itself does. We do not watch how you use the application — what you look at, in what order, or for how long — and we build no record of it. Where we record how a piece of work turned out, that comes from what a party tells us, not from observing you. No Provider is shown a Buyer's history across Requests.
Before Rbundle opens. Until Rbundle opens to everyone, only email addresses on our approved list can sign in. We keep that list only to decide who can sign in, and we delete it once sign-ups open. If you sign up before then, we keep your email address so we can email you once when Rbundle opens.
When you write to us
Your message, and only what you choose to add.
When you write to us through the Contact Us form, we store your message together with what it is about and anything else you give us: whether you would like a reply, your name and an email address if you would, a Request or Engagement code, or what kind of user you are. What your message is about and the message itself are always required; your name and email are needed only if you ask for a reply. The message is kept apart from any account. A copy is emailed to our support inbox. It stays until our staff delete it. If you include a Request or Engagement code alongside your name, you are telling us which Request or Engagement is yours; we use that only to answer you.
When you book a call with us, the booking page asks only for your name and email, and we keep the booking in our calendar until our staff delete it. Please leave out Request and Engagement codes when you book; send anything about a specific Request or Engagement through the Contact Us form. Video calls on Google Meet are transcribed, and Google shows everyone on the call that transcription is on; we keep the transcript until our staff delete it. Phone calls and voicemails are transcribed too. We keep transcripts and voicemails until our staff delete them.
Who we share it with
Processors that run the service, Buyers who receive a Provider's messages and Proposals, and legal process. That is the list.
We do not sell your data. We share it only with the service providers that process it on our behalf under equivalent obligations, with the selected Provider in the selection flow described above, and where the law requires it or where sharing is necessary to prevent fraud, abuse or harm. If you are a Provider, a Buyer you message or send a Proposal to sees your firm's name and the name, title and phone number of the user who wrote or sent it; it does not see your firm's address or legal details.
If Rbundle receives a subpoena, court order or other legal process seeking information about you, we will notify you before disclosing it, unless we are legally prohibited from doing so, or we reasonably believe notice would risk death or serious physical injury or would interfere with a report of child sexual exploitation.
The processors we rely on to run the Marketplace, as of November 19, 2026:
- Vercel Inc.
- Application hosting and delivery.
- Supabase Pte. Ltd
- Managed Postgres database, authentication, and file storage for Proposal documents. Data is held in the United States.
- Plus Five Five, Inc. d/b/a Resend
- Transactional email — sign-in links and service notices.
- Cloudflare, Inc.
- Bot protection (Turnstile) on the sign-in, sign-up and report forms. It receives your IP address and information about your browser when you use those forms, never your email address.
- Google LLC
- Appointment booking and video calls (Google Calendar and Google Meet), when you book a call with us. It receives the name and email you give when you book and the time you choose, carries the call itself, and stores its transcript.
- Dialpad, Inc.
- Our business phone line. It receives the number you call from, the time and length of the call, and any voicemail you leave, and transcribes the call and voicemail.
Rbundle also uses ordinary business tools — email, documents and a customer-relationship system — for company correspondence with people who contact us directly. Anonymous marketplace Requests are deliberately kept out of those systems.
We will post a change to this list here at least 30 days before we add a processor of our own choosing. When one of our processors changes its own sub-processors, we post a notice of that change here promptly after it notifies us.
Affiliates
People who refer businesses and firms to Rbundle, and what each side sees.
Affiliates are people and companies approved by Rbundle to share links to the platform. When you arrive through an affiliate's link, we set the rb_aff cookie described in our Cookies Policy. If you then send a request, or a firm sends a proposal, from that visit, we record which affiliate link it came from.
An affiliate never learns who you are. They can see what a business is asking for, with no buyer name, company, address, email or phone number. Their dashboard shows monthly totals for each of their links: visits, requests sent, engagements and commission. It never lists individual buyers, requests or engagements.
If you apply to be an affiliate, we collect your name and your email address. We use them to decide your application, to run the program and to pay you. We do not store tax forms, tax identification numbers or bank details; those are exchanged directly with the Rbundle team, outside the platform.
Retention, closure and erasure
Closing an account severs your login and cancels live work. The records stay, severed from you.
You may close an account at any time from your account settings, and closure is immediate. When you do:
- The account's link to your sign-in is severed. If it was the last account under that email, the sign-in itself is deleted.
- Live Requests are canceled so that Providers can no longer respond to them, and a Provider's outstanding Proposals are withdrawn.
- Any identity you revealed to a Provider through a Direct Invitation is deleted from our systems.
- For a Buyer, the documents Providers attached to Proposals on your Requests are deleted, and your messages and your reasons for marking a milestone "Not yet" are replaced with a note that they were removed.
- For a Provider, closing the firm withdraws its live Proposals and marks the firm closed. Its past Proposals stay on the record under the firm's name. A document attached to a Proposal is deleted on the schedule in "Proposal documents" below.
What is kept, and we would rather be plain about it: your Requests, answers, standing Proposals and any Engagement that followed are retained as records of what the market asked for and what it was offered. Closing your account does not alter or delete those records. What it does is sever the account they belong to from your sign-in and from any identity you revealed, so that the account persists only as a pseudonymous number. Where our own staff recorded how an engagement turned out, that record names the staff member who entered it, not you. A Proposal that was standing when a Request closed is kept as market data whether or not it won. Drafts you never completed and Proposals that were withdrawn are kept on the same terms as everything else: severed from your sign-in, not deleted. The documents attached to them follow the schedule in "Proposal documents" below. If you are a Provider user, your name, title and phone number stay on the messages you wrote after your seat is closed, so the Buyer's record of the conversation stays whole.
When a Buyer changes a Request after Proposals were made against it, the earlier version and the Proposals made against it are kept for at least four years after the later of the Request closing and the Engagement ending, as the record of what was asked and what was offered. If the Buyer asks us to delete their data, the earlier version is emptied as described in "Deletion on request" below, and the Proposals stay as the Provider's record.
Closing an account never prevents you from signing up again later.
Proposal documents. A document a Provider attaches to a Proposal is deleted from our storage 90 days after the work it was for ended: the Engagement closed, or the Request closed or was withdrawn without one. It is deleted sooner if the Buyer closes their account, or asks us to delete what they shared with that Provider; then every document that Provider attached to a Proposal on that Buyer's Requests is deleted at once. After that, neither the Buyer nor the Provider can open it on Rbundle, so keep your own copy of anything you need.
What each side wrote. When a Buyer closes their account or deletes what they shared with a Provider, we remove what the Buyer wrote, not what the Provider wrote. A Provider's Proposals and milestones stay as its record of the work, under the firm's name. Messages from both sides are deleted 90 days after the work ended.
Deletion on request. If you ask us to delete your data, through Your privacy rights in your settings or the Privacy request page, and confirm the request from your sign-in email, we delete a Buyer account's data instead of only severing it. That covers your company profile, your Requests and saved Requests and their answers, your Bundles, your provider preferences and their history, your invitations to firms, the messages you wrote, your ratings, your survey and notification settings, your waitlist entries, and any message you sent us through the contact form that quotes one of your codes. Where a Provider sent a Proposal on one of your Requests, the Request is kept as an empty record holding only the service and its dates, so that the Provider's Proposal, milestones and any Engagement stay as its record of the work; nothing you wrote stays in it. Payment records, invoices, refunds and disputes, and our staff's audit records, are kept where the law or a dispute requires, with nothing you wrote. Your account is kept as an empty record holding only its pseudonymous name, its type and the dates it was opened and closed, so that those records still point to something, and we keep the record of your deletion request. For a Provider or staff account, write to info@rbundle.com and we will handle the request individually.
Your rights and choices
Get a copy of your data, correct or delete it, close your account, appeal, or write to us.
A Provider can export any Request or Bundle it received to CSV or Excel from its own page; a Bundle exports as one tab per service. To ask for a copy of your data, a correction, or deletion, use Your privacy rights in your settings, or the Privacy request page if you can't sign in. We confirm a request with a link to your account's sign-in email, never by asking who you are, and reply within 45 days of that confirmation. If you use a provider or staff account, are filing for someone else, or have no account, write to info@rbundle.com. You can close an account from your settings, as described above.
Because we hold so little that identifies a Buyer, the sign-in email is generally the only way we can connect a request to an account. Keep it current.
Depending on where you live, US state privacy laws, including those of California, Colorado, Connecticut and Virginia, give you the right to know what personal information we hold about you and how we use it, to get a copy of it, to correct it and to have it deleted. They also give you the right to opt out of the sale of your personal information, of its sharing for cross-context behavioral advertising, and of profiling that produces legal or similarly significant effects. We do none of those, so there is nothing to opt out of; we also treat a Global Privacy Control signal from your browser as that opt-out. We do not collect sensitive personal information as those laws define it, and we will not treat you differently for using any of these rights.
You may make a request through an authorized agent. The agent writes to info@rbundle.com with your signed permission, and we may confirm the request with you directly.
If we decline a request, in whole or in part, we will tell you why. You may appeal by writing to info@rbundle.com with "Appeal" in the subject within 45 days of our answer. We answer an appeal within 45 days and explain the result. If we deny your appeal, you may contact the attorney general of your state.
If you are in the European Economic Area, the United Kingdom or Switzerland, Rbundle, LLC is the controller of your personal data. Besides the rights above, you may ask us to restrict or stop processing it, to give it to you in a portable form, and to stop processing that relies on your consent, without affecting what we did before. We answer within one month of confirming your request; where the law allows, we may extend that by two months and will tell you if we do. You may also complain to the data-protection authority where you live or work.
Where the GDPR applies, we process your data to perform our contract with you (your account, your Requests, Proposals and Engagements, and the emails that go with them); for our legitimate interests in keeping the Marketplace secure, preventing fraud and abuse, keeping the record of what the market asked for and was offered, and understanding the market in aggregate, which we have weighed against your rights; to comply with the law; and with your consent, for the optional surveys. How long we keep each kind of data is set out in "Retention, closure and erasure" above.
Security
Managed infrastructure, access control at the database, and a breach notice if it matters to you.
We take reasonable and appropriate measures to protect information against loss, misuse and unauthorised access. Access control is enforced at the database layer rather than only in the application, sign-in is passwordless by magic link, and Proposal documents are held in private storage reachable only through short-lived signed links.
If a security breach materially affects your information, we will notify you as soon as we can and report what we did in response.
Please do your part: keep access to your sign-in email secure, and tell us immediately if you think your account has been compromised.
Where we operate
United States.
Rbundle is operated from the United States and the data is stored there. If you use the Marketplace from elsewhere, you understand that your information will be transferred to, stored and processed in the United States, where data-protection law may differ from that of your own country.
Where the GDPR or the UK GDPR applies to a transfer to one of our processors, that transfer relies on the Standard Contractual Clauses in the processor's data-processing agreement.
Other sites, changes and contact
Our policy covers our site. We will post changes here.
The Marketplace links to sites we do not control. This policy does not apply to them; read theirs.
We may update this policy. The date at the top reflects the current version, and material changes take effect when posted.
Questions, complaints or requests: info@rbundle.com, or write to Rbundle, LLC, P.O. Box 1971, Apex, North Carolina 27502.