Skip to content
Bindato

Legal

Privacy Policy

Effective September 15, 2026Version 2026-09-15

What we collect, how we use it, how long we keep it, who else processes it, and how to exercise your rights. Where the security architecture is concerned, this policy points at /security rather than repeating it.

1. Scope and who is responsible

This Privacy Policy describes how Bindato handles personal information when you use the Bindato service, visit this website, or contact us. It applies alongside the Terms of Service.

Two kinds of personal information pass through the service, and our role differs for each. For the data inside your connected systems — your customers' orders, addresses and the like, which we move and store on your instructions — you are the controller and we are your processor: we act on your configuration and this policy does not decide what is done with that data; your own privacy policy does. For the information about your account and your use of the service — your name, work email, sign-in activity, billing and usage — we are the controller.

2. What we collect

We collect the following, and nothing we have not listed here:

  • Account data: your name, work email address, business name, the role you hold on the account, the plan you chose and the times you sign in. Payment card details are collected by our payment provider directly and never reach our servers; we hold a reference to your subscription and your invoices.
  • Connection credentials: the API keys, tokens or OAuth grants you give the service to reach your connected systems. They are encrypted at rest under a data key unique to each credential, and decrypted only in the process that is about to call that system.
  • Run records: for each flow execution, the trigger and every step's input, output and outcome. Because flows move commercial data, these records include the payloads your connected systems exchanged — orders, customer names and addresses, shipments, inventory. They exist so you can see what moved and debug what did not.
  • Marketplace data: where you connect a marketplace such as Amazon, the order, line-item and buyer shipping information that marketplace returns for the orders you asked us to sync, obtained only through the marketplace's authorised API with the roles you granted. It is used solely to move those orders to your other connected systems, is held in run records for your plan's retention period, is never sold or used for advertising, and is deleted with the connection or the account.
  • Usage and metering: counts of runs per calendar month per account, the limits of your plan, and the notifications the service raised. These are counts and identifiers, not payloads.
  • Contact-form submissions: the name, company, work email, store URL and message you send us from /contact, with the page you sent it from.
  • Server logs: each request's path, method, status, timing, a request identifier and the client IP address. The IP address is used for rate limiting and to investigate abuse; request and response bodies and credential fields are redacted before a log line is written.

3. How we use it

We use personal information only to:

  • run the flows you have configured, and keep the run records that show what they did;
  • operate your account: sign you in, invite the people you add, and let owners see the account's audit trail;
  • meter usage against your plan and bill you through our payment provider;
  • reply to you when you contact us, and set up a demo when you ask for one;
  • send transactional email — a password reset, an invitation, a notice about billing or a change to these documents; we do not send marketing email to account holders without asking first;
  • keep the service secure: rate-limit abusive traffic, investigate incidents, and find a failure from the reference you quote to us;
  • meet legal obligations, including tax and accounting records.

4. How long we keep it

Run records are kept for the retention period of your plan, published on /pricing, and then deleted by a scheduled job. If you change plans, the new plan's period applies from the change and older records are pruned; the dashboard says so before you confirm a downgrade.

Account data is kept for the life of the account. When an account closes we make Customer Data available for export on request within thirty days, as the Terms of Service describe, and delete it afterwards, subject to backups that expire in the ordinary course and to records we must keep by law, such as invoices.

Connection credentials are deleted when you delete the connection or when the account closes. Contact-form submissions are kept until handled, and for no longer than twelve months. Server logs are rotated on a short cycle appropriate to their purpose of security and debugging.

5. Who else processes it (subprocessors)

We use a small number of providers to run the service. Each processes personal information on our instructions, for the purpose stated:

  • DigitalOcean — hosting of the application, its Postgres database and its Redis instance, in the United States. Everything the service stores lives here.
  • Stripe — billing. Stripe collects and holds your payment card details and issues invoices; we hold subscription and invoice references.
  • Resend — transactional email: password resets, invitations, billing and legal notices, and the notification we receive when you submit the contact form.

6. Security

The security page at /security describes what the architecture does — how tenant data is isolated in the database, how connection credentials are encrypted, how webhooks are verified, how logs are redacted and what is audited — with the file that does each thing, and it lists plainly what we do not claim. We do not repeat those statements here, and this policy does not add to them.

No system is perfectly secure. If we become aware of a breach affecting your personal information or your Customer Data, we will notify you without undue delay, tell you what we know, and cooperate with any notification you must make to your own customers or to a regulator.

7. International transfers

The service is hosted in the United States. If you or your customers are elsewhere, the personal information the service handles is transferred to and stored in the United States. Where the law of your country requires a specific mechanism for that transfer, contact us and we will put the appropriate terms in place.

8. Your rights

Depending on where you are, you may have rights over your personal information, including rights you may have under the GDPR or the CCPA: to access it, to correct it, to have it deleted, to receive a copy in a portable form, to object to or restrict certain processing, and not to be discriminated against for exercising a right. You can exercise these rights by writing to the legal contact below; we will verify the request and answer within the time the applicable law allows.

Where the personal information concerned is inside your Customer Data — your own customers' orders, for instance — we are your processor, and a request from one of your customers is for you to answer. We will help you do so, including by exporting or deleting the records concerned on your instruction.

9. Cookies

This website sets no cookies. There is no analytics script, no advertising pixel and no third-party embed on any page of it; the contact form sends what you type to our own API and nothing else.

The dashboard sets one cookie: a session cookie that keeps you signed in. It is marked httpOnly and same-site, is sent only over a secure connection in production, and expires after a period of inactivity. It is not used to track you across other sites. No advertising cookies are set anywhere.

10. Children

The service is for businesses and is not directed at anyone under eighteen. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, write to the legal contact below and we will delete it.

11. Changes to this policy

We may update this policy. When we do, we will publish the new version at /privacy with a new effective date, and notify account holders by email or in the dashboard before a material change takes effect. The version of this policy is its effective date.

12. Contact

Questions, requests and complaints about privacy go to legal@bindato.com, or by post to Bindato, 5201 Great America Pkwy, Suite 320, Santa Clara, CA 95054. If you are not satisfied with our answer, you may also have the right to complain to a data-protection authority where you live.