Privacy Policy
Effective date: 10 November 2026
Bytewells at https://bytewells.com/ is operated by ThoughtPivot, Inc, a US corporation at 2937 East Grand Boulevard, Detroit, MI 48202, United States. ThoughtPivot, Inc is the controller of account, billing, waitlist, contact, and audience data on this page.
When a customer puts personal data into a run or into storage, that customer is the controller and we are the processor. That processing is described in the Data Processing Addendum.
To ask about this policy or to exercise a right listed below, use the contact form and put “Privacy” in the message.
Accounts
Creating an account collects your email address, your name, a password, and a username if you choose one. If you do not choose a username, we create one from the email address. We store the password as a hash. We also store the organization the account belongs to, API token names and a short preview of each token, and when the account and token were created and last used. We store a hash of the token, not the token itself.
We use this to provide the account, sign you in, and protect the service. You sign in with email and password. Login and sign-up with Apify are not available. The basis is Article 6(1)(b) GDPR for the account, and Article 6(1)(f) for security records such as when a token was last used.
Billing
When you pay, or when you publish and get paid, Stripe processes the card payment and, for developers, the identity and bank checks. We store a Stripe customer id, rental, pass, and invoice status, the credit ledger, and, for a developer, the payout country, the Stripe Connect account id, and the earnings ledger. We do not store the full card number.
The basis is Article 6(1)(b) for providing the paid service, and Article 6(1)(c) where we have to keep a record for tax or accounting. Card charges for rentals, passes, and compute are made on our Stripe account. A developer's share is transferred to their Stripe account later. The developer does not charge the card.
Importing from Apify
An Apify account does not sign you in. To copy an Actor with the bw import apify command, you pass an Apify token for that command. The token stays in the command. We receive the Actor files you upload, not the token, and we do not receive your Apify password.
The console can also connect an Apify account so you can pick Actors to import. That connection does not sign you in. If you use it, we store your Apify user id and username, and the access and refresh tokens, encrypted. Apify asks you to approve profile and full API access, which is what lets us list those Actors and read the ones you import. Disconnecting deletes the stored tokens. The basis is Article 6(1)(b): you asked us to import from that account.
Runs and storage
A run can include input, output, datasets, key-value stores, request queues, logs, schedules, and webhooks. That content can include personal data about other people. You decide what is collected. For that content you are the controller and we are the processor, under the Data Processing Addendum.
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. We do not give the developer who published the Actor your name, email, run input, or run output.
Actor source is stored so we can build and run it. Customers receive the built image, not the source. We may inspect the source for legal, compliance, or security reasons.
Developer waitlist
The form at /developer-waitlist collects:
- your email address
- your Apify username
- the IP address of the submission, and an approximate country and city when the host attaches them to the request
We use the email and username to invite you to publish and to match the Actors you already publish. Before we store the submission we look the username up on Apify’s public Actor catalog API and keep the signup only if that account has at least one public Actor. We do not receive your Apify password, token, or private account data.
The legal basis is Article 6(1)(b) GDPR: you asked to be contacted about publishing on Bytewells. The IP address, approximate location, and bot check are Article 6(1)(f): keeping the form from being filled by scripts.
Contact form
The form at /contact collects your name, email address, and message, plus the same IP address and approximate location as the waitlist. We use them to reply. The basis is Article 6(1)(b) for the reply, and Article 6(1)(f) for the connection data and bot check.
Signup attribution cookies
When you browse bytewells.com, we may set two first-party cookies, bw_ft (first touch) and bw_lt (last touch). They are kept for 90 days, use Path=/, SameSite=Lax, Secure, and HttpOnly, and help us understand how someone first found Bytewells before they create an account.
Each cookie holds a small JSON record, encoded for storage: the landing page path and any UTM parameters in it (up to 300 characters), the hostname of the referring site when your browser sends a Referer header, standard UTM campaign parameters if they appear in the URL, whether a Google or Microsoft ad click id was present in the URL (we store only yes or no, not the id itself), and a timestamp. They do not contain your name, email address, or other personal data. We do not share them with third parties and we do not use them for advertising. You can delete them in your browser at any time.
The legal basis is Article 6(1)(f) GDPR: attributing signups to how people discover Bytewells so we can improve the product and marketing we control. These cookies are disclosed here and are not gated on a separate consent banner.
Audience measurement
We use Pirsch Analytics (Emvi Software GmbH, Germany) to count visits and a few actions, such as opening the developer pages, copying the import commands, and joining the waitlist. Pirsch does not use cookies. On each request it hashes the IP address, user agent, date, and a salt into a visitor id that lasts 24 hours. The IP address is not stored. Country and city are approximate, from a local database. Events do not include names, email addresses, or Apify usernames. The basis is Article 6(1)(f): seeing which pages and developer actions matter, without an advertising profile.
Bot check
Both forms can show a Cloudflare Turnstile widget. When it is enabled, Cloudflare processes the check to decide whether the submission is automated. That processing is covered by Cloudflare’s own terms. We receive a pass or fail result, not a biometric or an advertising profile.
Who else receives the data
We do not sell personal data. Recipients include:
- Resend, which sends the contact form and waitlist mail to our operations inbox, sends account email such as address verification and password reset, and stores outreach unsubscribe status
- DigitalOcean, which hosts the site, the console, the API, the database, and object storage. Production run data and Actor source are stored in Frankfurt, Germany
- Stripe, which processes card payments and developer identity and bank checks
- Cloudflare, when Turnstile is enabled on a form
- Apify, which receives a username when we check the public Actor catalog for a waitlist signup. If you connect Apify from the console to import Actors, Apify also receives the API calls we make with that connection. A command-line import does not send us your Apify token
Page views and the events above are sent to Pirsch Analytics (Emvi Software GmbH) in Germany. Pirsch does not receive form contents.
Some of these providers process data outside the European Economic Area. Where they do, the transfer relies on the provider’s Standard Contractual Clauses or an adequacy decision.
How long we keep it
We keep a waitlist or contact submission until you ask us to delete it, and in any case no longer than 24 months after we last email you about Bytewells. Account data lasts for the life of the account. Billing, tax, and payout records last as long as tax and accounting law requires, including after the account is closed. Run and storage retention is described above. We may keep a record longer if we need it to establish, exercise, or defend a legal claim. Copies in backups remain until the backup expires.
Email opt-out
Outreach email includes an unsubscribe link. One-click unsubscribe from your mail client, or open the link in your browser. That marks your address as unsubscribed in our mail provider (Resend) so we do not send outreach again. To delete a waitlist or contact submission as well, use the contact form and ask to be removed.
Your rights
You can ask us for access, correction, deletion, restriction, or a copy of your data, and you can object to processing based on legitimate interests. Use the contact form. We may need to confirm that the request comes from you.
If you are in the European Economic Area or the United Kingdom, you can also complain to the data protection authority where you live.
Changes
If this policy changes, the effective date at the top of this page changes with it.