This page describes the registration form on this site and the emails that follow it. It was written against the actual form fields, the actual database columns, and the actual sending code, not against a template. If something here does not match what the system does, the system is what needs fixing, and you should tell us.
Nick C. Gonzalez, operating under the trade name DealTunnel, based in Colombia. He is a sole proprietor. There is no company, no LLC, and no corporate group behind it. One person decides what happens to your data, and that person is accountable for it.
Contact for anything on this page, including any request about your data: nicolas@dealtunnel.io. A real person reads it.
The postal address is in Colombia and we will give it to you on request, by email, to anyone who asks. It is not printed on this page. Our commercial emails carry it in their footer, because US law requires it there.
This section exists because a policy that only lists its good decisions is a brochure. Both of these were found and fixed on August 31, 2026, before this version was published.
An unconfirmed postal address in our email footer. Until August 31, 2026 the footer of our emails carried a Miami street address that nobody had confirmed. It has been removed. The address is now supplied by configuration, and the sending code refuses to send any external email while it is missing: the message fails a pre-send check and is recorded as failed instead of going out with a blank or an invented address. We would rather send you nothing than send you something with a false address on it. That check is active right now, which means no email is going out to anyone until a confirmed address is in place.
An internal notification that went to a Gmail account. When a registration arrives, the system emails a copy to an internal address so a person can review it. Until August 31, 2026 that internal address was a personal Gmail account, which would have meant Google receiving the full contents of every registration form. It now goes to a mailbox on our own domain, and Google no longer receives any of it. To be exact about the damage rather than vague about it: the only three notifications ever sent to that Gmail account came from our own test registrations while the system was being built, not from any real registrant. We are telling you anyway, because you should judge us on what we do when we find something, not only on what we get right the first time.
The Revenue Room is run for business owners in Florida, and your data is stored on infrastructure in the United States. Section 14 explains what that means for you.
Two things, and nothing else:
It also covers the contact page and the unsubscribe page on this site. It does not cover other DealTunnel pages, other campaigns, or any conversation you have with us outside those emails.
Seven answers and two consent choices. Everything is stored exactly as you typed it.
| Stored as | What it is |
|---|---|
| full_name | Your first and last name. |
| work_email | Your work email. The form declines personal webmail addresses, and so does the server before any email is sent. |
| company | Your company name and website, as one field. |
| role | One of four options you pick from a list. |
| revenue_range | One of three revenue bands you pick from a list. A band, never an exact figure. |
| product | What you distribute, in your own words. |
| buyers | The kinds of companies that buy it, in your own words. |
| consent | The required box: session emails, and your acknowledgment that the session is recorded. |
| marketing_consent | The optional box: follow-up from DealTunnel after the session. Stored as false unless you tick it. |
The form does not ask for a phone number, a home address, a date of birth, a government ID, or payment details, and the form has no field for them.
On the unsubscribe page, the only thing we collect from you is the email address you want removed, plus one hidden field that is always empty for a real person and exists to catch automated submissions. Your browser also loads fonts on that page, which is covered further down under what your browser sends.
| Stored as | What it is |
|---|---|
| id | A random identifier for your registration. |
| created_at | When you registered. |
| work_email_norm | Your email in lowercase, so a second registration with the same address updates your record instead of creating a duplicate. |
| event_id | Which Revenue Room you registered for. |
| status | Pending, approved, or declined. |
| reviewed_at, reviewed_by, approved_at | When a human reviewed your registration and who. |
| notes | A free text field an operator can write in during review. It is the one place in the system where something about you could be recorded that you did not type yourself. Write to us and we will tell you whether anything was written about you, and what. |
| attended | Whether you showed up. Set by hand after the session, from the attendee list. |
| attendance_source, attendance_recorded_at | How and when that was recorded. |
| unsubscribed_at | The date you unsubscribed, if you did. This timestamp is the whole of our unsubscribe record. See section 09. |
| bounce_state | Whether your address is deliverable. Every record starts at "ok" and nothing in the system has ever changed it. See section 09. |
| updated_at | When your record last changed. |
Each email in the sequence gets one row in a separate log: which email it was, which address it went to, whether it was sent, scheduled, blocked, skipped, canceled or failed, the identifier the delivery provider gave it, and the timestamp. That log exists to guarantee you never receive the same email twice, and to let us prove what was sent if you ask.
When the system is running in rehearsal mode, the log also keeps the subject line and the full text of the email that would have gone out. In live mode it does not store the body.
GTM-N7WLWBM3. Through that container we measure page visits and form submissions. It does not run on this privacy page, on the contact page, or on the unsubscribe page. To be exact about the limit of what we can tell you: the individual tags inside that container are configured outside the page source, so this policy cannot list them one by one or promise that the container holds nothing else. Ask us and we will tell you what is in it.dt_theme. It never leaves your device and it is not linked to you.One purpose per field. If a field had no purpose we could state, the right answer would be to stop collecting it.
| Data | What it is used for |
|---|---|
| full_name | To address you by name in the emails, and to match you against the attendee list after the session. |
| work_email | The only channel we use to reach you. Also checked against the mail records of your domain before anything is sent, so a typo does not turn into a bounce. |
| company | To decide whether you fit the room, and to name your company in the emails. |
| role | To decide whether you fit. The room is for people who can decide. |
| revenue_range | To decide whether you fit the $2M to $50M band the room is built for. |
| product | To decide fit, and as the input to your free Revenue Audit. It is also the line we can filter the public business registry against, live, during the session, if you volunteer it. |
| buyers | Same. It is the line your audit gets built against, which is why we ask you to correct it if it is wrong. |
| consent | To hold proof that you asked to hear from us about the session and were told it is recorded. |
| marketing_consent | To record whether you separately agreed to follow-up. Today it is a record, not a switch: no code reads it, so a person has to check it before any follow-up goes out. See the note below. |
| attended | To decide which follow-up you get after the session: the one for people who came, or the one for people who did not. |
| unsubscribed_at | To stop sending. Every email in the system passes through one function, and that function refuses to send anything to a record with this date set. |
The optional consent is enforced by a person, not by the software. No code reads that field today. There is also no follow-up email in the sequence yet, so there is currently nothing for it to hold back. Before any follow-up is ever built, either the software will check the field or a person will, and until the software does it, a person does. We are saying this because section 10 sets the rule for this whole page: when something is done by hand, it says so, and this is the place where that rule matters most.
Your registration is also emailed to an internal address on our own domain the moment it arrives, so a human can approve or decline it within 24 hours. That internal message contains your name, work email, company, role, revenue band, product and buyers. Section 01 explains what that address used to be and why it changed.
We do not build a profile of you from third party sources, we do not enrich your record with data bought elsewhere, and we do not use what you typed to target advertising at you.
The form has two separate checkboxes, and they do different things. One box covering both would have been easier for us and worse for you.
| Box | What it covers |
|---|---|
| Required | Emails about this session: the acknowledgment that we read your request, the yes or the no, the calendar invite, the reminders, and the recording afterward. It is also where you are told that the session is recorded. Without it we cannot run the registration at all, which is why it is required rather than optional. |
| Optional | Follow-up from DealTunnel after the session is over. Leaving it unticked costs you nothing: you keep your seat, you keep your free Revenue Audit, and you still get everything in the row above. |
If you leave the optional box alone, it is stored as a no. Not as a blank we can interpret later. A no.
Anyone who registered before August 31, 2026, when the form had a single combined box, is recorded as not having given the optional consent. They never saw a separate box, so they could not have ticked one, and we are not going to infer an agreement that was never offered.
Unsubscribing stops everything, both boxes at once. There is no arrangement where you leave the session emails and stay on a marketing list.
We would rather tell you the shape of this than let you assume it is sturdier than it is.
What we store is two yes or no values attached to your registration, plus the date the registration was created. We do not store the moment you ticked the box as an event of its own, we do not store your IP address, and we do not store which version of this policy was on screen when you agreed. That means our record shows that a submission carrying your email address included those answers. It does not, by itself, prove which person was at the keyboard.
That matters because of how a repeat submission works. If a registration arrives for an email address that is already in our records, the answers are refreshed, and the optional consent can be switched from no to yes but never from yes back to no. We built it that way so that an accidental resubmission could not silently strip a consent someone had given. The honest other half: the same rule means a second submission can silently grant that consent, it can be sent by anyone who knows the address, and once granted that route cannot take it back. The word "you" in "if you register a second time" is not something the form verifies.
Two things are true alongside that. Unsubscribing always works and is not affected by any of this, so nothing here can trap you on a list. And a consent given that way still cannot produce a follow-up email today, because as section 04 explains, a person checks that field before anything goes out.
Still open. Recording the moment of consent and the version of this policy shown at the time is a change to the system, not to this page, and it has not been made yet. It is on the list, and this paragraph stays here until it is done.
Five companies, named, with what each one actually sees. "Trusted third parties" is not a disclosure, so here is the list.
| Company | Role | What it sees |
|---|---|---|
| Vercel | Hosts this site and the unsubscribe endpoints. | Your IP address and request details in its server logs. Not your form answers, which go straight to the database. |
| Supabase | The database where your registration is stored. | Everything in section 03. |
| Resend | Delivers every email we send, including the internal copy of your registration and the notice generated when you use the unsubscribe page. | Your name, your email address, and the full text of each message, which mentions your company, your product and your buyers. |
| Tag Manager on the registration page, and the font files on every page of this site. | Your IP address and browser details on every page, and your behavior on the registration page. It does not receive the contents of the form. That statement is true as of August 31, 2026 and was not true before; section 01 explains what changed. | |
| Zoom | Runs the live session itself. | The name and email you use to join, your connection details, and your camera, microphone and chat while you are in the room. See section 07. |
The jsDelivr public CDN also serves one code library to the registration page and sees your IP address and browser as a consequence. It never receives your form answers.
Each of these companies processes your data on our instructions, under its own terms and its own security controls. We do not hand your data to anyone else.
The Revenue Room is a 45 minute session on Zoom, and it is recorded. You are told this on the registration form, before you decide, and again in the email that confirms your seat. Florida requires the consent of everyone being recorded, so telling you at the door would be too late.
The recording is then sent by email to everyone who registered and was approved, whether they attended or not.
Which means: if you speak, ask a question, turn on your camera, or type in the chat, that ends up in a recording that other attendees receive. Plan accordingly. You can attend with your camera off and stay silent, and nothing of you beyond your name in the participant list will be in it.
The recording will be announced again out loud at the start of the session, before anything is captured. If you do not want to be in it, say so in the chat or leave, and either way the recording still reaches you afterward.
We keep the recording for 12 months from the date of the session, then delete it. It is made through Zoom and delivered to you as a link. We are not naming a storage provider on this page, because at the time of writing the session has not happened and no recording exists yet. Once it does, we will tell you where it is held if you ask.
Real periods, not "as long as necessary", which is a way of not answering.
| What | How long |
|---|---|
| Your registration record, including the date you unsubscribed if you did | 24 months from our last contact with you |
| The log of emails sent to you | 24 months |
| The session recording | 12 months from the session |
"Last contact" means the most recent email we sent you or you sent us, whichever is later. If you never hear from us again after the session, the clock runs from the last email in the sequence.
When you unsubscribe, we do not move you onto a second list. We write a date into your existing registration record, and every email the system sends checks that date first. That is the entire mechanism. It is simple and it works, and it has one consequence worth being straight about.
Because the unsubscribe date lives inside your registration record, it lasts exactly as long as that record does, and it disappears if that record is deleted. So if you ask us to delete you outright, you are also deleting the thing that remembers you asked us to stop. Nothing would then prevent your address from entering the system again through a future registration, and we would have no record telling us not to write to you.
That is a real trade and it is yours to make, not ours to make quietly on your behalf. Section 10 sets out both options when you ask for deletion, and we will ask you which one you want rather than assume.
These periods are enforced by a person reviewing the records, not by an automated job that expires rows on a schedule. We are telling you that because a policy that describes automation which does not exist is a false statement, and because it does not change your rights: you can ask us to delete you at any point before those periods run out, and section 10 explains how.
One thing that is automatic: the log of emails sent to you is tied to your registration. If your registration is deleted, that log goes with it.
About the bounce_state field in section 03, since it does have an effect: every record is created as "ok", and that value is one of the conditions the system checks before sending you a reminder. Nothing in our software has ever set it to anything else, so no address has ever been marked as bouncing or complaining. If your address stops receiving mail, we find that out from the delivery provider and act on it by hand.
Below is what the system does today, not what it could do one day. Where something is done by hand, it says so.
The link in any email we sent you. Automatic and immediate. Every email carries a personal unsubscribe link in its footer. One click and it is done, on the spot, with no login and no waiting. The link is signed, so nobody else can unsubscribe you by guessing. Clicking it does two things: it cancels any reminder already scheduled with our delivery provider, and it writes the date into your record that every send checks before going out. Our emails also carry the standard headers that make Gmail and Outlook show their own one click unsubscribe button at the top of the message; that button reaches the same place. If you have one of our emails in front of you, this is the route to use.
The unsubscribe page on this site. Handled by a person. Someone arriving there has no email in hand and no signed link, so there is nothing to prove the address is theirs. Rather than let anyone unsubscribe anyone by typing an address, the page sends a notice to an internal mailbox that Nicolás monitors, and he processes it by hand. The page does not change anything in the database by itself, and we are not going to pretend otherwise: until he acts on it, the system still considers you subscribed, and a scheduled reminder could still reach you in the meantime. US law allows up to ten business days to complete an opt out; in practice it is done the day he reads it. If you want it to stop the instant you click, use the link in any of our emails.
You can also just reply to any of our emails, or write to nicolas@dealtunnel.io. Same result, same hands.
If you want the follow-up to stop but you still want the emails about the session you registered for, say so at nicolas@dealtunnel.io and we will set the optional consent back to no by hand. This one is manual. The unsubscribe link is all or nothing, and we are not going to describe it as something more selective than it is.
There is no self service export button, and we are not going to pretend there is. Email nicolas@dealtunnel.io from the address you registered with and ask. You get back your registration record and the list of emails we sent you. We answer within 30 days.
If your product line or your buyer types are wrong, too broad, or missing the category that actually pays you best, reply to any of our emails and fix it. Two lines is plenty. We will also correct your name, company or role on request.
Email nicolas@dealtunnel.io and ask to be deleted. This is a manual operation performed by one person, not an automated pipeline, so it takes as long as it takes to be done properly, and no more than 30 days. Deleting your registration also deletes the log of emails sent to you.
The question we will ask, for the reason explained in section 09: deleting your record also deletes the date that records your unsubscribe, because that date lives inside the record. So you can have either of these, and you tell us which.
If you do not tell us which, we will ask rather than choose for you.
If you are in Colombia, Law 1581 of 2012 gives you the rights to know, update, correct and delete your data, and to withdraw the authorization you gave. Requests go to nicolas@dealtunnel.io. Questions are answered within 10 business days, extendable by 5 more; complaints within 15 business days, extendable by 8 more. If you are not satisfied with our answer, you can escalate to the Superintendencia de Industria y Comercio.
Copying clauses from laws that do not apply to us would make this page longer and less honest. So here is the actual assessment.
Every email we send you about this session is commercial email to a recipient in the United States. That means truthful subject lines and headers, a real postal address in the footer, a working opt out, and honoring it within ten business days. All four are in place, and section 01 explains how the postal address is handled.
The person responsible for your data is domiciled in Colombia, which brings the processing under Colombian law regardless of where you are. That is why section 10 carries the Colombian response deadlines and names the Colombian supervisory authority. That law also requires us to keep proof of the authorization you gave, which is why section 05 sets out exactly what our record proves and what it does not.
Florida requires the consent of every party to record a communication. Section 07 is how we meet that: disclosed on the form before you register, repeated in the confirmation email, and announced again at the start of the session.
California's law applies to a business that meets at least one of three thresholds: more than roughly $25 million in annual gross revenue, or handling the personal information of 100,000 or more California consumers or households, or making half its revenue from selling or sharing personal information. DealTunnel meets none of them, and it does not sell or share personal information at all. If that ever changes, this page changes with it.
Your audience here is Florida, so this is worth being precise about. Florida's 2024 privacy law is written for controllers with more than $1 billion in global gross annual revenue. It does not reach a sole proprietor. You are not losing a right by registering with us; that particular law simply does not cover an operation this size. The recording rule in the paragraph above is a different Florida statute, and it does apply.
The Revenue Room is offered only to distributors in Florida. We do not market it in Europe or the United Kingdom, this page and the registration page are excluded from search engines, and we have no European establishment. On that basis European law does not apply and we have not appointed a representative under it.
There is no cohort planned outside Florida, and this page does not promise one. If that ever changes, the consent language and this section get rewritten before the first invitation goes out, not after.
What we can state precisely, because it is in the code:
One weakness we will name ourselves, because section 05 depends on it: the registration form accepts a submission from anyone, without verifying that the email address belongs to the person submitting it. That is what makes a form usable without an account. Section 05 sets out what it means for our record of your consent.
What we will not claim: that this is unbreakable. It is a small operation on well run infrastructure. If we ever discover a breach affecting your data, we will email you about it directly.
This is a business session for company owners and executives. It is not directed at anyone under 18, and we do not knowingly collect data from anyone under 18. If you believe a minor has registered, write to us and we will delete the record.
You are in the United States. The person responsible for your data is in Colombia and accesses it from there. The site, the email provider and the database are run by US companies.
Your registration is held on Supabase infrastructure. We are not naming a specific data center on this page, because we have not verified one in writing and we do not publish facts we have not confirmed. Ask and we will tell you the region.
The practical answer, which is the part that affects you: by registering, you understand that one person outside the United States reads your registration in order to decide whether you fit the room.
When this page changes, the effective date and version at the top change with it. If a change materially affects what we do with data you already gave us, we email you before it takes effect rather than quietly editing the page.
Version 1.1 corrected several statements in version 1.0 that an internal audit found to be inaccurate against the running system, and describes fixes made to the system on the same day. Both are set out in sections 01, 04, 05, 09 and 10 rather than buried in a changelog.
Nick C. Gonzalez, sole proprietor, trading as DealTunnel, based in Colombia.
Email: nicolas@dealtunnel.io
Postal address: given on request, by email, to anyone who asks.
Use that address for any request in section 10, for anything on this page you think is wrong, and for anything the system does that this page failed to describe. The second and third are the ones we most want to hear about.
There is also a contact page and an unsubscribe page on this site.