Skip to content
Bullion API

Privacy Notice

Last updated:

This is what we collect, why, and what we do with it — written in plain English. Last updated 15 November 2026. Have a lawyer review the notice before relying on it for your business.

1.Scope

This Privacy Notice explains what personal data Bullion API ("we", "us") collects, why we collect it, who we share it with, and what rights you have. It applies to the website at api.bullionapi.dev and the API endpoints under that domain. It does not apply to any third-party sites linked from our pages.

2.Data we collect

We collect the minimum needed to run the service:

  • Account data: your name and email address, plus a securely hashed password when you use email/password sign-in. If you choose Google or GitHub sign-in, we receive your provider account identifier, name, email address, email-verification status and, when supplied, profile image. We do not receive your Google or GitHub password.
  • Where you found us: when you create an account, the campaign tags naming the source, medium and campaign on the link that first brought you to the site, the name of the website you came from (not the full page address), and your answer to the optional "How did you first hear about Bullion API?" question. These travel in the page address until you sign up; nothing is stored on your device. We use them only to see which channels bring sign-ups.
  • API keys: the keys you create. We store only their SHA-256 hash; the plaintext is shown to you once at creation and we cannot recover it.
  • Request logs: retained authenticated request records contain a timestamp, API key ID (not the key itself), endpoint, method, HTTP status and response time. These application request records do not contain IP addresses, user agents or response bodies. Sign-in sessions can separately contain IP addresses and user agents; Cloudflare also processes connection information to deliver and protect the service.
  • Billing data: handled by Stripe. We receive your plan, the Stripe customer ID and the subscription status back from Stripe. We do not see or store your card number.
  • Support emails: anything you send us at hello@bullionapi.dev or our privacy, security and sales addresses, stored in Gmail.
  • Preferences and service history: optional-email choices and their history, alerts, monthly API usage, sign-in connections, checkout/subscription changes, credit balances and transaction history, and email delivery statuses. Email bodies are not stored in the application delivery ledger.
  • Contact-form bot checks: when you use the contact form, Cloudflare Turnstile processes browser and client-side signals needed to distinguish automated traffic. We do not include your message or other form entries in the verification request, and we do not retain verification tokens after checking them.

We do not set tracking cookies, do not run advertising pixels, and do not sell or share personal data for marketing.

3.Portfolio data

If you use the portfolio features, we store the financial details you enter about your gold holdings:

  • Transaction records: the transaction date, quantity and weight unit, amount paid or received, delivery costs, fees, product description, and the tax treatment you declare.
  • Calculated figures: your holdings, cost basis, profit or loss, valuations, and gains worked out from those records.

We use this information only to provide the portfolio features: showing what you hold, what it cost you, what it is worth now, and any gains or losses. You can delete individual transactions at any time in the dashboard, or delete your whole account to remove everything at once. We never sell this information or use it for marketing.

4.How we use it

We use the data above to:

  • Provide, authenticate and bill the service.
  • Enforce per-plan quotas and detect abusive usage.
  • Diagnose outages and respond to support requests.
  • Comply with legal obligations and respond to lawful requests.
  • Notify you of service changes or security incidents that affect your account.
  • See which channels bring sign-ups, from where you found us.

We do not use your data to train third-party models and we do not run behavioural advertising.

5.Sub-processors

We use these service providers and recipients. Their roles vary: payment and identity providers may act as independent controllers for their own purposes. Appropriate processing and transfer terms are required where applicable; a provider's published terms alone do not establish our account-specific arrangements.

  • Cloudflare — Website/API hosting, edge security, D1 storage, operational logs, cookieless Web Analytics and contact-form bot checks through Cloudflare Turnstile. Processing location: Global network, including processing outside the UK/EEA; no UK/EEA-only residency is promised.
  • Cloudflare Workers Email Service — Transactional email delivery and delivery-status events. Processing location: Cloudflare’s global email delivery infrastructure; recipient mail providers also process delivered messages.
  • Stripe — Payments and subscription management; Stripe also acts as an independent controller for some payment, fraud and legal processing. Processing location: United States and other countries used by Stripe; no account-specific regional restriction is verified.
  • Google (Gmail) — Support correspondence and operational mailbox copies, including customer details in billing notifications. Processing location: Google’s international infrastructure, including the United States; mailbox-specific residency and retention controls are not yet verified.

Cloudflare Turnstile is used for contact-form bot checks. See Cloudflare’s Turnstile Privacy Addendum.

Twelve Data and Gold API receive service-level market symbols, currencies and time ranges, not your account data. Our password-breach check sends only the first five characters of a SHA-1 password hash to Pwned Passwords, not your password, full hash or account details. Operational incident notifications may also be delivered through Discord when configured; they must not contain customer data.

We will give at least 30 days' notice by email before adding a new sub-processor that handles customer personal data.

Optional social sign-in

If you choose to sign in with or connect Google or GitHub, your browser visits that provider and the provider learns that you are authenticating with Bullion API. These optional identity providers process information in the United States and other countries under their own privacy notices: Google Privacy Policy and GitHub Privacy Statement. We request only identity and email information for authentication, not access to your files or repositories. Email/password sign-in remains available. Matching email addresses do not automatically connect accounts; existing users connect a provider while signed in through Settings.

6.Cookies and sessions

We use a small number of strictly necessary cookies and server-set session tokens. None of them are used for tracking.

  • better-auth.session_token — signed session token set when you sign in. HTTP-only, Secure on https://.
  • Temporary authentication cookies protect social sign-in redirects. Your explicit signup preferences, and where you found us, are carried in protected OAuth state while you authenticate with a provider and are applied only when your account is first created.
  • __cf_bm (Cloudflare) — bot management for the public pages. Not on by default for authenticated dashboard traffic.

