Pritty Ghood Privacy Policy

Version: 1.2

Effective date: 26 September 2026

What changed in 1.2: we now keep our own record of visits to the site, so we can see how it is being used: the pages opened, how long each was on screen, the approximate location, the kind of device and browser, and the site the visit came from. We do not store your IP address for this and we set no cookie. Section 9 says so.

What changed in 1.1: a host business can now authorise other people, such as their staff, to act for them. That means we hold an email address a host has given us for somebody who may not have an account yet, that a host business is now several people rather than one, and that an advertiser's booking may be seen and answered by any of them. Sections 1, 5, 6 and 8 say so.

Who we are. Pritty Ghood Advertising Limited, trading as Pritty Ghood, NZBN 9429049579437, registered office 34 Edgewater Parade, Waiuku, Auckland 2123. We are the agency responsible for the personal information described here under the Privacy Act 2020.

Contact. Privacy questions, access requests and correction requests go to Info@prittyghood.com.

This policy sits alongside the Platform Terms. Where the two overlap, this policy governs how we handle personal information.

---

1. What we collect, and why

We only collect what we need to run the marketplace. Information Privacy Principle 1 requires a lawful purpose connected to our function, so each item below is listed with the reason it exists.

Everyone with an account

Hosts

Advertisers

Staff of a host business

A host can authorise other people to act for them, so somebody can answer a booking request while the owner is away. Two things about that are worth setting out plainly.

We are given your email address before you have an account. To invite you, a host types your email address into the Platform, and we send you an invitation. That is personal information about you collected from somebody else rather than from you, which Information Privacy Principle 2 allows where collecting it directly is not reasonably practicable, and it plainly is not: we have no way to reach you until somebody tells us how. We use it to send that one invitation and for nothing else. We do not add you to any mailing list, and if you ignore the invitation it expires and is deleted. The invitation link itself is stored only as a one-way hash, so nobody reading our database can use it.

What you can see. Working for a host means you can see that host's bookings and the advertisers who made them, and, if the host has given you those permissions, their messages and their earnings. You cannot see their bank details, and no permission a host can give makes those visible.

When a host removes you, your access ends immediately. Your own account is not affected and stays yours. The record of what you did while you were there stays on the bookings you did it on, because it is part of the history of somebody else's contract and is not ours to erase.

Signwriters

Business details, portfolio images and pricing, so advertisers can find you.

2. Campaign QR codes

Every campaign gets a QR code. When somebody scans it we record the time, a broad device category (mobile, tablet or desktop) and the referring page, so we can tell the advertiser how their campaign performed.

We do not store the IP address of a person who scans a code. We combine the IP address, browser user agent and referrer into a one way hash and store only that hash. It lets us tell a repeat scan from a new one without keeping anything that identifies the person scanning. We cannot reverse it.

3. Photographs of advertisements in place

Hosts photograph the advertisement in position as proof it was displayed. These photographs are stored privately and are visible only to the host who took them, the advertiser on that booking, and us.

Hosts should photograph the advertisement, not the people near it. Where a photograph does capture an identifiable person, that is personal information and we handle it accordingly.

We do not carry out facial recognition or any other biometric processing on these photographs, and we do not permit anyone else to. This is a standing commitment, consistent with the Biometric Processing Privacy Code 2025.

4. Payments

Payments are processed by Stripe. Card numbers are entered directly with Stripe and never reach our systems. We store a reference to the payment, the amounts, and the country the card was issued in, which we need because an overseas card costs more to process and changes the price we quote you.

Hosts who take payment complete an onboarding process with Stripe, which collects identity and bank details directly. That information is held by Stripe under its own terms, not by us.

5. Who we share it with

We are not in the business of selling personal information, and we do not.

• Between a host and an advertiser, we share what a booking requires: the advertiser's artwork and business identity go to the host, and the host's business and location go to the advertiser.
• Within a host business. A host is not necessarily one person. Where a host has authorised staff, those people can see the bookings made with that host and the advertisers who made them, to the extent the host has allowed. If you are an advertiser, the practical effect is that "the host" who sees your booking and your artwork may be any of the people that business has authorised, in the same way that writing to a company is not writing to one named employee.
• Service providers who run parts of the platform for us: Supabase (database, authentication and file storage), Vercel (hosting), Stripe (payments), Resend (email delivery), and OpenStreetMap Nominatim (turning a host address into map coordinates). They act on our instructions.
• Where the law requires it, or to establish or defend a legal claim.

Some of these providers store or process information outside New Zealand. Before we send personal information overseas we satisfy ourselves that it will be protected by comparable safeguards, as Information Privacy Principle 12 requires.

6. How long we keep it

• Terms acceptance records: 7 years. These prove the existence and content of a contract, and 7 years covers the limitation period for a contract claim under the Limitation Act 2010.
• Booking, payment and donation records: 7 years, which is the period the Tax Administration Act 1994 requires business records to be kept.
• Artwork and display proof photographs: for the campaign and 12 months afterwards, so a dispute about whether an advertisement ran can be resolved.
• Account information: while your account is open, and then only what the records above require us to keep.
• Unaccepted staff invitations: deleted. An invitation expires 14 days after it is sent and the record is removed 30 days after that. An email address given to us for an invitation nobody used is not something we keep.
• Which person accepted, declined or cancelled a booking: for as long as we keep the booking record, because it is part of that booking's history.

7. Your rights

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 if it is wrong. Email Info@prittyghood.com. We will respond within 20 working days.

You can update most of your own information from your account at any time.

You can ask us to delete your account. We will do that, except for the records in section 6 that we are required to keep. We will tell you what we are keeping and why rather than quietly retaining it.

If you are not happy with how we have handled your information, you can complain to us first, and then to the Office of the Privacy Commissioner at privacy.org.nz.

8. Security, and what happens if something goes wrong

Access to personal information is restricted to the account it belongs to and to the people on the other side of a booking who need it. Artwork, display proof photographs and payment credentials are held in private storage that is not publicly reachable. Database access is controlled row by row, so one account cannot read another's data.

Where a host has authorised staff, the same row by row control decides what each of them can reach, from the permissions their host gave them. It is not a matter of what a screen chooses to show: a staff member without permission to see a host's earnings cannot read them by any route. Bank and payout details are not reachable by anybody but the account holder.

Decisions made in a host's name record which person made them, so a host can always tell who accepted, declined or cancelled a booking on their behalf. That record is shown to the host, and to us, and is not shown to the advertiser.

If we suffer a privacy breach that is likely to cause serious harm, we will notify the Office of the Privacy Commissioner and the people affected, as sections 112 to 117 of the Privacy Act 2020 require.

9. Cookies and site analytics

We use cookies that are necessary to keep you signed in and to keep the site secure. We do not use advertising or cross site tracking cookies.

We keep our own record of how the site is used so we can see what people look at and what they struggle to find. For each visit we record the pages opened and how long each was on screen, your approximate location as read from your network address (at best the city, never the address itself), the kind of device, operating system and browser, your screen size and language, and the site or link the visit came from. We do not store your IP address for this. To tell one visit from the next, your browser keeps two random numbers in its own storage; they are not derived from anything about you and identify no one, and clearing your browser's site data removes them. If you are signed in, the visit is joined to your account so we can see how hosts and advertisers use the site differently. Only the operator of the site can see this record. It is kept for thirteen months and then deleted.

10. Changes to this policy

If we change this policy we will publish the new version here with a new version number and effective date. If a change materially affects how we handle your information we will tell you before it takes effect.