DeCaro Auctions

Privacy Policy

← Sign in

Privacy Policy for decaroauctions.com

Last Updated: August 10, 2026

DeCaro Real Estate Auctions, Inc. ("DeCaro Auctions," "we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you use decaroauctions.com and our Platform.

1. Information We Collect

We store data in Supabase and our databases.

2. How We Use Your Information

3. Sharing Your Information

We may share information with:

We do not sell your personal information for money. Third-party service providers are contractually obligated to protect your data and use it only for the services they provide to us.

3.1 Mobile Information

Mobile information will not be shared with third parties or affiliates for marketing/promotional purposes.

We ask for a phone number so a member of our team can call you about your deposit, your paperwork, and arrangements on the day of a sale. The Platform does not send text messages. Phone numbers are used solely for that direct contact and for operational purposes. We do not use or share mobile information for independent marketing or promotional activities by third parties.

4. Cookies and Tracking

We use cookies for core site functionality and, with your consent, two further kinds.

Analytics (PostHog). Used to understand how the site is used so we can improve it.

Listing activity, kept by us. Separately from PostHog, we keep our own record of how each auction listing is used: opening the listing, opening its photo gallery, playing a property film, downloading a due diligence document, and saving the auction date to a calendar. It is stored as one entry per listing per day with a count, so ten visits in one afternoon are a single entry saying ten. Background video that plays by itself on a listing is never counted, because nobody chose to watch it, and activity by our own team is not recorded at all.

If you are signed in, this is ordinary account activity. It is held with your account in the same way as your bids and your registrations, and it is kept whatever you answered on the cookie banner.

If you are not signed in, we keep it only if you accepted analytics. In that case we set a first party cookie holding a random identifier, so that repeat visits from the same browser count as one person rather than as a series of strangers. That identifier is not derived from anything about you, it is not shared with anyone, and it can only be read by our own servers rather than by scripts running on the page. If you declined, or have not answered the banner yet, no identifier is set and no listing activity is recorded for you.

If you later sign in, or send us an enquiry, the activity already recorded against that identifier is attached to your record, so an interest in a property you looked at before you contacted us appears alongside your enquiry. This only happens while you still accept analytics. If you have withdrawn, the identifier is not used and nothing is attached to your name.

One identifier belongs to one person. If somebody else uses the same browser and contacts us from it, their enquiry is not joined to the earlier activity, and the identifier is retired so that what each of you does from then on stays separate.

Only our own team can see this, in our customer records. It is never shown to other bidders, it is not shared with anyone outside DeCaro Auctions, and it is not used for advertising or sent to any advertising partner.

If you withdraw your consent, using the Cookie Preferences link in the site footer, we delete the identifier and the anonymous listing activity held against it. Clearing your browser cookies also stops any further activity being linked, though it leaves our copy in place, so withdraw if you want it removed. Activity that has already been attached to your name is part of your customer record and is deleted on request using the details in Section 10.

We also record how you arrived at the site, for example the search or advertisement you clicked, or the campaign printed on a mailer or sign you scanned a QR code from. This tells us which of our campaigns is working. It is our own record, held with your enquiry, and it is not shared with anyone else.

Analytics are not collected until you accept via the consent banner shown on your first visit. Declining keeps them off, and you can change or withdraw your choice at any time using the Cookie Preferences link in the site footer. We do not use advertising cookies. For more details, see our Cookie Policy section below.

5. Your Rights and Choices

6. Data Security and Retention

We implement reasonable security measures. However, no system is infallible. We retain data as long as necessary for the purposes described or as required by law.

7. International Transfers

Data may be processed in the United States. For EU users, we rely on appropriate safeguards where required.

8. Children's Privacy

The Platform is not intended for children under 18. We do not knowingly collect data from children.

9. Changes to This Policy

We may update this Privacy Policy. We will notify you of material changes and post the updated date. Your continued use constitutes acceptance.

10. Contact Us

If you have questions about this Privacy Policy, wish to exercise your rights, or need to submit a legal notice, please contact us at:

Cookie Policy

(Incorporated herein) We use essential cookies for core site functionality and, only with your consent, analytics cookies (PostHog) to understand site usage and improve the experience. Analytics stay off until you accept via the consent banner; declining keeps them off, and you can change your choice at any time via Cookie Preferences in the footer. We do not use advertising cookies. Third-party analytics cookies are subject to PostHog's policies. EU/EEA visitors are asked to consent before any analytics are collected. Accepting analytics also allows one first party cookie of our own, holding a random identifier, which lets us count repeat visits to a listing from the same browser as one person; it is described in Section 4, it is readable only by our servers, and declining leaves it unset.