Hasti
Hasti Privacy Notice
Last updated: 30 September 2026
What this notice covers
This notice explains how Hasti handles information you submit through the enquiry form at hasti.com.au. It applies to the name, business, email address, phone number and enquiry notes you provide, together with the time of submission and limited campaign information used to understand where the enquiry came from.
How we use your enquiry
We use these details to receive, review and respond to your enquiry about Hasti's speed-to-lead service. By selecting Send enquiry, you permit Hasti to contact you about that enquiry using the details you provide. We may call or text you, or use your email address or other supplied contact details, to respond to the same enquiry.
The optional promotional checkbox controls whether we may send future news, offers and updates by SMS and email. Leaving it unchecked does not block service follow-up about your enquiry, and an enquiry submission alone does not grant marketing permission. A separate, independent ad-measurement checkbox controls reporting this enquiry to Meta; it does not subscribe you to promotional messages. Both choices are optional and unchecked by default.
AI receptionist demo calls
If you request a demo call, we use your name and phone number to place that service call and record its request and outcome for follow-up. The AI receptionist may ask about your business, lead volume, current process, service interests and how to contact you. When a conversation is available, its full transcript and verified answers are held privately for internal review and service follow-up, not placed in website analytics or a public visitor feed. A brief summary of the outcome and verified details may be sent by WhatsApp to our internal lead team; the full transcript is not sent in that notification. An unanswered call is recorded as an outcome without invented conversation details. Requesting a demo does not grant marketing permission or create a CRM lead by itself.
We retain a complete private demo transcript for up to 30 days and the demo request and contact record for up to 90 days, unless a shorter period is required by a valid request or a longer period is required by law. Access is limited to authorised staff and service systems. You can ask us about your demo-call record using the contact details below.
Website source information
To understand how people find Hasti, we capture limited campaign tags or, when those are absent, a referring website hostname. We do not retain the referring page’s path or query string for this purpose. This source information is stored in this browser tab’s session storage and can be reused for up to 30 minutes when you navigate the site. It can be attached to an enquiry you submit. Expired source information is cleared or replaced on the next source check; session storage is normally cleared when the tab closes. A saved, unresolved enquiry keeps the source information captured when that enquiry was created so retries remain consistent. Referring-site information does not prove that an AI service recommended Hasti.
Website analytics
We use the PostHog browser SDK to count visits to the Hasti landing page, clicks on enquiry and checkout buttons, and enquiries started and successfully received. We also use Meta Pixel to record landing-page visits for campaign measurement. After the checkout endpoint returns an OK response containing a valid Stripe Checkout URL, Hasti's browser code records a Meta Pixel InitiateCheckout event. The code does not record InitiateCheckout on a button click or for a failed or unconfigured checkout. It does not send the checkout URL or personal information to Meta. For new enquiries, the independent ad-measurement checkbox—not promotional permission—controls Lead reporting after successful receipt. Browser Lead events contain no form fields or contact details. With measurement permission, our CRM and Core service can also report a server-side Lead through Meta's Conversions API, using ad-click identifiers and hashed email or phone details for matching. The browser and server use the same event identifier to avoid counting the enquiry twice. Hashed contact details are used only for this measurement, not sent as raw contact fields; business information, notes and demo transcripts are not included. Do Not Track and Global Privacy Control disable this new enquiry measurement choice. Saved pending enquiries keep their original permissions for consistent retries; this change does not replay past enquiries. PostHog uses a session-scoped identifier in this browser tab’s session storage. Hasti also keeps campaign attribution there for up to 30 minutes. Meta Pixel may use cookies or similar browser identifiers in accordance with Meta’s privacy terms.
Captured events do not include your name, business, email, phone number, enquiry notes or form choices. We remove the landing page’s query string from the browser address before loading either analytics SDK, after retaining only the bounded campaign attribution described above. Session replay is enabled to help us understand page usability: every form input is masked before replay data leaves the browser, and requests to Hasti’s /api/ endpoints are excluded from the replay network timeline. We do not enable automatic event capture, call identify, or create PostHog person profiles. PostHog processes events and replay data in its US Cloud service; Meta processes Pixel events under its own privacy terms. Meta Pixel may receive the browser-provided referring page as part of its standard event transport. Both providers receive connection information needed to process requests. We respect the browser’s Do Not Track and Global Privacy Control signals by loading neither analytics SDK when either is enabled.
For private operations reporting, Hasti also counts successful landing-page loads and daily unique browsers on our own server. A first-party cookie holds a random identifier that expires at the next Manila midnight; the private visit store retains only a one-way daily digest and daily totals, not the identifier itself, your IP address, page query, form details or Meta IDs. We remove daily digests within 30 days and anonymous daily totals after 13 months. This counter is separate from PostHog and Meta and does not send its records to them. Browsers with Do Not Track or Global Privacy Control enabled are excluded from this counter, and blocked or cleared cookies can make unique-browser counts approximate.
CRM and service providers
We store enquiry records in our customer relationship management system (CRM) so our team can follow up, keep an accurate history and manage the service. We use infrastructure and service providers to host the website, store and secure the records, deliver calls or text messages, and maintain the CRM.
Where configured for internal operations, messaging providers such as Twilio and WhatsApp may receive relevant enquiry details to notify Hasti staff that a new enquiry was received. Those internal notifications are not marketing messages to you. Providers process information only for the services they supply to Hasti and under their own privacy terms.
Retention and security
We retain an enquiry while it is needed to respond, provide or administer the service, meet legal and accounting obligations, resolve disputes, and maintain an auditable CRM history. We then delete or de-identify it under our retention procedures unless a longer period is required by law.
We use access controls, encrypted connections and protected storage appropriate to the information we handle. No internet transmission or storage system is completely risk-free, so please do not include passwords or other sensitive information in the enquiry notes.
Your contact choices
You can withdraw marketing permission, ask us to stop contacting you, or request access or correction of your enquiry by contacting [email protected]. You can still ask us to respond about the enquiry by email.
If you receive an SMS from Hasti and do not want further SMS messages, reply STOP (or use the unsubscribe instructions in the message). A STOP or unsubscribe request overrides any marketing permission, including a checkbox selection, and suppresses future marketing contact. Withdrawing consent does not affect processing that already occurred lawfully.
Questions and complaints
For privacy questions, requests or complaints, contact [email protected]. We will review the request and respond within a reasonable period. You may also contact the privacy regulator in your jurisdiction if you are not satisfied with our response.