Privacy Policy

MON3Y, a sole proprietorship owned by Danny Meza in California, builds and runs marketing and software for service businesses. This policy covers mon3y.io and what happens when you apply to work with us or book a call through this site. It does not cover two neighbouring things. The MON3Y platform, at contractoros.mon3y.io, is our product for businesses that already work with us, and it carries its own privacy policy. A contractor whose own website we built has their own policy on their own domain, and that one is theirs rather than ours. Write to us at MON3Y, 750 Otay Lakes Rd #2017, Chula Vista, CA 91910, or email danny@mon3y.io.

The application on this site asks for nine things: your business name, your trade, the city or area you work in, your mobile number, your email address, your website if you have one, roughly what the business does in a year, roughly what you spend on marketing a month, and what made you click the ad. We use all of it for one purpose, which is deciding whether we can help you and being ready for the call you book. The revenue and marketing-spend answers are bands rather than exact figures because a band is all we need. The last answer, what made you click, is read to write better ads. We do not sell any of it. We do not pass it to other contractors, and nothing on this site adds you to a list you did not ask to be on.

We advertise on Facebook and Instagram, and we measure whether those ads work. Two things do that measurement, and both send information to Meta. The Meta Pixel is a piece of Meta's code that runs on the public pages of this site: the home page, the application pages (/apply, /roofers, /remodelers, /pool-builders), the confirmation page after you book, this privacy policy and the terms. It runs nowhere else. It records that a page was viewed, that an application was started and submitted, and that a call was booked, and it sets two cookies of its own, named _fbp and _fbc. On the same pages we set one cookie of our own, named m3y_vid: a random identifier for your browser, so that a visit and a later application can be recognised as the same person. Meta's Conversions API is the same measurement sent from our server rather than from your browser, so that it still works if your browser blocks the pixel. When you view one of those pages or start the application, we send Meta the same page view from our server, carrying your IP address, your browser's user agent, the two Meta cookies above and m3y_vid, and nothing you typed. When you submit the application or book a call, we send Meta an event that carries your email address, your mobile number, your name, your city, your state and your postcode where we have them, each one converted to a SHA-256 hash before it leaves us, together with your IP address, your browser's user agent, the two Meta cookies above, and two identifiers of our own, m3y_vid and one for your application, both hashed. We want to be plain about what hashing does and does not do. A hash is not anonymisation. Meta hashes the same values on its side and compares them, which is how it recognises you as one of its users. That is the point of sending it. Under California law, sending identifiers to an advertising network for cross-context behavioral advertising counts as sharing personal information. We do that, we are telling you we do it, and you can stop it at any time using the route in the next section. None of this runs anywhere else on mon3y.io. There is no pixel on the demo pages and none on the signed-in parts of the site.

We do not sell personal information for money. We do share it with Meta for advertising, in the way the section above describes, and California residents have the right to stop that. Use the form at /privacy/do-not-share. It does three things immediately: it records your request, it sets a preference in your browser that stops the pixel and the server-side measurement from running for you at all, and it tells us so we can honour it for the records we already hold. You can also email danny@mon3y.io or write to MON3Y, 750 Otay Lakes Rd #2017, Chula Vista, CA 91910 and say that you are opting out of sharing. Either way we act on it and we will not treat you differently for asking. An authorised agent may make the request for you, and we will ask for proof that you gave them permission.

If you tick the box to receive texts, we use your mobile number to text you about your application and your call. The texts are sent through Telnyx, our phone and text provider, which uses your number only to deliver them. Ticking the box is optional, and you can apply without it. We never share your consent to receive texts, or the fact that you gave it, with anyone else, and we do not sell your mobile number or share it for anyone else's marketing. The Advertising and measurement section above explains the one other place your number goes: a hashed copy is sent to Meta to measure our ads. Reply STOP at any time to stop our texts, or HELP for help.

We use a small number of companies to run this site, and each of them sees only what its job needs. Vercel hosts the site. Supabase holds the database the application is written to. Resend sends and receives our email. Calendly runs the booking calendar. Google Meet is where the call itself happens, so Google receives the meeting invitation. Telnyx is our phone provider: our calls to you go through it, and so do our texts if you tick the box for them. Meta receives the advertising measurement described above. Calendly is worth naming separately because of how much it sees. When the calendar appears after you submit the application, we pass your name, email address, mobile number, business name and trade into it so that you do not have to type them again. Calendly stores those with your booking, along with the campaign parameters that brought you here. We do not give your information to anyone else, and none of these companies may use it for their own purposes.

On the public pages listed above, the Meta Pixel sets two cookies, _fbp and _fbc, which identify your browser to Meta for advertising measurement, and we set m3y_vid, a random identifier of our own that we send to Meta in hashed form. It lasts a year. If you opt out using the form above, we set one preference cookie, named m3y_do_not_share, and its whole job is to stop all three from being used. When we test our own measurement, we open these pages from a special link that sets a cookie named m3y_tec for two hours, so that our test visits are kept out of the real figures. You will only have it if you followed such a link. The booking calendar is Calendly's, running inside a frame on our page, and it sets its own cookies under its own domain and its own policy. The signed-in parts of this site set a session cookie so that a signed-in person stays signed in. A visitor never reaches those pages. There is nothing else. No analytics suite, no tag manager, no advertising network other than Meta. You can block or clear cookies in your browser, and everything on the public side of this site keeps working if you do.

We build sample versions of what a website or dashboard could look like for a particular business, and we host them at addresses like examplecompany.mon3y.io. They are built from information that business has already published: its name, what it does, its public photos and reviews. Those pages carry no advertising pixel and no tracking. If one of them is about your business and you would rather it did not exist, email danny@mon3y.io with the address of the page. We take it down, and we do not ask for a reason.

We keep an application for two years from the day you send it, and we keep the record of a call for as long as we are working together plus the period our accountant needs afterwards. If you ask us to delete something sooner, we do. An opt-out request is the exception, because we have to keep a record of it in order to honour it. We keep those for as long as we hold anything about you.

If you live in California you have the right to know what personal information we hold about you, the right to a copy of it, the right to have it corrected, the right to have it deleted, and the right to stop us sharing it for advertising. Depending on where you live, you may have some or all of the same rights under another state's law, and we apply them the same way for everyone. To use any of them, email danny@mon3y.io and say which one, or write to MON3Y, 750 Otay Lakes Rd #2017, Chula Vista, CA 91910. To stop the advertising sharing specifically, the form at /privacy/do-not-share is faster and takes effect in your browser straight away. We will ask you enough to be sure it is you before we delete or hand over anything, because this site collects mobile numbers and we are not going to give one to whoever asks. We answer inside forty-five days. We will not treat you differently, charge you differently, or refuse to work with you because you exercised a right.

Traffic to this site is encrypted. The database sits behind row-level security, and the tables holding applications are reachable only by the server, never by a browser. Operational access is limited to the people who run the business, which today is a small number of named people. We are a small company and we are not going to pretend to hold a certification we do not have. If something goes wrong that affects you, we will tell you.

This site is for business owners and is not intended for anyone under 18. We do not knowingly collect information from children, and we do not sell or share the personal information of anyone under 16.

We may update this policy. When we do, the date at the top of this page changes, and the new version replaces this one here. If a change materially affects what we collect or who we send it to, we will say so at the top of the page rather than leaving you to find it.

Questions, corrections, deletion requests and opt-outs: danny@mon3y.io, or MON3Y, 750 Otay Lakes Rd #2017, Chula Vista, CA 91910.