Account and data deletion
In productSelf-service permanent deletion at /account/subscription (DELETE /api/v1/user/account). Removes local application data, API keys, and Supabase auth identity.
Enterprise trust
Security reviewers, legal teams, and MSP partners use this hub for subprocessors, retention, operational controls, and our published Data Processing Agreement. Huntertech ingests public vendor status data; we do not require access to your infrastructure.
Subprocessors
5
In-product controls
6
Retention categories
5
Published DPA
Yes
Document sections
Standard DPA
Published for review
Procurement
Subprocessors listed
5
Controls in product
6
Retention categories
5
Published DPA
Yes
Quick links
Standard DPA
Published processor agreement for procurement and legal review.
OpenPrivacy Policy
How we collect, use, and delete personal data across the service.
OpenAPI & alert delivery
Rate limits, webhooks, PagerDuty, Slack, and enterprise procurement notes.
OpenMSP evaluation pack
Use cases and trust materials for managed service provider rollouts.
OpenData scope
Huntertech monitors publicly published vendor status. We process account and API metadata you configure, but never require access to your cloud tenants, endpoints, or internal systems.
What we process
What we do not require
Vendor intelligence is sourced from publicly published status pages and feeds
Jump to section
What Huntertech processes, what we do not touch, and where to find related legal documents.
Vendor intelligence content is sourced from publicly published vendor status pages, RSS feeds, and similar public channels. See our Privacy Policy and Data Processing Agreement for role definitions and contractual terms.
Who Huntertech is in contractual terms, and what to tell enterprise counsel during vendor review.
Jonathan R. Hunter, an individual doing business as Huntertech.io
Huntertech.io is operated by Jonathan R. Hunter, an individual doing business as Huntertech.io. In our agreements and policies, references to "Huntertech.io," "Huntertech," "we", "us", or "our", or similar terms mean the Service Provider, unless the context requires otherwise.
The Service Provider is currently a sole proprietor and is not yet incorporated as a corporation or LLC. We plan to form a U.S. business entity and will offer enterprise customers a reasonable opportunity to assign or novate agreements to that entity when it is formed.
For vendor security questionnaires and enterprise procurement: Huntertech is operated today by a solo founder (Jonathan R. Hunter, d/b/a Huntertech.io), not a registered corporation. Subprocessors, security controls, and the published DPA reflect current operations. We disclose this status proactively and document our plan to migrate contracts when a formal entity is formed.
Countersigned DPAs use a signature block for Jonathan R. Hunter, d/b/a Huntertech.io. See Section 16 of the Data Processing Agreement.
Maps each trust commitment to what is available in the product, through support, or under an executed enterprise agreement.
6
60% of controls
1
10% of controls
3
30% of controls
Self-service permanent deletion at /account/subscription (DELETE /api/v1/user/account). Removes local application data, API keys, and Supabase auth identity.
Handled through in-app support channels per our Privacy Policy. Identity verification may be required before processing.
Current subprocessors are listed on this page and referenced in our standard Data Processing Agreement.
Create, rename, and revoke API keys from account settings. Keys are stored hashed; usage is tracked for quota enforcement.
Configure in-app, email, webhooks, Slack, PagerDuty, and personal feed channels from account notification settings.
Google Analytics loads only after cookie consent. See our Cookie Policy.
Jonathan R. Hunter, an individual d/b/a Huntertech.io, is identified as the Service Provider in our Terms, DPA, and Privacy Policy. Solo-founder / not-yet-incorporated status is disclosed for procurement.
Our standard DPA is published at /legal/data-processing-agreement. Countersigned copies and custom security exhibits are provided through enterprise sales.
The subprocessors list on this page is updated when providers change. Enterprise customers with an executed DPA receive notice per that agreement.
Handled under the executed DPA and Privacy Policy, not through an automated in-product workflow.
| Control | Status | How it works |
|---|---|---|
| Account and data deletion | In product | Self-service permanent deletion at /account/subscription (DELETE /api/v1/user/account). Removes local application data, API keys, and Supabase auth identity. |
| Privacy rights requests (access, correction, deletion) | Support-assisted | Handled through in-app support channels per our Privacy Policy. Identity verification may be required before processing. |
| Subprocessor disclosure | In product | Current subprocessors are listed on this page and referenced in our standard Data Processing Agreement. |
| API key lifecycle | In product | Create, rename, and revoke API keys from account settings. Keys are stored hashed; usage is tracked for quota enforcement. |
| Notification delivery preferences | In product | Configure in-app, email, webhooks, Slack, PagerDuty, and personal feed channels from account notification settings. |
| Cookie consent for analytics | In product | Google Analytics loads only after cookie consent. See our Cookie Policy. |
| Legal contracting party disclosure | In product | Jonathan R. Hunter, an individual d/b/a Huntertech.io, is identified as the Service Provider in our Terms, DPA, and Privacy Policy. Solo-founder / not-yet-incorporated status is disclosed for procurement. |
| Countersigned Data Processing Agreement | Enterprise agreement | Our standard DPA is published at /legal/data-processing-agreement. Countersigned copies and custom security exhibits are provided through enterprise sales. |
| Subprocessor change notifications | Enterprise agreement | The subprocessors list on this page is updated when providers change. Enterprise customers with an executed DPA receive notice per that agreement. |
| Formal breach notification to enterprise customers | Enterprise agreement | Handled under the executed DPA and Privacy Policy, not through an automated in-product workflow. |
Third parties that process personal data to operate Huntertech.io.
5 subprocessors disclosed. Full terms in our published DPA.
| Provider | Purpose | Data processed | Region |
|---|---|---|---|
| Supabase | Authentication, account identity, and managed Postgres for application data | Account email, profile metadata, auth session tokens, application records you create | United States (configurable project region) |
| Stripe | Subscription billing and payment processing | Billing contact, payment method metadata, invoice and subscription status | United States |
| Cloudflare | CDN, DDoS protection, and edge delivery for the public site and API | IP address, request metadata, security and performance logs | Global edge network |
| Mailjet (Sinch Email) | Transactional email for account and notification delivery | Recipient email address, message content for opted-in notifications | United States / EU (provider regions) |
| Google Analytics | Aggregated website usage measurement when cookies are accepted | Pseudonymous usage events (only with consent) | United States |
Full processor terms: Data Processing Agreement.
How long categories of data are kept and when they are removed.
Retained while your account is active. Removed when you delete your account from Subscription settings (self-service) or after a verified deletion request via support. Billing records may be retained where required by law.
Public vendor incidents, maintenance, advisories, and updates are ingested from vendor-published sources. Historical depth follows your plan data window (7 days to unlimited, depending on tier).
Aggregated hourly request counts per API key and route group for quota enforcement and support. Removed when your account is deleted; not tied to individual HTTP bodies.
Notification inbox items are retained while your account is active and removed with account deletion. Email engagement signals may update deliverability preferences.
Enterprise demo requests and support tickets are retained to respond and for operational history unless you request deletion and no legal hold applies.
Our standard processor agreement for enterprise customers and MSP partners.
The DPA is a full published agreement covering processor obligations, subprocessors, security measures, breach notification, data subject assistance, and deletion at termination.
Countersigned DPAs, custom security exhibits, and vendor questionnaires.
Need a countersigned DPA, custom security exhibit, or vendor security questionnaire? Request an Enterprise demo and reference the standard DPA.
Request an Enterprise demo for countersigned agreements, custom security exhibits, or vendor questionnaires.