Trust
Security and trust
Blackbird asks for the documents you would not hand to a stranger. This page says what happens to them — and separates what you can verify yourself from what you have to take our word for.
Updated
In short
- Your records live in India. The database, sign-in and file storage run in Supabase’s Mumbai region.
- Every row is scoped to one account by row-level security in the database, not only by the application asking nicely.
- We never hold a readable copy of a secret. Passwords, API keys and tokens are stored only as one-way hashes.
- The claims about the browser are checkable. The commands are at the foot of this page; run them against the live site.
- No independent security audit has been done. No penetration test, no SOC 2, no ISO 27001. That is stated here rather than left to be assumed.
Where your records are kept
The database, authentication and file storage are Supabase, in its Mumbai region. The application is hosted on Vercel; its pages are served from a global network, but the records themselves are not copied there.
Payments for Blackbird plans go through Razorpay, and card and bank details stay with Razorpay — they never reach Blackbird. The full list of everyone who processes anything is below, generated from the same register the privacy notice uses.
Who can read it
Row-level security, in the database. Every table carrying your records is restricted by policy to the account that owns them. That restriction is enforced by Postgres, not by the application remembering to add a filter — a query that forgets the filter returns nothing rather than someone else’s invoices.
Service-role-only tables. A few tables — API keys, OAuth clients, codes and tokens, background job cursors — have row-level security switched on and no policies at all. Nothing holding a user session can read them under any circumstances; only the server’s own service role can, and it does so in code paths that check the account first.
Delegated access is explicit and revocable. Where a CA or colleague can see a business, that access is a record you create and can end; ending it ends their ability to download that client’s originals too.
Blackbird staff. Support access to a live account is not a self-service switch, and we are not going to pretend there is a hardware-token-and-two-approvers ceremony behind it either. If you want a written answer about staff access before trusting the product with a year of records, ask and you will get a straight one.
Signing in
Two-factor sign-in with an authenticator app is available on every account. When you have it on, a password alone gets you to a lower assurance level and no further: every private page and every private API route waits for the six-digit code.
That rule is also written into the database as a restrictive policy, so a request that somehow reached Postgres without the second factor is refused there as well. Two independent refusals, not one.
Passwords are never stored. What is kept is a one-way hash, and a sign-in compares hashes.
API keys, and connecting an assistant
API keys are shown once. What is stored is the SHA-256 hash of the key and nothing else — there is no readable copy to leak, and no way for us to tell you what your key was. Verification compares hashes in constant time, so the comparison cannot be used to guess a key one character at a time.
Connecting Claude or ChatGPT uses OAuth 2.1, with PKCE required and only the S256 challenge method accepted. Access is scoped: the reading tools cannot write, and the one tool that writes a record is separate and asks for a different scope. Refresh tokens rotate, and re-use of a retired token revokes the whole family rather than quietly issuing another.
Every connection can be revoked from your account, and revoking it stops the assistant immediately rather than at the end of a token lifetime.
What those tools can do, and what they refuse to do, is written out on the developer page.
Your documents and certificates
Originals — bills, bank statements, FIRCs and FIRAs — are kept in a private bucket, never a public URL. Each one is stored under a path keyed to the account and the business it belongs to, and its SHA-256 hash is recorded when it is saved.
On download, three things are checked before any bytes are returned: that the document is linked to a business you can currently see, that the stored path belongs to that business’s owner, and that the file still hashes to what was recorded. A file that no longer matches its hash is refused with an explanation rather than handed over quietly.
What each export contains, and what it does not, is set out in data exports and service continuity.
In the browser
The public claims on this page are the ones you can check without an account. Every response from the site carries:
| Header | What it does |
|---|---|
Strict-Transport-Security | Two years, subdomains included. After one visit a browser refuses plain HTTP to this domain. The header also carries preload, but the domain has not been submitted to the browser preload list, so a browser that has never been here is not yet covered |
Content-Security-Policy | Scripts, styles, images, connections and frames limited to a named list |
X-Frame-Options: DENY | The site cannot be framed, so it cannot be used for clickjacking |
X-Content-Type-Options: nosniff | A file is treated as the type it says it is |
Referrer-Policy | strict-origin-when-cross-origin: a page address is not leaked to another site |
Permissions-Policy | Camera, microphone, geolocation and interest-cohort tracking switched off |
Private pages and API responses add Cache-Control: private, no-store, so nothing personal is kept by a shared cache.
curl -sI https://www.blackbirdfinance.net/ \
| grep -iE 'strict-transport|content-security|x-frame|nosniff|referrer-policy|permissions-policy'Who else processes your data
Generated from the same register the privacy notice and the data processing agreement read, so the three cannot drift apart.
| Who | What they do | Where |
|---|---|---|
| Optional journal AI service (identified before upload) | Extracts and suggests journal drafts from only the description and files you choose to submit; available only when Blackbird enables it | The service and its terms are shown before you submit a file |
| Supabase | Database, sign-in and file storage | India |
| Vercel | Hosting the app | India; pages served from a global network |
| Razorpay | Taking payment for Blackbird plans; card and bank details stay with Razorpay | India |
| WhatsApp Business Platform (Meta) | Delivering the payment reminders a customer sends their clients | Outside India |
| Sandbox (sandbox.co.in), a GST Suvidha Provider | Reaching the GST system when a customer files through Blackbird | India |
Services you connect yourself — Binance, PayPal, your bank’s exports, a Google or Microsoft sign-in — are not our processors. Data moves between you and them at your direction.
Keeping it, and deleting it
| What | How long |
|---|---|
| A grievance or data request is answered within | 90 days |
| A personal-data breach is reported to the Data Protection Board within | 72 hours of becoming aware |
| As your processor, we tell you within | 24 hours, so your own 72 hours are not spent waiting on us |
| Processing logs are kept for at least | 365 days |
| After an account closes, you have | 30 days to export before erasure |
Each data set has its own retention, set out in full in the privacy notice and summarised here:
| Records | Whose decision | Kept for |
|---|---|---|
| Your journals and ledger | Yours; we process it for you | Posted entries and audit records remain while your account exists. Raw journal AI uploads are not stored by Blackbird; the configured provider’s retention terms apply to submitted content. |
| Your account | Ours to answer for | While your account exists. Sign-in logs are kept for at least a year, as the DPDP Rules require, then erased. |
| Your business profile | Ours to answer for | While your account exists. |
| Your plan and payments to us | Ours to answer for | For as long as tax law requires us to keep accounts (up to 8 years), then erased. |
| Your privacy records | Ours to answer for | While your account exists. |
| Your clients | Yours; we process it for you | Until you delete it, or your account closes. |
| Your invoices and income | Yours; we process it for you | Until you delete it, or your account closes. Tax law may require you to keep invoices for years; that is your choice to make. |
| Your vendors and expenses | Yours; we process it for you | Until you delete it, or your account closes. |
| Your bank lines and payouts | Yours; we process it for you | Until you delete it, or your account closes. |
| Your GST and export filings | Yours; we process it for you | Until you delete it, or your account closes. A GST session ends when it expires. |
| Your crypto trades and the people you trade with | Yours; we process it for you | Kept as a permanent record of each trade while your account exists; erased when it closes. |
| Your WhatsApp payment reminders | Yours; we process it for you | Until you delete it, or your account closes. |
| Your connected accounts | Yours; we process it for you | Until you disconnect, or your account closes. |
| Your audit trail | Yours; we process it for you | While your account exists; at least a year in any case, as the DPDP Rules require of logs. |
| Your settings and catalogue | Yours; we process it for you | Until you delete it, or your account closes. |
What has not been done
A trust page that lists only what exists is read as claiming everything else by omission. These are the things Blackbird does not have, stated plainly so nobody has to guess:
- No independent penetration test, and therefore no summary to publish. If one is commissioned, the summary goes here.
- No SOC 2 report and no ISO 27001 certificate. Neither has been sought.
- No bug bounty programme. Reports are still wanted — write to the address below and you will get an answer from a person.
- Not on the HSTS preload list. The header asks for it; the submission has not been made, so a browser’s very first request to this domain is not yet protected by it.
- No tested shutdown migration or standby service. A backup policy is not a promise that the app stays reachable; data exports and service continuity says what to keep independently.
- No independent review of the tax calculations by a practising chartered accountant. The methodology is published in full so it can be checked, and the page says the same thing about its own review status.
Found something wrong? Write to support@blackbirdfinance.net. A security report gets a reply from a person, not a ticket number, and we would rather hear it from you than read it somewhere else.
Read further
- Blackbird privacy notice — the full register, by data set
- Blackbird data processing agreement
- Data exports and service continuity
- Tax calculation methodology — how every figure is worked out
- Digital Personal Data Protection Act, 2023
This page, the privacy notice, the data processing agreement and the Privacy tab in your settings are all generated from one register in the code. If two of them ever disagree, that is a bug — tell us.
Questions people ask
- Is my data stored in India?
- Yes. The database, sign-in and file storage run in Supabase’s Mumbai region, and payments go through Razorpay in India. The one processor outside India is the WhatsApp Business Platform, and only for payment reminders a customer chooses to send their own clients.
- Can Blackbird staff read my invoices?
- Technically, a service role exists that is not limited by row-level security — that is how background jobs and support work at all, and any product that says otherwise is describing something it does not have. What we will not do is dress that up. If you want it in writing before trusting us with a year of records, ask and you will get a straight answer.
- What happens if I lose my API key?
- You create a new one and revoke the old one. We cannot tell you what the old key was: only its SHA-256 hash is stored, which is the point.
- Has Blackbird had a security audit?
- No. There has been no independent penetration test, no SOC 2 and no ISO 27001. It is said here rather than left to be assumed, and if that is a blocker for you it is a reasonable one.
- How do I check the claims on this page?
- The browser ones take ten seconds — the curl command is in the section above. The rest are in the privacy notice, the data processing agreement and the data-continuity page, all generated from the same register as this page.
- How do I report a vulnerability?
- Write to support@blackbirdfinance.net with enough detail to reproduce it. There is no bounty programme, and you will still get a reply from a person.
- What happens to my records if I close my account?
- You have 30 days to export everything before erasure. What each export contains is listed on the data exports page.
Read next
- How Blackbird calculates your taxEvery rate and assumption, and what it refuses to decide
- Data exports and service continuityWhat you can take out, and what to keep independently
- Privacy noticeThe full register, data set by data set
- Blackbird comparedAgainst ClearTax, Zoho Books, Refrens, a CA and a spreadsheet