Bindy by Makr

Security

Business records, customer enquiries and connected accounts need careful handling. These are the controls used by the current workspace.

Updated 12 September 2026

Hosting and data location

The production web application is hosted on Vercel and served over HTTPS. Bindy uses Supabase for authentication, its primary database and file storage. The current primary database region is Tokyo, Japan. Other providers may process data internationally.

We do not claim Australian-only storage or processing. See service providers for the services involved.

Workspace access

Protected workspace routes require an authenticated session. Workspace membership and role checks govern access to business records and actions. Database policies provide additional controls for customer data; privileged server operations must also check the requesting user’s authority.

Private file access requires the relevant permissions. A file intended for publication, such as an approved website image, is different from a private source or review file.

Credentials and account connections

The Supabase service-role key and provider secrets belong in server configuration. They are not public browser settings. Authentication is managed by Supabase rather than storing readable passwords in business records.

Makr and Bindy share owner workspace switching, with signed, short-lived handoffs and replay protection. Each workspace retains its own session; signing out of one does not sign you out of the other.

Social account authorisation uses the shared Makr scheduling service. It is currently in private setup; no customer social publishing is active through that service.

Approvals and operational limits

Growth automation and outbound delivery are disabled in the current release while provider setup is completed. Approval records and account scope checks remain necessary when those features are enabled.

Public intake uses URL checks and request limits. These controls reduce abuse; they do not make an uploaded document, website or AI output inherently trustworthy. Health checks distinguish service configuration from verified availability.

Reporting a security issue

Email mickey@makr.ac with the affected address, a description and safe reproduction steps. Please avoid including passwords, tokens or other people’s private data. Do not access or alter someone else’s records to demonstrate a problem.

Security review and incident handling are operated by the current owner. This page is not a claim of independent security certification, a guaranteed response time or uninterrupted availability.

Operator

Bindy is a product of Makr, currently operated by Mickey as an individual. A Singapore company is planned but has not yet been incorporated. For account, privacy or service enquiries, contact mickey@makr.ac.