Legal & Policy Updates

29 September 2026

Paying members are now asked to complete their account in two steps: confirm the business behind the workspace (legal and trading name, ABN, contact, phone, address), then verify the owner by scanning a code with HAMANI Connect, the HAMANI product that performs the identity check. Free workspaces are not asked. Privacy now states exactly what is kept from that check — the outcome, date, method label, HAMANI Connect’s reference and an opaque identifier — and that documents, document numbers and dates of birth are never received or stored. A verified paying workspace is no longer subject to the free-tier sending caps.

24 September 2026

Sign-in change: “Continue with Google” was removed. HAMANI no longer routes any customer identity through Google — the remaining ways in are email + password, a 6-digit emailed code, a passkey, “Continue with Microsoft” (Entra), and enterprise SSO where your business federates its own provider. Existing accounts are unaffected: your workspace, data and email address are unchanged, and if you previously signed in with Google, use “Forgot password?” once to set a password. Google Gemini was also removed as an AI provider option. Privacy and Security were updated to match, and the Data Processing Agreement’s data-residency clause was corrected: it named Google Cloud australia-southeast1, which stopped being true when the store moved to Cloudflare D1.

7 July 2026

Account security: new workspaces now confirm their email through a single-use verification link (valid 24 hours) before the first sign-in, and a self-serve password reset was added (single-use link, valid 1 hour). Privacy and Security describe both flows: only a one-way hash of each token is stored, a newer link replaces the older one, and token records are erased with your account. These are account service emails, not marketing.

6 July 2026

Sign-in changes: added “Continue with Microsoft” (Entra, single-tenant) and passkeys (WebAuthn — Face ID, Touch ID, Windows Hello, Android biometrics) alongside email + password and Google. Removed the emailed sign-in link. Privacy and Security note what Microsoft sign-in receives (email and name, which we do not store) and that a passkey’s biometric never leaves your device — its public key, a usage counter and the name you give it are stored, and erased with your account.

4 July 2026

Added Google sign-in and a single-use emailed sign-in link as passwordless options alongside email+password. Privacy and Security note what Google sign-in receives (email, and — via its standard profile scope — a name/photo we receive but do not store) and the sign-in link's 20-minute, single-use expiry.

4 July 2026

Enterprise readiness: added enterprise Terms clauses (SSO federating into HAMANI as system of record, team-seat licensing, SLA/DPA incorporation), a DRAFT Data Processing Agreement and DRAFT Service Level Agreement for review, a Trust Centre answering the security questionnaire from real controls (SOC 2 shown as not held), and privacy/security updates for SSO and verifiable data export/deletion.

4 July 2026

Added agency terms (client sub-accounts, flow-down consent responsibility, per-client vs master wallet billing, white-label limits) and matching privacy disclosures for agency-managed sub-accounts.

20 June 2026

Initial publication of the Privacy Policy, Terms of Service, Acceptable Use Policy and AI Disclosure for HAMANI Marketing.