Privacy Policy
What Blockhash keeps about you, why, who else handles it and for how long.
This page is a draft for review. It is not in force yet and may change before it is.
- Status
- Draft, not in force
- Company
- Blockhash LLC
- Organized in
- Texas
- Contact
1. What this policy covers
This policy is from Blockhash LLC, a Texas limited liability company. In it “Blockhash”, “we” and “us” mean Blockhash LLC.
It covers this website, the dashboard, and the service: the RPC endpoint and the Data API for Robinhood Chain.
It says what the service keeps today. When that changes, this page changes, as section 11 says.
Some things the service does not do by itself, such as closing an account. Where a person at Blockhash does one of them by hand, this policy says so.
It does not cover other sites that this one links to, Mancer among them.
It does not cover what is on the chain. Addresses and transactions on a public blockchain are public, and we did not put them there.
2. What we collect and why
We collect what the service needs to sign you in, to approve accounts, to count your use, to charge you and to keep accounts safe.
We do not sell it, rent it or trade it, and we do not “share” it as U.S. state privacy laws use that word.
We do not use it for advertising.
| What | Why | How it is kept |
|---|---|---|
| Your email address | To sign you in, and to write to you about your account, your charges and these documents. | As you typed it, trimmed and in lower case. An address typed at sign-up is kept from then on, whether or not it is ever confirmed. |
| Your password | To sign you in. | As a salted scrypt hash only. The password itself is never stored and never logged. |
| Your identity at GitHub or Google, if you sign in with one | To know you the next time you sign in there. | The provider’s id for you. For a new account, the email address the provider has verified, as the account’s address. Nothing else the provider sends is kept: no name, no picture and no token of the provider’s. |
| What you are building, if you tell us | So that the person who approves accounts knows what an account is for. | As you typed it, trimmed. You can change it in the dashboard while your account waits for approval. When an account joins the waitlist and its address is confirmed, the service sends us one email with the address and what you said. |
| Whether your account is approved | So that only an approved account can make a key or add a card. | The time it was approved. Each approval that a person at Blockhash makes is also recorded: the account or the address that was approved, and when. An approval made in the dashboard also records who made it. |
| Your email address, if we approved it before you signed up | So that the account you make with it does not wait for approval. | The address, a note that a person at Blockhash wrote with it, and when it was added. The record of that approval names the address. |
| Your sessions | To keep you signed in. | A cookie in your browser. We keep only a hash of it, with when it was made and when it ends. |
| The places you sign in from | To let you in while somebody guesses at your password from elsewhere. | A keyed hash of each place’s network address, never the address, with when you were last seen there. The newest 20. |
| The network address and email address of a sign-in attempt | To hold back sign-ups, password guesses and emails that come too fast. | In the service’s memory only, for at most 1 hour. Never written to the database or to the service’s log. |
| Your API keys | To know which account a request belongs to. | A hash of each key, with the name you gave it, when it was made and when it was revoked. A key itself is never stored. |
| Your use | To hold a plan to its limits, to show you your use, and to charge for it. | Counts for each key, UTC day and method: the calls answered and the compute units they cost. Counts of refused requests for each key, day and reason. |
| Billing, on Pay as you go | To charge your card and to account for it. | Stripe’s id for you as its customer, for your card, and for each page you opened to add a card. The card’s brand, last four digits and expiry, never its number. An email address for invoices, if you set one. Your limit and your alert. What you owe, your credits and the promo codes you used. Each charge, and each invoice and credit note as a PDF, with the address it was mailed to. |
| The links we email you | So that a link to confirm your address, to reset your password or to confirm a sign-in works once. | A hash of the link’s token, until the link is used or runs out. A sign-up’s link also holds the hash of the password given at sign-up and what you said you are building, and a link that confirms a sign-in holds the provider’s id for you. |
| What you write to us | To answer you. | In our mailbox. |
Signing in with GitHub or Google. When you sign in with GitHub, the service asks GitHub for permission to read your profile there and your email addresses. When you sign in with Google, it asks Google for your profile and your email address. So what each of them sends holds more than we keep, your name and your picture among it.
The service reads two things from what is sent: the provider’s id for you, and an email address that the provider has verified. It stores the id. It stores the address only when the sign-in makes a new account, as that account’s address. It stores nothing else, and it keeps no token of the provider’s: the one it is given is used for that sign-in alone.
The emails we send. The service sends these by itself:
- a link to confirm your address, or to confirm that a sign-in with GitHub or Google is yours;
- a link to reset your password, which is also sent when somebody signs up with an address that already has an account;
- word that your account is approved, if it waited for approval;
- each invoice and each credit note, as a PDF;
- a notice that a charge failed, that your account is suspended, that your month’s spend reached your alert, or that it reached your limit.
A person at Blockhash writes the others:
- the notices that the Terms of Service and this policy promise: of a change to either that matters, of a higher price or a call that costs more units, of the end of the service or of your account, and of a suspension for breaking the terms;
- word that your data was reached by someone who should not reach it, as section 8 says;
- answers to what you write to us.
We send no other email, and no marketing email.
3. What we do not keep
- The content of your requests, with one exception. The service does not store or log the calls you send, their parameters or the answers. It keeps counts alone: for each key, day and method, the calls it answered and the units they cost, and for each key, day and reason, the calls it refused. The exception is the index’s database, which logs the statements the service runs to answer a Data API call: section 4.2 says what they hold and for how long.
- Your key, your password, your session’s cookie or the links we email you, as they are. The service keeps only hashes of them, and its log is written so that none of them can appear in it.
- Your card’s number or its security code. You type them on Stripe’s own page. They go to Stripe and never reach us.
- Your name, postal address, phone number or any government identifier. We do not ask you for them, and we keep no name that GitHub or Google sends when you sign in: an account is an email address and, if you gave one, a line on what you are building. What Stripe asks for on its own page goes to Stripe, and what Stripe prints on an invoice is in the copy of it that we keep.
- How you browse this site. Its pages load no analytics, no advertising and nothing from another site, and they connect only to this site and to our own service. The site behaves the same whether or not your browser sends a Do Not Track signal.
4. What is logged
This section says what our own logs hold of the requests you send to the endpoint, and for how long.
We read these logs to find the cause of a fault or of an overload. We do not use them to profile anyone.
4.1 The node’s web server
Calls to the chain are answered by a node, behind a web server that we run. Today the RPC endpoint’s name is answered by that web server.
It writes one line for each request it receives: the network address the request came from, the time, how long it took, its status and size, the headers sent with it, without the Referer header, and the name of whoever the key was issued to.
The key itself is not written. At that server a key is the first part of a request’s path, and the whole path is replaced before the line is written. So a line says whose key was used, and never the key.
The request’s body, which holds your calls, and the answer are never written.
A call that the service passes on to the node is the service’s own request there. Its line holds our service’s network address and our service’s name, not yours.
The log is kept in files of 100 MB. When a file is full a new one begins, and only the newest 3 full files are kept. No number of days is set: how long a line stays depends on how fast the files fill.
4.2 The index’s database
Data API calls are answered from an index of the chain, in a database that we run.
The database logs each statement that the service runs to answer such a call, with the values the call named, such as the address asked about.
That log does not hold your key, your account or your network address. It is kept 7 days.
The database also writes log files of its own, kept as 5 files of 200 MB. A statement that failed can appear in them.
4.3 The service’s own log
The service that checks keys and counts use has a log of its own. It holds faults, and no line of it is made from a request, a key or a network address.
5. Cookies and browser storage
The service sets cookies only to sign you in. Each is set by api.blockhash.xyz and sent to that name alone, only over HTTPS, and no script on a page can read it.
This site also keeps two small values in your browser’s own storage.
| Name | What it is for | How long |
|---|---|---|
__Host-bh_session | Keeps you signed in to the dashboard. | 30 days, or until you sign out |
__Host-bh_signup | Marks the browser you signed up in, so the link we email to confirm your address works there without your password. | 24 hours |
__Host-bh_link | Marks the browser you signed in with GitHub or Google in, while you confirm by email that the sign-in is yours. | 1 hour |
__Host-bh_state_github__Host-bh_state_google | Carries a sign-in to GitHub or Google and back. | 10 minutes |
blockhash-theme | Browser storage, not a cookie. Remembers the light or the dark theme, if you choose one. It is never sent to us. | Until you clear it |
blockhash-signed-in | Browser storage, not a cookie. Remembers that this browser was signed in, so the dashboard draws the right outline while it loads. It is never sent to us. | Until you sign out |
Our own code sets no other cookie: no analytics cookie and no advertising cookie.
Cloudflare, whose network is in front of api.blockhash.xyz, and Vercel, which hosts this site, can set cookies of their own on those names. Our code neither sets nor reads such a cookie, and it cannot tell us whether one is set for you.
Stripe’s payment page and the sign-in pages of GitHub and Google are their own sites, and set cookies of their own.
6. Who else handles your data
These companies handle data for us. The table says what each one does, and what of yours it handles.
| Who | What it does for us | What it handles |
|---|---|---|
| Stripe | Takes card payments and makes invoices. | Your card’s details, which you type on Stripe’s own page. Your email address and our number for your account. Your charges, invoices and credit notes. |
| Resend | Sends the emails the service sends by itself. | Your email address, and what each email says, with the invoice or credit note attached where there is one. |
| Cloudflare | Runs the network in front of api. | What your browser sends the dashboard’s service and what it answers, as it passes through. Backups, encrypted before they leave our server. |
| Backblaze | Stores the other copy of our backups. | Backups, encrypted before they leave our server. |
| Latitude. | Rents us the servers that the service, its database and the node run on. | Everything the service keeps is on those servers. |
| Vercel | Hosts this website. | Your requests for its pages. |
| GitHub | Signs you in, if you choose it. | It learns that you sign in to Blockhash. It lets our service read your profile there and your email addresses. We keep its id for you and, for a new account, one verified address. |
| Signs you in, if you choose it. Holds our mailbox. | It learns that you sign in to Blockhash. It sends our service your profile and your email address. We keep its id for you and, for a new account, the address. The emails you write to us, and the ones a person here writes to you, are in its mail service. So is the email the service sends us when an account joins the waitlist. |
The servers the service runs on are in the United States. Cloudflare’s network, which is in front of the dashboard’s service, and Vercel’s, which serves this site, run around the world. Wherever you use the service from, your data is handled in those places.
We give your data to nobody else, with two exceptions.
- We disclose what a law or a court’s order requires us to.
- If Blockhash or the service passes to another company, the accounts pass with it, under this policy until that company tells you of a change.
7. How long things are kept
How long a thing is kept depends on what it is. Section 9 says what closing an account deletes.
| What | How long |
|---|---|
| Your account: its email address, its password’s hash and its sign-ins | Until the account is closed, which a person at Blockhash does on your request. |
| An email address typed at sign-up and never confirmed | It stays, as an account that awaits confirmation and has no password, session or key, until a person at Blockhash deletes it on request. The link we emailed is deleted when it runs out, after 24 hours, and with it the hash of the password and what you said you are building, as they were typed at that sign-up. |
| What you said you are building | Until you change it, or until the account is closed. The email in which the service told us of it stays in our mailbox until a person at Blockhash deletes it, and it is deleted when you ask. |
| When your account was approved, and the record of each approval | With no fixed end. |
| An email address that we approved before its holder signed up, with its note | Until a person at Blockhash takes it off the list of approved addresses. It stays on that list after you sign up with it. The record that it was approved, and that it was taken off, names the address and has no fixed end. |
| Your sessions | 30 days from the sign-in, or until you sign out or reset your password. An account keeps its newest 20. |
| The links we email you | Until the link is used. Otherwise 24 hours for a link that confirms an address, and 1 hour for a reset or a sign-in to be confirmed. |
| The places you sign in from | 90 days after you were last seen there. A password reset forgets all of them but the one it was made from. |
| The counts that hold back sign-in attempts | At most 1 hour, in the service’s memory. |
| Your keys | Until the account is closed. A revoked key’s hash and name stay until then, so that its past use keeps its name. |
| Your use | With no fixed end. The dashboard shows the last 90 days. |
| Stripe’s id for you as its customer | From the first time you open the page to add a card, with no fixed end. It stays when you leave Pay as you go, and it is kept with the record of your charges. |
| Stripe’s id for your card, and the card’s brand, last four digits and expiry | Until you replace the card, or until you leave Pay as you go: the card is then detached at Stripe and forgotten here. |
| The email address invoices are mailed to, if you set one | Until you change it or clear it in the dashboard. Each invoice and credit note keeps the address it was mailed to. |
| Invoices, credit notes and the record of charges and credits | While the account is open, and after it is closed for as long as we must be able to account for payments. |
| What Stripe tells the service (each event’s id and kind), and Stripe’s id of each page you opened to add a card | 30 days. |
| The log of the node’s web server | Until its files are replaced, as section 4.1 says. No number of days is set. |
| The logs of the index’s database | Its log of statements 7 days. Its own log files until they are replaced, as section 4.2 says. |
| Backups | Hourly copies 8 days, daily copies 35 days, monthly copies 400 days. A copy cannot be deleted in its first 7 days. A plain copy stays on our server for 72 hours. |
| The emails you write to us | In our mailbox, with no fixed end. |
A backup is a copy of the whole database, encrypted before it leaves our server. So something deleted from the database stays in backups until the last backup that holds it is deleted: at most 400 days.
Stripe keeps its own record of your payments and invoices, under its own policy.
8. How it is protected
- Passwords are kept as salted scrypt hashes. Keys and sessions are kept as hashes. A copy of the database signs nobody in and gives nobody a key.
- The site, the dashboard’s service and the endpoint are reached over HTTPS.
- Backups are encrypted before they leave our server, with a key that is kept in neither backup store.
- The service’s log is written so that no key, password, cookie, email address or URL can appear in it.
No system is safe from every attack, and we cannot promise that your data will never be reached by someone who should not reach it. If we learn that it was, a person at Blockhash will tell you by email, at the address on your account.
9. Your choices
In the dashboard you can revoke a key, reset your password and sign out. While your account waits for approval you can change what you said you are building. On Pay as you go you can also replace your card, set where invoices are sent, and leave the plan, after which your card is removed.
The service does nothing else of this kind by itself. For the rest, write to developers@blockhash.xyz from your account’s address, and a person at Blockhash does it by hand, within 30 days of your request. You can ask us:
- for a copy of what we keep about you;
- to correct your email address;
- to close your account and delete what we keep about you;
- to delete an email address of yours that was typed at sign-up and never confirmed;
- to delete an email address of yours that we approved before you signed up.
When an account is closed, its keys stop working and we delete what identifies you in it: its email address, what you said you are building, its password’s hash, its sign-ins, its sessions and the places it signed in from. An account on Pay as you go leaves that plan first, as section 5.7 of the Terms of Service says, so it is closed once the month has turned and its last charge is paid, even where that is later.
The email in which the service told us what you are building is not in the account. It stays in our mailbox until a person at Blockhash deletes it, and it is deleted when you ask.
Four things cannot be deleted on request:
- invoices, credit notes and the record of charges and credits, which we keep for as long as we must be able to account for payments;
- counts of use, which are kept once they are no longer tied to a person;
- copies in backups, which stay until each backup runs out, as section 7 says;
- lines in the logs of section 4, which stay until those logs are replaced.
Where a privacy law gives you other rights over your data, such as to take it elsewhere or to object to a use of it, write to the same address. We will honor them for the data we hold.
None of this reaches what is on the chain. A transaction on a public blockchain is there for good, and nobody can change or delete it.
You can clear this site’s cookies and storage in your browser at any time. Clearing the session’s cookie signs you out.
10. Children
The service is for developers. It is not meant for children, and an account may be made only by someone who is at least 18 years old.
We do not knowingly keep data about a child. If you believe a child has made an account, write to us and we will close it.
11. Changes to this policy
When what we keep or who handles it changes, this page changes.
Before a change that matters takes effect, we email the address on every account at least 30 days ahead. A change matters if we begin to keep a new kind of data about you, or to use what we keep for a new purpose.
Other changes take effect when they are posted here.