Privacy notice

How we handle your information.

This notice explains what personal information HunchGo collects through this website and how we use it.

Last updated: 19 October 2026

What we collect

When you contact us, we collect the information you choose to share, such as your name, work email, company, role and details about your workflow. This website does not use advertising cookies or tracking pixels.

The contact form sends your enquiry to hello@hunchgo.com through our configured email provider and sends an acknowledgement to the email address you supply. Your enquiry is retained in our mailbox for follow-up. When our team changes your enquiry’s stage in the CRM, we also send a relevant update to your contact email and notify the responsible team members. To prevent duplicate submissions and limit abuse, the application also keeps a request identifier, keyed hashes of the submission, connection address and email address, timestamps and delivery flags. These metadata records do not contain your enquiry text and are eligible for removal after 24 hours, on the next accepted contact submission.

How we use it

  • To reply to your enquiry and discuss possible work together.
  • To prepare proposals and manage any engagement you agree to.
  • To meet our legal and accounting obligations.

We do not sell your information, and we do not use it to send marketing unless you ask us to.

Support Reply Agent beta

When you prepare or revise a reply, your enquiry, supplied policy and (for revisions) edited draft and revision request are sent through our server to OpenAI. Remove personal, confidential and payment information before submitting. The agent does not access your customer systems or send replies.

Our application does not save enquiry, policy or draft content in its database or application logs. The workspace keeps content in page memory while you use it; Clear workspace removes it from the page. Hosting providers may maintain access and security logs under their own retention settings.

We request that OpenAI not store generated responses for later retrieval. This is not a promise of zero retention: OpenAI may retain content in abuse-monitoring logs, normally for up to 30 days, subject to its applicable settings and exceptions. See OpenAI’s API data controls.

To limit public usage, we temporarily store request identifiers, timestamps and a keyed hash of the connection’s IP address. Entries are eligible for deletion after 24 hours and are removed on the next accepted generation request. If you submit feedback, we attach only your chosen rating to that request; we do not attach your enquiry or draft. The beta does not set tracking cookies or save drafts in browser storage.

Workflow Lab

The Workflow Lab uses fictional scenarios and evaluates rules in your browser. It does not send lab configurations or scores to our server or an AI provider. If you choose Remember scores on this browser, we save only mission scores and attempt counts in local browser storage. Clear progress removes those saved scores. You can use the lab without saving progress; scores are then kept only for the current page session.

HunchGo Learn

Learning accounts are separate from staff CRM accounts. We save your name, email, a salted password hash, verification status, package access and expiring session records. We also save your selected workflow and architecture settings, component types/positions/connections, revisioned design drafts, assessment results, scores, attempt timestamps and lesson versions so you can resume across devices. Learning exercises use fictional cases and do not send practice content to an AI provider.

HunchGo Studio saves private project descriptions, chat, job status, successful source versions and built previews in your learner account. To generate or edit an app, the backend sends your request, recent project chat, source files and any relevant build error to our configured AI provider. A separate isolated build service compiles source, and a separate preview origin serves successful sample apps using short-lived access links. Do not submit secrets, confidential information or real customer data. Generated apps use sample data; their in-app state resets on reload. Studio projects, source and chat remain saved so you can return later. To request deletion, contact hello@hunchgo.com.

The MCP Playground saves a private fictional CRM workspace, practice drafts and tasks, proposed actions and decisions, up to 50 recent execution events, and completed practice milestones in your learner account. Protocol traces remain in the current browser tab’s memory. Playground practice is not sent to an AI provider or external business app. Reset fictional workspace clears these sandbox records; it does not clear your learning or payment history. Use fictional details only.

Account verification and password-reset emails use our SMTP provider. Verification uses a six-digit code that expires after 10 minutes, works once and allows five attempts. Reset links work once. Codes and tokens are stored only as keyed hashes with expiry and use information, and usable codes and links are hidden in admin email previews. Temporary rate-limit records contain keyed hashes of connection or account identifiers. Learner sessions use essential HttpOnly cookies; learner passwords and assessment content are not stored in browser local storage.

If you choose to purchase access, Razorpay processes checkout and payment information. We store provider order/payment references, amount, currency, purchase/access dates and payment state. We do not receive or store card numbers. The checkout script loads when you start checkout. Payment references and purchase records are retained for account support and business record-keeping; Razorpay has its own data handling policies. A verified full refund removes the associated purchase’s access grant. Partial refunds are recorded and retain access pending company review.

Authorised CRM administrators can review learner accounts, grant or remove manual access, and suspend sign-in. Account and package changes are audited. Your learning and payment records persist until reviewed under our retention obligations; they are not removed by the public demo’s Clear progress button. To request access, correction or deletion of learner information, contact hello@hunchgo.com. Backups and provider records are separate.

Client data in projects

Data that clients share with us during a project is handled under the agreement for that project, including agreed rules on access, storage and retention.

Who we share it with

We share information only with service providers who help us run our business, such as email and hosting providers, and only as needed. We may disclose information where the law requires it.

Our team workspace

When you submit the contact form, we save your contact details, workflow description, preferred timing and enquiry reference in our private team CRM before attempting email delivery. Authorised team members may also record enquiry details you share by email or in a conversation. HunchGo team members use these records to assign an owner, track progress, set follow-up dates and record conversation notes. Email failures do not remove a saved enquiry. CRM records and team notes are separate from the short-lived sending metadata described above.

Our CRM also keeps copies of automated contact-form emails, lead status updates and team account welcome emails, their recipients, subjects, sending times and sending outcomes so administrators can review correspondence and investigate failures. These copies are accessible only to authorised administrators and are retained with the related enquiry. Team welcome emails are retained separately as account correspondence and contain no passwords. We do not add email tracking pixels or record whether you opened an email. A mail server accepting a message does not establish inbox delivery.

Team members sign in with individual accounts. We store password hashes, expiring session records and temporary sign-in attempt counters to protect access. We also retain a minimal account-security audit of password changes, admin resets and member deletions (actor, target email, action and time), without plaintext passwords. Administrator-requested password resets send a single-use link to the team member’s email. Reset tokens are retained only as keyed hashes with expiry and use information; usable links are hidden in saved email previews. Removing a team account revokes access while retaining related enquiry, correspondence and activity records. Session cookies are essential to the private workspace and are not used for advertising. CRM enquiry records remain for as long as needed to handle the conversation and any resulting engagement; deletion requests can be sent to hello@hunchgo.com. Mailbox copies and backups have their own retention.

How long we keep it

We keep enquiry details for as long as needed to respond and follow up, and project records for as long as our agreements and legal obligations require.

Your choices

You can ask to see, correct or delete the personal information we hold about you, or withdraw consent for its use, subject to applicable data protection law. Write to hello@hunchgo.com and we will respond promptly.

Changes to this notice

We may update this notice from time to time. The date at the top shows when it last changed.