Every company claims to have values. What almost none of them write down is what happens the day those values cost them money. That's what this page is for: so you know in advance what we'll choose — and can call us out if we don't live up to it.
GVenue was built by people from the trade: we ran clubs and events for years before writing a single line of code. And that's how we know something you can't see from the outside: a system like this accumulates two delicate things — data about people (who bought, who entered, who consumed) and power over people (who gets through the door and who doesn't).
We don't use lab-grade AI or train models: we use narrow, concrete AI — finding a product photo, suggesting a restock, answering what time doors open. GVenue's risk isn't science fiction: it's what gets done with your data and your door. That's what these red lines are about.
Each one with the same structure: if this happens, we do this. No poetry.
If someone offers us money for databases, audience cross-matching between clubs, or "aggregated insights" about your buyers…
…the answer is no. Your base isn't sold, isn't rented, and isn't crossed with another club's: each venue lives in its own compartment. And when we do need access (the backup of your database in GV Rental, for example), it's written in the contract, in plain sight — never silent.
If a feature could leave someone out of an event without anyone at the club having decided it…
…it doesn't get built that way. The admission list is loaded by a person at the club and the system records who loaded it, with room for the reason — visible only to your team, never to the buyer. GVenue enforces and audits it, it doesn't invent it: there is no block that nobody decided.
If a new module could profile your attendees by who they are —ideas, religion, who they go with— or follow them outside the venue…
…that module doesn't exist and won't exist. We record what the club needs to run its night: tickets, consumption, capacity. And the ID number identifies but doesn't authenticate: since July 2026, logging into your account requires a code sent to your email, not a number anyone can look up.
If dressing up a number would help close a sale —a capacity we don't measure, stock that doesn't add up, a "free" with fine print…
…we prefer the real number. Prices are published at /armar without talking to a salesperson, the service fee is itemized before you pay, and when a figure is uncertain the system shows it as uncertain — it doesn't invent certainty. The in-house rule is literal: first make it true, then write it.
If automating a decision about money or people would save support hours but leave an algorithm deciding on its own…
…it doesn't get automated. GVenue's AI finds the catalog photo, answers what time doors open. It frees up your staff's time; it doesn't decide who gets in, who gets charged, or how much. Those decisions have a first and last name — your team's.
GVenue grows by modules, and every new module with more power over data or over people goes through these lines before it's sold. If it crosses them, it doesn't ship: it gets redesigned until it doesn't. This isn't theory — it has already happened:
· AI credits are prepaid: the bot warns when they run out and the club decides whether to top up. We never charge usage upfront "so it doesn't cut off" — that was more convenient for us and less honest with you.
· Turnstiles and access readers are being evaluated with one non-negotiable design condition: a human at the club presses the button. If the integration doesn't allow it, it doesn't get integrated.
· In GV Rental (the system on your own server) the backup of your database to our datacenter is written into the contract as a benefit, with a first and last name — the convenient alternative was to sync silently, and it was discarded outright.
This document is reviewed every 6 months and every version is dated and published. If a review changes a red line, you'll be able to see what it said before and what it says now — promises edited in silence are not promises.
v1 · July 2026 · next review: January 2027
Behind GVenue there's no fund and no software factory: there's a small team based in Argentina that comes from the same trade as you and calls its clients by name. That's a policy too: we'd rather have few clients well cared for than many half-served.
Did you see something in GVenue that doesn't live up to what's written here? Tell us. We mean it: that's what makes this page worth anything.
somos@gvenue.com.ar