Skip to content
The Club Pricing Hardware Our Story
verde
Club Login Book a demo

Last updated September 13, 2026

Privacy policy

Verde holds two different kinds of information, and the rules are different for each. This page separates them rather than blurring them together.

On this page

  • 1. Two different roles
  • 2. Who this page is for
  • 3. What we collect about you
  • 4. What your club collects
  • 5. Where it comes from
  • 6. Why we use it
  • 7. Cookies and measurement
  • 8. Card payments
  • 9. Who else touches it
  • 10. Junior members and children
  • 11. How long we keep it
  • 12. Your rights
  • 13. If you are a club member
  • 14. How it is protected
  • 15. Where it is stored
  • 16. Changes to this policy
  • 17. Contact

1. Two different roles

Almost every confusing privacy policy in software comes from mixing up two things. Verde is trying not to.

For our own visitors, we decide. When you browse imverde.com, book a demo or email us, Verde decides what to collect and why. In privacy law that makes us the controller, and this page is the full account of it.

For a club's members, the club decides. When a club runs its tee sheet, its register and its member list on Verde, that member data belongs to the club. The club decides what to collect, who sees it and how long it is kept. Verde processes it under the club's instructions and does nothing else with it. In privacy law that makes us a processor, or a service provider under California's rules.

The practical version. If you are a club member and you want to know what is held about you, or want it corrected or deleted, your club is the right place to ask. Section 13 explains what we do when a request comes to us instead.

2. Who this page is for

This policy covers imverde.com, the Verde service, the Verde member app and the club websites we host. It is written for three groups: people looking at Verde for their club, staff who sign in to run one, and members of clubs that use Verde.

Verde is operated by Verde Technologies LLC in Omaha, Nebraska.

3. What we collect about you

This section is about information where Verde is the one deciding — visitors to this site, clubs evaluating us, and staff accounts on the service.

Category What that means
Contact details Name, club, role, email and phone number, from a demo request, the contact form or an email to us.
Account details The email address a staff account signs in with, the permissions the club has given it, and a hashed password. We never see the password itself.
Billing details The plan a club is on, its billing contact and its invoice history. Card details for a subscription go directly to our payment processor, not to us.
Support correspondence Messages you send us and our replies, so the next person you talk to already knows the history.
Technical records IP address, browser and device type, pages requested, and error and security logs. Ordinary server records, kept short.

We do not ask for and do not want anything sensitive here — no health information, no government ID numbers, no background data of any kind.

4. What your club collects

This is the club's data, held on Verde. Typically it is member names and contact details, membership type and tier, bookings and check-ins, league and event entries, scores, purchases at the register, member account balances, and whatever the club types into a note field.

We do not decide what goes in there. We do not mine it, sell it, or use it to market to a club's members. We look at it when a club asks us to help with something and when we have to in order to keep the service running and secure.

We may use aggregated, de-identified figures — how many bookings the platform handled in a month, how often a feature is used — that do not identify a club, a member or any individual.

A note about note fields. Booking notes and member notes are free text, which means staff can type anything into them. Do not put card numbers, Social Security numbers or medical information there. The acceptable use section of the terms says the same thing, and it is the single easiest privacy mistake for a club to make.

5. Where it comes from

  • From you — a form on this site, an email, or what you type into Verde at the club.
  • From your club — if you are a member, your club created your record, usually from its existing roster.
  • Automatically — server and security logs generated when a browser or a Verde device makes a request.
  • From our processors — for example, the payment processor tells us a payment succeeded, and which card brand and last four digits were used.

We do not buy contact lists, and we do not enrich what you give us with data bought from brokers.

6. Why we use it

  • To run the service your club pays for
  • To answer you when you contact us, and to follow up on a demo
  • To bill, and to keep the records tax law requires
  • To keep the platform secure — detecting abuse, investigating incidents, and rate limiting
  • To find and fix problems, and to understand which parts of Verde are used so we know what to improve
  • To meet a legal obligation when one applies

We do not sell personal information, and we do not share it for cross-context behavioral advertising. Those two phrases have specific meanings under California law and we mean them in that sense. There is no advertising network on this site and none inside Verde.

7. Cookies, and what we measure on this site

Verde uses cookies for two things inside the service: keeping you signed in, and remembering settings like which club you are working in. Those are necessary for it to work at all.

What we measure on imverde.com

This marketing site is measured in detail, and this section says so plainly rather than describing it as "analytics" and leaving you to guess. On imverde.com — not inside the service, and not on a club's own site — we record:

  • pages viewed, page titles, how long each page was actually read, and how far down it was scrolled
  • where clicks landed on the page, and clusters of repeated clicking on something that does not respond
  • sampled cursor positions, several times a second, used to build a heat map of where attention goes
  • which form fields were used and which were abandoned — never what was typed into them
  • the page or search that sent you here, and any campaign tags on the link you followed
  • browser, operating system, device type, screen and window size, language, and time zone
  • approximate location — country, region and city — worked out from the network, never from device location
  • page load speed, and errors the page ran into

Why a marketing site is measured this closely. Verde is built by a very small team with no research budget. Knowing that people reach the pricing page and stop halfway down it, or click something that is not a button, is how the site gets fixed. There is no advertising network involved and nothing is sold.

