Privacy Policy

What we process, why, on what legal basis, and what you can do about it.

Last updated: 25 October 2026

1.Controller

The controller for the processing described here is:

Max Benz
Am hohen Stein 36a, 01189 Dresden, Germany
legal@saasbid.io

We have not appointed a data protection officer. The thresholds of § 38 BDSG are not met; we will appoint one and publish the contact details here if that changes.

2.No tracking, no consent banner

saasbid.io runs no analytics, no advertising pixels and no cross-site tracking. We do not profile visitors and we do not sell data.

The only information stored on your device is what the service cannot work without: your login session and, if you switch it on, the preview mode flag. Both are strictly necessary within the meaning of § 25 Abs. 2 Nr. 2 TDDDG, so no consent banner is required. Should we ever add analytics, we will ask for consent first.

3.Visiting the website

The site is delivered by Netlify, Inc., 512 2nd Street, San Francisco, CA 94107, USA. Netlify processes server log data on our behalf, including your IP address, the page requested, the time of the request, the referring page and your browser and operating system.

Purpose and legal basis. Delivering the site, keeping it secure and diagnosing faults. Art. 6(1)(f) GDPR, our legitimate interest in operating a functioning and secure website.

Transfer to the USA. Netlify is a US provider. The transfer is safeguarded by a data processing agreement including the European Commission's standard contractual clauses and, where Netlify is certified, the EU-US Data Privacy Framework. US authorities may in principle be able to access data held by US providers, and you may not have the same remedies as in the EU.

Retention. Log data is deleted or aggregated after a short period; we do not build long-term profiles from it.

4.Accounts

You register as a buyer or as a vendor. We process your email address, your password in hashed form, your name, your company name, whether you buy or sell software, for vendors the product website you give, and for buyers the category or vendor you came from, so your first request can start there.

Vendor confirmation. To link a vendor account to a product we compare the domain of your email address with the product's domain and send a one-time confirmation link to your address; we store a hash of that link, never the link itself. Where the domains differ, we check the claim manually.

Legal basis. Art. 6(1)(b) GDPR, performance of the contract of use you enter into by registering. Public profile content of a listed product is published deliberately; that is the purpose of the directory.

Accounts and listing data are held by Supabase Inc., 970 Toa Payoh North, Singapore, on infrastructure in the EU (AWS eu-west-1, Ireland), as our processor under Art. 28 GDPR. Data therefore stays in the EU in normal operation; support access from outside the EU is covered by standard contractual clauses.

Sign-up and sign-in attempts. When the registration or login form is submitted we record the attempt, the email address it was submitted with, whether it succeeded and, if it did not, the reason given. We use this to see where people fail on the form and to notice repeated failed attempts against an address. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in a working sign-up and in the security of the accounts on it. These records are deleted after 90 days and are visible to us alone.

Retention. For as long as the account exists. After deletion we keep what commercial and tax law requires us to keep, up to ten years under § 147 AO and § 257 HGB for invoices and booking records and restrict processing of that data to those purposes.

5.Requests, offers and introductions

What a request contains. The category, title and background you write, your company size, number of users, industry and country, your requirements, integrations, hosting and security needs, budget range, timeline and current tool, the vendors you shortlisted, and your contact details: company, name, email address, and if you give them role and phone number.

Who sees what. We read every request before it is sent, to keep requests genuine. After approval, the vendors you shortlisted (at most five) see the request without your company, name and contact details. A vendor receives your contact details only when you accept its offer, and only that vendor. From then on that vendor is an independent controller for your contact details and processes them under its own privacy policy; our terms allow it to use them only to follow up on your request.

Offers. Offers contain what the vendor writes: price, answers to your requirements, implementation time, contract terms and a message, plus the vendor's name. Offers are shown to the buyer of the request and to us.

Legal basis. Art. 6(1)(b) GDPR. Passing the anonymous request to your shortlist and releasing your contact details to a vendor happen because you instruct us to, by submitting the request with the consent checkbox and by accepting an offer; that is the service you use. Reviewing requests also serves our legitimate interest in keeping the platform free of fake or abusive requests (Art. 6(1)(f) GDPR).

Matching. To suggest a shortlist we score vendors against your requirements (company size fit, documented capabilities, integrations, hosting, certifications). This assesses vendors, not you, and you decide the shortlist yourself; it is not an automated decision within the meaning of Art. 22 GDPR.

