Who is responsible
Hillbase operates the service. For privacy questions or requests, contact privacy@hillbase.com.
What we collect and why
- Account e-mail: to send sign-in codes and links, identify your account and communicate about billing or the service.
- Sign-in session: the
hb_sessioncookie keeps you signed in. It is HttpOnly, so browser scripts cannot read it, and is used only for sign-in. - API keys: to authorize access. We store keys hashed; the full key is shown when it is created.
- Usage records: per key and day, including operation, credits, response status and region where applicable, to enforce plan allowances, show usage and operate the service.
- IP addresses: used transiently for rate limiting and abuse prevention.
- Batch inputs and results: to process your requested batch and let you retrieve its results; kept for 7 days.
- Signals webhook URLs: to deliver updates you request. Treat credentials embedded in a webhook URL as sensitive.
- OAuth connected apps: app identity, permissions and authorization records to grant, show and revoke app access.
Service providers and storage
Our service data is stored in Canada, in the Vancouver area, except for processing by our service providers. Cloudflare provides hosting and CDN services, Resend sends sign-in e-mail, and Stripe processes payments and subscriptions. These providers may process information outside Canada under their own privacy policies.
We send each provider the information needed for its role, such as your e-mail for sign-in delivery and billing information for payment processing. Stripe collects payment details directly; Hillbase never sees your full card number. We may disclose information where legally required.
Public-record information
Hillbase provides data from public publishers. Personal information in publisher records is filtered at output: personal contact details are removed and private individual name fields are not returned. If you find personal information in an answer or believe a record is incorrect, contact privacy@hillbase.com with the response or record reference. Do not send more personal information than is needed to identify the issue.
Retention and deletion
Batch inputs and results expire after 7 days. Sign-in sessions expire after 30 days of inactivity or are revoked when you sign out. We keep account, key, usage, webhook and connected-app records while needed to provide the service, manage billing and prevent abuse. We do not promise a fixed deletion period for records required for legal, accounting or security purposes.
Account deletion replaces your account e-mail, removes outstanding sign-in challenges and revokes your sessions and API keys. Some associated operational, usage and billing records may remain where required for those purposes. Contact us to request deletion of other personal information. Provider records and backup copies may remain according to their retention obligations.
Your privacy rights
Under the applicable Canadian privacy laws, including PIPEDA and British Columbia’s PIPA, you can request access to your personal information and correction of inaccuracies, subject to the exceptions in those laws. You can request deletion through account deletion or by e-mailing privacy@hillbase.com. We will explain any information we must retain and may ask you to verify your identity before acting on a request.
You can revoke API keys and connected apps from your account. Learn more about privacy rights in British Columbia and accessing personal information under Canadian privacy law.
No sale or advertising trackers
We do not sell personal information and do not use advertising trackers. The sign-in cookie supports account access. We use account and usage information to provide and protect the service, not to build advertising profiles.
Changes and contact
We will publish updates here with a new last-updated date and notify you of material changes through the website or account e-mail. Contact privacy@hillbase.com for questions, access, correction, deletion or privacy concerns.