What is never collected

  • Anything typed into a field. Not email addresses, not messages, not passwords. The collector cannot read field contents at all.
  • Your keystrokes.
  • Your IP address. It is turned into a one-way hash on arrival, used only to spot automated traffic, and cannot be turned back into an address.
  • Anything that follows you off this site. There are no third-party advertising or retargeting trackers on imverde.com. The measurement is ours, stays on our servers, and stops at the edge of this site.
  • Your name or anything that identifies you. A visit is tied to a random string your browser generates, nothing more.

How to turn it off

We honor Global Privacy Control. If your browser sends the GPC signal, the visit is still counted but no cursor track is recorded or stored. Several browsers and extensions send it, and in a number of US states it is a legal instruction rather than a request. We treat it as one.

Blocking JavaScript for imverde.com stops all of it. The site is readable without it — only the support answer library needs it to load.

Inside the service

None of the above happens inside Verde itself. We do not build heat maps of your staff at the counter, and we do not record cursor movement on the tee sheet. What we keep there is the operational record described in section 4 and the error logs in section 3.

Your browser can block or clear cookies. Blocking the necessary ones will stop sign-in from working.

8. Card payments

Verde never stores a full card number. Not on our servers, not in a database, not in a log. When a card is tapped, dipped or entered, the card data goes from the Verde device or the browser to our payment processor directly.

What comes back to us, and what we keep, is the part you would see on a receipt: the card brand, the last four digits, an expiry month, the amount, and a token that lets the club refund the sale later. That token cannot be used to charge a card anywhere else.

Payments are processed by Stripe, which is responsible for its own handling of card data under its terms and privacy notice.

9. Who else touches it

Verde is built on other people's infrastructure, which is the honest thing to say rather than implying it all lives in a building we own. Each of these is bound to use the data only to provide its service to us.

Who What for
Stripe Card processing, payouts and payment records
Supabase Database and authentication
Vercel Hosting and content delivery
Resend Transactional email — receipts, confirmations, resets

We will also disclose information where the law requires it, and if Verde is ever acquired, to the acquirer — in which case this policy travels with the data and clubs are told before anything changes.

If this list changes in a way that affects club data, we will update this page and tell account administrators.

10. Junior members and children

Golf clubs have junior programs, and this is the part of a privacy policy most club software ignores.

Verde is sold to clubs, not to children, and the member app is not directed at children under 13. A club should not create a member app sign-in for a child under 13 without a parent's consent. Record a junior under the parent's membership instead, which is how most clubs already run it.

If we learn that a member app account belongs to a child under 13 and was created without parental consent, we will tell the club and remove the account and its personal information.

A junior's name appearing on a roster, a tee time or a leaderboard entered by club staff is the club's record to keep and its decision to make.

11. How long we keep it

What How long
Club data on the service For as long as the club's account is open, then thirty days after it closes for export, then deleted
Demo and contact enquiries Two years from the last time we heard from you, unless you ask us to remove it sooner
Billing and tax records Seven years, because we are required to keep them
Server and security logs Ninety days, unless one is part of an open investigation
Backups Deleted data disappears from backups as those backups age out, within thirty-five days

12. Your rights

Depending on where you live, you may have the right to ask for a copy of the personal information we hold about you, to have it corrected, to have it deleted, to receive it in a portable format, and to appeal if we say no.

We will not treat you differently for asking. There is no worse service, no different price, and no penalty of any kind for exercising a privacy right.

Email the contact form and say what you want. We answer within forty-five days and usually much sooner. We may need to confirm who you are before we hand over a copy of anything, which is a protection for you rather than an obstacle.

13. If you are a club member

Your relationship is with your club. It decided to collect your information, it decides what is kept, and it is the fastest route to getting something changed or removed.

If you contact us instead, we will not quietly ignore you and we will not act on our own either. We will pass the request to your club, tell you we have done it, and help the club carry it out. Acting unilaterally on a club's member record is exactly the thing a processor should not do.

14. How it is protected

Encryption in transit and at rest, access limited to the people who need it, and each club's data separated from every other club's at the database level.

The security page covers this properly, including how to report a vulnerability.

No system is perfectly secure. If there is ever a breach that affects a club's data, we will tell the club promptly and directly, with what we know and what we are doing about it, rather than burying it in a status page.

15. Where it is stored

Verde is a US company serving US clubs, and club data is stored in the United States. Some of the services in section 9 operate globally and may process limited data — logs, routing, content delivery — outside the US as part of running their own networks.

16. Changes to this policy

When this page changes, the date at the top changes with it. For a material change affecting club data we tell account administrators by email before it takes effect.

We will not quietly broaden what we do with club data and count on nobody re-reading the page.

17. Contact

Privacy questions go to a person, not a queue.

Verde Technologies LLC

the contact form
Omaha, NE

See also the terms of service and the security page.

verde
Omaha, NE
Pages
  • The Club
  • Pricing
  • Hardware
  • Apps
  • Our Story
  • Team
  • Careers
  • Contact
  • Support
  • Status
Legal
  • Terms
  • Privacy
  • Security
© 2026 Verde Technologies LLC. All rights reserved. Built in Omaha, NE