We also use Cloudflare Web Analytics to see how the website is used and how quickly pages load. It is cookieless: it does not set cookies, store anything on your device, or track you across other websites. It records aggregate figures such as page views, referring pages, browser and device type, country, and page-load performance, and we see only those totals, not individual visitors. Because it sets no cookies and does not track you, it does not need your consent.

7.Retention

We keep data only as long as we need it:

  • Account data: for as long as your account is active. Account deletion from the dashboard happens immediately and cannot be undone.
  • Sessions and security tokens: valid until expiry or revocation; a daily job removes expired stored sessions and tokens. Credential values are never included in data exports.
  • Portfolio data: kept while you use the portfolio features. Deleting a transaction removes it immediately; deleting your account removes all portfolio data immediately and cannot be undone.
  • API keys: retained while you have a key with that name. Revoking a key stops it working immediately and the row is deleted within 24 hours.
  • Request logs: deleted once they are 30 days old, by a job that runs every day. We also keep only the most recent 50 requests for each account, so older entries can be deleted sooner.
  • Preferences, consent, usage and local billing history: retained while your account is active and removed on account deletion. Account-linked financial audit events have identity and free-text links removed on deletion while their numerical history remains protected against editing.
  • Email delivery evidence: retained while your account is active for delivery and duplicate-send prevention. On account deletion we remove account links, recipient digests, provider message links and metadata, and prevent in-flight operations from restoring them. Remaining unlinked email evidence is removed by daily cleanup once it is 30 days old. Account-deletion confirmation messages have separate delivery evidence, removed by the same daily 30-day cleanup so we can confirm delivery. Address-suppression digests may be kept separately to avoid sending to bounced or complaining recipients; ask us to review a suppression record as part of a rights request.
  • Migration recovery copies: completed application migration row copies are removed by daily cleanup after 30 days. Recovery copies outside the application require separate retention controls and are not represented as erased by account deletion.
  • Stripe billing history: held by Stripe under its own legal and retention obligations. Deleting your Bullion API account does not delete Stripe's records.
  • Support emails: our target is deletion within 12 months of the last exchange, unless a documented legal need requires longer retention. Gmail enforcement is not yet verified; application cleanup does not delete mailbox messages. Contact us for deletion or access to correspondence.

Where we are required to keep data longer for legal reasons (for example, anti-money-laundering records), we retain it for the minimum period required by law.

8.Your rights

Depending on where you live, you have some or all of these rights:

  • Access — request a copy of the personal data we hold about you.
  • Correction — ask us to fix anything wrong.
  • Deletion — delete your account and the data we hold. The dashboard has a Delete account button; deletion happens immediately and cannot be undone.
  • Export — while signed in, download your application data as JSON. This includes your retained account, usage, billing, preferences and portfolio records, without passwords, keys, tokens or licensed market-price history. Downloads are limited to one per minute and must fit the supported size limits; we never silently truncate them. If an export is too large, or you need Gmail correspondence, separate status-subscription records or records held by an external provider, email privacy@bullionapi.dev for an assisted request.
  • Object or restrict — object to certain processing or ask us to pause it.
  • Withdraw consent — where our lawful basis is consent, you can withdraw it at any time without affecting prior processing.
  • Complain — to your local data protection authority.

We respond without undue delay and normally within one calendar month. Where the law permits extra time for complex or numerous requests, we explain the extension and its reasons within that first month. We may need proportionate identity confirmation before disclosing or changing personal information.

9.Legal basis (GDPR / UK GDPR / CCPA)

Under the EU GDPR and UK GDPR we rely on the following bases:

  • Contract: to provide the API you have signed up for, including authentication, billing and support.
  • Legitimate interests: to keep the service secure (request logging, abuse detection), to keep records of financial transactions and to improve the product based on aggregate usage.
  • Legal obligation: to comply with applicable law, respond to lawful requests and keep accounting records.
  • Consent: for anything optional (for example, marketing emails, if we add them later).

Under the California Consumer Privacy Act (CCPA/CPRA), we do not sell or share personal information for cross-context behavioural advertising. California residents have the same access, deletion and portability rights listed above and can exercise them through the same channels.

If you are in a jurisdiction that requires a different lawful basis for any processing described here, contact us and we will work with you to resolve it.

10.Security

We protect data with controls proportionate to the sensitivity of the information:

  • TLS everywhere — our service is HTTPS-only.
  • Email/password credentials are securely hashed through Better Auth and are never stored in plaintext. Social-only accounts do not require a Bullion API password.
  • API keys are hashed with SHA-256 before storage; the plaintext is shown once at creation.
  • Production access is gated by role, audited and limited to operational necessity.
  • We log and alert on anomalous auth patterns (impossible travel, high-volume enumeration, key sharing).

No system is perfectly secure. If you find a vulnerability, please report it to security@bullionapi.dev rather than filing a public issue.

11.International transfers

The services listed above may process data outside the UK, EEA or Switzerland. Applicable transfer safeguards can include an adequacy decision, the European Commission's Standard Contractual Clauses and the UK addendum or International Data Transfer Agreement. The applicable mechanism depends on the recipient, contract and transfer; provider documentation does not by itself verify our arrangements. Contact us for information about the safeguards applicable to your data. We do not promise UK/EEA-only storage.

12.Children

The Service is intended for adults. We do not knowingly collect personal data from anyone under 18. If you believe a child has provided us with personal data, contact privacy@bullionapi.dev and we will delete it.

13.Changes and contact

We will post material changes on this page at least 14 days before they take effect and email the address on your account. The "Last updated" date at the top reflects the current version. Earlier versions are available on request.

Any question about this notice or how we handle your data: privacy@bullionapi.dev. Security disclosures: security@bullionapi.dev.

Back to top