Privacy Policy

• Account details — your name, email address, and whether you joined as a homeowner or a business.
• Listing details (homeowners) — photos of your fence, its address and precise location, sign-space measurements, and your asking price. How you like to be paid (e.g. bank transfer) if you choose to add it.
• Business details (businesses) — your business name, description, category, regions, address, and sign library.
• Activity on the platform — approaches, offers, messages, and agreed deals (including the tax-ledger records both parties can see).
• Billing — handled by Stripe. We see your subscription status; we never see or store your card number.
• Technical basics — the session cookies that keep you signed in, and standard server logs.

This deserves its own section, because it's the most sensitive thing we hold:

• The public only ever sees an approximate location — a broad circle on the map, never a pin on your house — and blurred photos.
• Your exact address and precise location are revealed only to a business you have an agreed deal with, or one you choose to share it with during a negotiation (sharing is always your action, one business at a time, and ends if the negotiation does). Businesses' contact details are revealed to you when a deal is agreed.
• These rules are enforced in the database itself, not just in the pages you see.

• to run the service — listings, search, matching, negotiation, messaging;
• to email you about activity that concerns you (an approach, an offer, a message, an agreed deal) — these emails deliberately contain no private details, just a nudge to log in;
• to bill subscriptions and prevent abuse (e.g. rate limits, reports);
• to meet our legal obligations.

We don't sell personal information, we don't share it with advertisers, and we don't use third-party analytics or tracking.

Only what's needed, only to make the service work:

• The other party to your deal — contact and payment details are shared between homeowner and business once (and only once) a deal is agreed.
• Supabase — our database and authentication provider. Your data is hosted in Sydney, Australia (see “Where your data lives” below).
• Stripe — subscription billing.
• Resend — sends our notification emails.
• OpenFreeMap — serves the map imagery you see (built on OpenStreetMap data).
• Toitū Te Whenua LINZ — a NZ government service we use for aerial imagery and to turn addresses into map coordinates.
• Authorities, where the law requires it.

Fences data is stored with Supabase in Sydney, Australia — the closest hosting region to New Zealand. The Privacy Act 2020 lets us store information overseas where it will be subject to comparable safeguards; Australian privacy law provides protections comparable to New Zealand's, and our providers protect your information under their own privacy commitments regardless of where it sits.

We set only the cookies needed to keep you signed in (authentication/session cookies). No advertising cookies, no tracking cookies, no third-party analytics. Because these cookies are strictly necessary for the service to function, there's nothing to opt in or out of — if you'd rather not have them, the only option is not to sign in.

• Your account and listings — for as long as your account is open.
• Negotiation history and tax-ledger records — kept while your account is open, since both parties may need them (for example, for tax records).
• If you close your account, we delete or anonymise your personal information within a reasonable period, except where we must keep it (e.g. billing records).

Under the Privacy Act 2020 you can ask us for a copy of the personal information we hold about you, and ask us to correct it. Most of it you can see and edit yourself from your dashboard. For anything else, email hello@fences.nz and we'll respond within 20 working days.

If you're not happy with how we've handled your information, you can complain to the Office of the Privacy Commissioner (privacy.org.nz).

All traffic is encrypted in transit. Access rules are enforced at the database level (row-level security), so even our own application code can't hand out data it shouldn't. Precise locations, addresses, and payment preferences have additional protections on top.

If we change this policy in a way that matters, we'll flag it on the site or email you before it takes effect. Our terms of use are in the Terms & Conditions. Privacy questions: hello@fences.nz.