Data Processing Addendum

Effective date: 22 October 2026

This addendum is between the customer ("you") and ThoughtPivot, Inc, a US corporation at 2937 East Grand Boulevard, Detroit, MI 48202, United States ("we"). It is part of the Terms of Service for Bytewells at https://bytewells.com/.

It applies when we process personal data in Customer Content on your instructions. For account, billing, and website data we are the controller, as described in the Privacy Policy. This addendum does not cover that data.

Customer Content

Customer Content is personal data in:

  • run input and output
  • datasets, key-value stores, and request queues
  • run logs
  • schedules and webhooks you configure
  • Actor source, where that source contains personal data

You are the controller of that personal data. We are the processor. You decide what an Actor collects and whether it includes personal data. We process it to host, build, and run Actors, to store and return the results, and to bill the compute those runs use.

A webhook delivers data to the address you set. That recipient is your provider. It is not our subprocessor.

Your instructions

Your instructions are to process Customer Content as needed to provide the service you configure: the runs you start, the storage you use, and the webhooks you create. We will tell you if an instruction would break data-protection law, and we may stop following it until it is changed.

You are responsible for having a lawful basis for the personal data you submit, and for the notices you give the people it is about. Do not ask us to process personal data you are not allowed to collect.

How long we keep it

You can delete datasets, key-value stores, request queues, and runs from the console or the API. A finished run is deleted after 30 days. An unnamed dataset, key-value store, or request queue is deleted after 30 days without activity. Named storage stays until you delete it.

After you close the account, or after a verified request to delete Customer Content, we delete what is still in the live system. We keep what we need for tax, accounting, security, or a legal claim. Copies in backups remain until the backup expires.

People and confidentiality

People who can reach Customer Content are limited to those who need it to operate the service, and they are under a duty not to use it for anything else. We do not sell Customer Content, and we do not give a developer a renter's name, email, runs, inputs, or outputs.

Security

The measures we use for Customer Content include:

  • TLS for connections to the service
  • encryption at rest on the production database and object storage
  • separation so one customer cannot read another customer's storage
  • run credentials that can reach only that run's storage
  • sandboxed execution of Actor code
  • access to production systems limited to operators who need it

On a written request we will describe these measures and answer reasonable questions about them. We will not send you a report we do not have.

Subprocessors

We use these subprocessors for Customer Content:

  • DigitalOcean, LLC (United States). Hosting, managed PostgreSQL, managed Redis, object storage (Spaces), and the machines that build and run Actors. Production customer content is stored in Frankfurt, Germany.

We will update this page at least 30 days before a new subprocessor starts processing Customer Content, unless a shorter period is needed to replace a subprocessor that has failed or become a security risk. If you object, you can stop sending the affected Customer Content before the change takes effect. Closing the account is the other option.

International transfers

ThoughtPivot, Inc is established in the United States. Production Customer Content is stored in Frankfurt. Where we transfer personal data out of the European Economic Area or the United Kingdom and the transfer needs a safeguard, the European Commission's Standard Contractual Clauses, or the UK International Data Transfer Addendum, are incorporated into this addendum and apply to that transfer.

Requests from people

You can export and delete Customer Content through the console and the API. If someone contacts us about personal data in your Customer Content, we will refer them to you when we can tell the request is yours, unless the law requires us to answer. We will help you respond when the request is one we are in a position to carry out and you cannot do it yourself with the product.

Breaches

If we become aware of a personal-data breach affecting Customer Content, we will tell you without undue delay, and where we can, within 72 hours of becoming aware. The notice will describe what we know about what happened, the data affected, and what we are doing about it.

Liability and law

To the extent the law allows, we are not liable for lost profits, lost data, or other indirect damage, and our liability for a claim is limited to the fees you paid us for the service in the three months before the claim. These limits do not apply where the law does not allow a limit. The same limits are in the Terms of Service. Mandatory data-protection law of the European Economic Area or the United Kingdom still applies to processing of people there.

This addendum lasts while we process Customer Content. Deletion, confidentiality, and the duties that have to survive by law continue after it ends.

Contact

Privacy questions, deletion requests, and subprocessor objections: use the contact form and put “Privacy” in the message. We have not appointed a representative in the European Union or the United Kingdom.