iVenue information
Terms of Use
1. Educational project and demo features
iVenue is an educational and demonstration event-discovery and ticketing project. Its accounts belong to real users, but reservations, ticket prices, seating and stored orders are demo features. iVenue does not process real payments or issue tickets with monetary value or a right of admission.
The current checkout displays and validates a reservation. Its order button reports that payment integration is unavailable; it does not collect card details or complete a real purchase, and the reservation keeps its original expiry. Existing demo order records or a demo “paid” status do not evidence a financial transaction. There is no real payment-refund or ticket-refund service.
2. Required policies and optional consent
The account flow requires acceptance of the current Terms of Use and acknowledgement of the current Privacy Policy. The site records the required policy versions and acceptance time. When required versions change materially, existing users are asked to accept or acknowledge the new versions.
This acceptance is separate from optional newsletter consent and does not authorize unrelated use of personal information.
3. Accounts and authentication
Use information you are entitled to provide, maintain accurate account details, and protect your account and device. Email/password registration uses email verification. Password recovery uses the site's email-code flow. Google sign-in is supported; Google users without an iVenue password are directed to create one before continuing.
Some account actions require your current iVenue password, and sign-in or protected actions may require an additional emailed verification code. A verified browser can be remembered for up to 24 hours. Follow the site's password-setup, verification and recovery flows; do not bypass them.
Complete required email verification promptly; unverified accounts may be automatically removed as explained in the Privacy Policy. Never send a password, OTP, access token, refresh token, session token or other authentication credential by email or to Support. Enter credentials only inside the appropriate secure site form. Do not impersonate another person, use someone else's credentials, or create accounts to evade a restriction.
4. Seat selection, carts and reservations
The ticket-selection interface limits each selection to four demo tickets. This is a per-selection limit, not a lifetime purchase allowance.
Selecting an available individual seat creates a temporary server-side hold associated with your account. The current reservation period is 10 minutes, and the interface displays the relevant countdown. A cart entry or a locally saved selection alone is not a permanent reservation or a ticket.
You cannot keep active server-backed reservations for different events at the same time. Finish or release the existing reservation, or let it expire, before reserving for another event. Seats may become unavailable because another user has reserved them. Expired holds are released and associated exact-seat cart entries are removed by expiration handling. Availability may be refreshed when the service processes the expiry.
Reservation and checkout access depends on the event's current eligibility and available inventory. Ended or unavailable events cannot be reserved through the current protected flow. Changing browser storage, manipulating requests or opening additional accounts must not be used to evade these rules.
5. Acceptable use
Do not use iVenue for fraud, unlawful conduct, impersonation, unauthorized access, malicious code, harmful exploitation of vulnerabilities, interference with availability, inventory manipulation or deliberate circumvention of reservation or account restrictions. Do not use automated activity to unfairly hold demo inventory or disrupt the service.
Do not harass, threaten or abuse users or Support personnel, or submit personal information about another person without an appropriate reason and authority. Good-faith complaints and bug reports, accidental errors and ordinary use of browser development tools are not automatically violations. Report vulnerabilities responsibly without accessing, modifying or destroying another person's information.
6. Support
The Contact form requires a signed-in customer with a completed profile name and email. Requests contain a subject, category and message. Conversations can be open, waiting for your reply, or resolved. Authorized Support employees can review the queue, reply, claim and resolve requests; administrators oversee assignment and Support access. Admin and Support employee accounts do not submit requests as customers through this form.
A resolved request cannot be reopened under the current lifecycle rules; use a new request for a new issue. Deleting a request from your dashboard hides it and ends its active workflow rather than immediately erasing it. Daily cleanup removes resolved or customer-deleted requests and their messages after 90 days from the later relevant resolution/deletion time. Open, undeleted requests have no fixed automatic cleanup period.
Communicate respectfully and provide only information needed to address the issue. Support is a communication channel, not a place to send authentication credentials or confirm account deletion by password.
7. Recorded violations and warnings
An authorized administrator can record a violation type, severity, points, reason, internal notes, date and optional expiry. Severity points help the administrator assess an account; recording a violation or reaching a point total does not automatically ban it. The current enforcement tools do not guarantee a separate warning notice before a restriction.
Serious or repeated misuse may justify an account restriction without a prior warning. A good-faith report or complaint should be evaluated on its circumstances rather than treated as misuse merely because it is critical of the project.
8. Temporary and permanent restrictions
Administrators can apply a temporary ban for 24 hours, 7 days or 30 days, or a permanent restriction, and can record a reason. Restrictions affect authentication and protected account operations. A temporary ban ends according to its duration; a permanent restriction remains until an authorized administrator removes it.
An administrator can review and remove an active restriction, recording an unban note. Ban, unban and violation history is retained after a restriction ends or is removed; expiry does not erase the record. Account deletion does not automatically erase enforcement notes. Do not evade restrictions with another account or interfere with a review.
You may ask for review through the signed-in Contact form when available. If you cannot access your account and need to make a privacy or personal-data request, use the email contact in section 13. The interface does not guarantee an automatic detailed ban notice, reason or appeal outcome.
9. Newsletter
Newsletter subscription is optional and requires its own consent checkbox. You can unsubscribe using a newsletter's unsubscribe link. Unsubscription makes the email inactive for future newsletter sends; it does not delete historical subscription or campaign records, delete your account, or prevent necessary security emails.
Account deletion and changing an account email do not automatically unsubscribe a separately stored newsletter address. Unsubscribe separately from each address you no longer want subscribed. Campaigns can target all active subscribers or selected active subscribers; administrators test campaigns before sending them.
10. Account deletion and personal information
The supported self-service deletion flow is in the signed-in account dashboard. It requires the current iVenue password and any requested sign-in security verification. Google-only users must first configure an iVenue password; Google users who already have one use that password, not their Google password.
Successful deletion removes the Auth account and profile and signs you out in the account interface; it does not guarantee that every previously issued access token immediately becomes invalid or permanently erase all historical information. Demo orders and activity statistics are disassociated; copied Support identity/message information, email-based newsletter history, enforcement notes and uploaded images can remain. See User Data Deletion and the Privacy Policy for the exact distinctions and retention rules.
The current self-service deletion endpoint rejects an account restriction. A user who cannot use that flow needs separate assistance through a verified channel; a Support message does not itself execute deletion or replace password confirmation.
11. Intellectual property and external services
Original iVenue code, design and original content may be protected by applicable intellectual-property rules. Third-party event names, photographs, performer names and trademarks belong to their respective owners where applicable. Their use in a demo does not establish sponsorship, endorsement or affiliation.
External sign-in, maps, images, fonts, links and sharing services operate under their own terms. Do not upload images or content you are not entitled to use. Uploaded profile images are served by publicly accessible links.
12. Availability and changes
The project can change, become temporarily unavailable, or have demonstration records reset during development. It does not guarantee uninterrupted access, event availability, reservation completion, real admission or a commercial ticket purchase. This educational status does not remove responsibilities concerning real users' personal information or their applicable legal rights.
Changes to required policies are dated and handled by the existing versioned acceptance flow. Optional newsletter consent remains separate.
13. Applicable rights and contact
Nothing in these Terms removes rights available under applicable Georgian law, including personal-data-protection rights. The Privacy Policy describes information processing and requests.
For privacy and personal-data questions or requests, email privacy@ivenue.site; account access is not required. For other questions use the signed-in Contact form. Never send passwords, OTP codes, access tokens, refresh tokens, session tokens or other authentication credentials by email or through Support.