Retention. Drafts until you delete them. Submitted requests and their offers for as long as your account exists, so you can go back to them; write to us to have a single request deleted earlier. Contact details already released to a vendor are then held by that vendor, and we will tell it about your deletion request.

6.Payments

Buyers never pay. Vendors buy introduction credits through Stripe; payments were also used for directory listings bought before 25 October 2026. We store which vendor bought how many credits, the amount and the Stripe session reference, and which accepted introduction used a credit.

Payments run through Stripe Payments Europe, Ltd., The One Building, 1 Grand Canal Street Lower, Dublin 2, Ireland. Stripe does more here than move money: it acts as the seller of record for the payment, issues the receipt or invoice, and determines and remits any tax due on it.

Because of that, Stripe is an independent controller for the payment, not our processor. It collects the billing details, tax identification number and payment data you enter, and processes them for its own purposes, completing the payment, preventing fraud and meeting its financial and tax obligations. Its privacy policy governs that processing; see stripe.com/privacy.

We never see or store your card details. What reaches us is the confirmation that a payment succeeded, the amount, and the listing it belongs to, the minimum needed to record it. Legal basis: Art. 6(1)(b) GDPR for performing our part of the contract, and Art. 6(1)(c) GDPR for the records we are required to keep.

7.Emails we send you

We send only emails tied to your account and what you do on it:

  • a welcome message once, when you register;
  • the confirmation link when you link a vendor account to a product;
  • for buyers: when your request goes live and when a new offer arrives;
  • for vendors: when a new request shortlists your product and when a buyer accepts your offer, including the contact details the buyer released.

Legal basis. Art. 6(1)(b) GDPR, all of them are part of the service you use. They are not advertising, and we do not send newsletters from this address.

Delivery is handled by Twilio SendGrid (Twilio Inc., 101 Spear Street, San Francisco, CA 94105, USA) as our processor under Art. 28 GDPR. SendGrid receives your email address and the content of the message. The transfer to the USA is covered by the standard contractual clauses in that agreement and, where Twilio is certified, the EU-US Data Privacy Framework.

8.Requests to third parties from your browser

One feature causes your browser to contact a third party. We list it because the request carries your IP address.

  • Product logos. Listing logos are served from our own storage in the EU. For a listing whose logo we have not cached yet, the image is loaded from Google's favicon service (google.com/s2/favicons), operated by Google Ireland Limited, which then receives your IP address and the domain of the product whose logo is displayed. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in recognisable listings.

Fonts are served from our own servers. No connection is made to Google Fonts, and no font request discloses your IP address to a third party.

Embedded videos are shown only when a business user has added one, and only after you open that tab; YouTube then receives your IP address as the video is loaded.

9.Reviews and public content

If you submit a review, we process the name, role and company size you supply, your rating and your text, and publish them with the listing. An email address, if given, is used only to contact you about the review and is not published.

Legal basis. Art. 6(1)(b) GDPR for publishing what you asked us to publish, and Art. 6(1)(f) GDPR for checking submissions to keep the directory trustworthy. Please do not include personal data about other people in review text.

10.Who receives your data

Vendors receive request data as described under "Requests, offers and introductions": anonymous until you accept their offer. Beyond that and the providers named above we pass data on only where we have to: to tax advisers, auditors and authorities where the law requires it, and to legal advisers where we need to establish or defend legal claims.

All processors act on documented instructions under data processing agreements pursuant to Art. 28 GDPR.

11.Your rights

You have the right, in respect of your personal data, to:

  • access it (Art. 15 GDPR);
  • have it rectified (Art. 16 GDPR);
  • have it erased (Art. 17 GDPR);
  • have its processing restricted (Art. 18 GDPR);
  • receive it in a portable format (Art. 20 GDPR);
  • object to processing based on Art. 6(1)(f) GDPR, on grounds relating to your particular situation (Art. 21 GDPR); and
  • withdraw consent at any time, with effect for the future.

Write to legal@saasbid.io. You also have the right to lodge a complaint with a supervisory authority, for example the Sächsischer Datenschutzbeauftragter.

Automated decision-making. There is none. The matching scores vendors, not people, and the buyer decides the shortlist.

12.Whether you have to provide data

Browsing requires no personal data beyond what is technically necessary to deliver the page. To open an account, send a request or answer one, the data marked as required in the relevant form is necessary; without it we cannot provide the service.

13.Changes to this policy

We update this policy when the service or the legal position changes. The current version always applies and is dated at the top of this page.