In short
- We collect what the Service needs and nothing more. No advertising trackers, only visit statistics for this website through Google Analytics (section 9), and we never sell personal data.
- Attendee data belongs to the organiser. If you registered for someone's event, that organisation decides how your data is used; we process it on their behalf and help them answer your requests.
- Each organisation's data is kept separate, credentials are encrypted or hashed, and every change is recorded in an audit trail.
- You can ask to see, correct or erase your data. We answer access and correction requests within 40 days as the Hong Kong Ordinance requires.
1. Who we are and our roles
VICO Events is operated by VICOSYS (泓浩系統有限公司), a company incorporated in Hong Kong. This policy applies to the website at events.vicosys.com.hk, to the VICO Events application and API, and to the widget that our customers embed in their own websites.
We handle personal data in two different roles, and your rights depend on which one applies:
- As a data user (the term the Personal Data (Privacy) Ordinance uses for what other laws call a controller) for the data of visitors to this website, of people who contact us, and of the people who hold and use customer accounts. We decide why and how this data is used, and sections 2 to 13 apply in full.
- As a data processor for the data of attendees who register for our customers' events. The organisation running the event (the organiser) is the data user. We process attendee data only on the organiser's instructions, as given through the Service's features, and we never use it for our own purposes. If you are an attendee, the organiser's own privacy statement governs your data, and section 8 tells you how to exercise your rights.
2. Data we collect
2.1 Visitors to this website
- Contact and trial requests. When you use the contact or free-trial form we store your name, email address, organisation (if given), the plan you have in mind, your message, the language you used, and the time of the request. The form has a hidden field used to catch automated submissions; it holds no data about you. Our forms also use Google reCAPTCHA to detect bots (section 9).
- Server logs. Our web servers record each request's IP address, time, requested page, browser type and the page that referred you. We use these to keep the site running and to detect abuse.
- This website uses Google Analytics to count visits and see which pages are read and which forms are completed; see section 9. It sets no advertising cookies. The language you pick is reflected in the page address, not stored about you.
2.2 Customer accounts and their users
- Account details. The organisation's name, its account email address and, if set, a public contact email, logo, time zone, languages and the address of the page where the widget is embedded.
- Users. Each dashboard user's username, email address, role, optional notification email, and a password that we store only as a salted hash. Password reset tokens are stored hashed and expire quickly.
- Credentials you give us. If you connect your own email server or bot-protection service, we store those credentials encrypted and use them only to send your attendee email or verify registrations. API keys are stored as hashes and shown to you once.
- Activity records. The dashboard and API write an audit trail of who did what and when, with the IP address the action came from, for example when an event is published, a key is rotated or an attendee is erased. Logins create a session record. We also count API requests per account per day for metering.
- Billing. Subscription periods, invoices and payment status. Card payments go directly to our payment provider: we never see or store full card numbers, only the payment status, the card's last four digits and expiry, and a reference token. Invoiced accounts pay by bank transfer or FPS.
- Support. The messages you send us and our replies.
2.3 Attendees of our customers' events
When you register for an event through a VICO Events widget or an organiser's own integration, the organiser collects, and we store on their behalf:
- your name and email address, and your answers to any extra questions the organiser added to the form;
- the language you registered in, the event or date you chose, your registration status (confirmed, waitlisted, cancelled), your ticket code and whether and when it was checked in;
- the emails sent to you by the Service on the organiser's behalf: confirmations, tickets, reminders, event updates and broadcasts;
- the IP address and browser details of the request that created the registration, used to limit repeated submissions and to detect bots, and, if the organiser has enabled it, a bot-verification token from Cloudflare Turnstile or Google reCAPTCHA;
- a daily count of how many times an event page was viewed. This is a number, not a record of who viewed it.
Organisers decide which questions to ask. We advise them not to collect sensitive data unless the event genuinely needs it.
3. How we use it
| Purpose | Data used |
|---|---|
| Providing the Service: showing events, taking registrations, enforcing capacity and plan limits, issuing tickets and check-in | Account, user and attendee data |
| Sending the emails the Service exists to send: registration confirmations, tickets, reminders, event updates and organiser broadcasts; login, password-reset, trial and renewal notices to account users | Email addresses, names, registration and account details |
| Answering your enquiry or trial request and following up on it | Contact-form data |
| Billing and account management, including charging renewals | Account and billing data, payment references |
| Security: preventing abuse, rate limiting, bot detection, investigating incidents, and keeping an audit trail for organisers | IP addresses, logs, audit records, verification tokens |
| Improving the Service, using aggregated figures such as registrations per day or API calls per account, never individual profiles | Counts and metering data |
| Meeting legal obligations, for example keeping business records and responding to lawful requests | Whatever the obligation requires |
We do not use personal data to build profiles, to make automated decisions with legal effect, or to train machine-learning models.
4. Who we share it with
We do not sell personal data and we do not share it for other organisations' marketing. We share it only with:
- The organiser whose event you registered for. They see their attendees' registrations in their dashboard and through their API keys, and can export them.
- Service providers who process data for us under written terms, only to the extent needed for their task:
- cloud hosting and database providers that run the Service and store its data and backups;
- a payment provider (PayPal) that processes online payments and holds payment details under its own privacy policy;
- Google Analytics, which processes visit statistics for this website on our behalf (section 9);
- an email delivery provider that sends the Service's email, unless the organiser has connected their own email server, in which case attendee email goes through that server instead;
- a content delivery network (such as Cloudflare) in front of the Service; Cloudflare Turnstile or Google reCAPTCHA, whichever an organiser has enabled for bot verification; and Google reCAPTCHA on this website's contact, free-trial and subscribe forms (section 9).
- Systems the organiser connects. Organisers can register webhook endpoints that receive registration events, and the widget runs on the organiser's own website, which may have its own cookies and analytics. Those are governed by the organiser's privacy statement.
- Professional advisers and authorities when the law requires it, to protect our rights or the safety of others, or in connection with a sale or reorganisation of our business, in which case the new operator is bound by this policy.
Customers can ask us for the current list of service providers at any time through the contact page.
5. Where data is stored
The Service's database and backups are hosted with cloud providers that may store data outside Hong Kong. Wherever data is stored, it is protected by the measures in section 7 and by contractual terms with the provider that require a standard of protection at least as high as this policy. We will tell customers before moving the primary storage location of their data to a different jurisdiction.
6. How long we keep it
| Data | Kept for |
|---|---|
| Contact and trial requests | Up to 24 months after the request, then deleted unless an account was opened |
| Web server logs | 30 days |
| Events, registration forms and attendee registrations | While the account has a plan or trial, unless the organiser deletes the event, erases the attendee or a retention setting anonymises them earlier. 90 days after a plan or trial ends without renewal (the export window) they are deleted from the live Service within 30 days and from backups within a further 30 days. Anonymised registrations keep only counts (for capacity and reports), not names or email addresses |
| Account record (organisation, users, settings, keys) | While the account exists, and up to 12 months dormant after its last plan or trial; then, or when the organiser asks us to close it, deleted from the live Service within 90 days and from backups within a further 30 days |
| Audit trail and security records | While the account exists, then deleted with it; entries about an erased attendee never contain the attendee's details |
| Session records | 7 days, or until you log out |
| Invoices and billing records | 7 years, as Hong Kong tax law requires |
7. How we protect it
- All traffic to the Service, including the widget, is encrypted in transit (HTTPS).
- Passwords and API keys are stored only as hashes. Credentials you give us for your own email or bot-protection service are encrypted at rest.
- Each organisation's data is isolated: a login or key for one account cannot read another's. Publishable keys, the ones placed in web pages, can create registrations but can never read attendee lists.
- Login attempts, form submissions and API calls are rate-limited, and registration forms carry bot-detection measures.
- Every change to an account is recorded in an audit trail that the organisation can review.
- Access by our staff is limited to what support, security and legal obligations need.
- If we become aware of a breach affecting personal data we hold, we tell the affected customers without undue delay and, where the Ordinance or guidance requires, the Privacy Commissioner.
8. Your rights
Under the Personal Data (Privacy) Ordinance you may ask to access the personal data we hold about you and to have it corrected. We respond within 40 days of a request. You may also ask us to erase data we no longer need, and to stop using your data for direct marketing at any time.
- If you are a website visitor or an account user, send your request through the contact page. We may ask you to confirm your identity first. Account users can change most of their details themselves in the dashboard.
- If you are an attendee, please contact the organiser of the event first: they are the data user and have the tools to see, correct and erase your registration. If you cannot reach them, or they do not act, contact us and we will help; we also erase attendee data on an organiser's instruction immediately.
We do not charge for handling a request unless the Ordinance allows it and we have told you the fee in advance.
9. Cookies and browser storage
- This website uses Google Analytics to count visits and see which pages are read and which forms are completed. For that purpose Google sets its analytics cookies (
_gaand_ga_*, kept for up to two years) and receives the page address, a truncated IP address and your browser's details. We have not enabled advertising features or Google Signals, and we keep the reports for 14 months. Nothing else is set by this website. - Forms on this website. The contact, free-trial and subscribe pages use Google reCAPTCHA to tell people from bots. On those pages Google receives your IP address, your browser's details and how you interact with the page, may set its own cookies, and handles this data under its Privacy Policy and Terms of Service.
- The dashboards set one session cookie after you log in. It is essential to keep you signed in, is only readable by the server, and expires after 7 days or when you log out. The dashboard also remembers a few display preferences, such as a page size, in your browser's local storage; these never leave your browser.
- The embedded widget sets no cookies. It may remember the layout you last chose in your browser's local storage on the organiser's website. The organiser's own website may use cookies independently of us.
10. Marketing
We email account users about their account: trial and renewal notices, invoices, security notices and changes to the Service or these documents. These messages are part of the Service and continue while the account exists.
We send marketing about VICO Events only to people who have asked to hear from us, for example by requesting a trial, and every such message carries a way to opt out. We never send marketing to attendees of our customers' events, and we never use attendee email addresses for our own purposes.
11. Children
VICO Events accounts are for organisations and are held by adults. Organisers may run events for younger attendees; in that case the organiser is responsible for obtaining a parent's or guardian's consent where the law requires it, and for setting an appropriate retention policy. If you believe a child's data has been given to us without such consent, contact us and we will help the organiser remove it.
12. Changes to this policy
We may update this policy as the Service and the law change. Material changes are announced to account owners by email and in the dashboard at least 30 days before they apply. The version and effective date at the top of this page identify the current version.
13. Contact and complaints
For any question or request about personal data, write to us through the contact page. VICOSYS is based in Hong Kong; our company details are on vicosys.com.hk.
If you are not satisfied with our response, you may complain to the Office of the Privacy Commissioner for Personal Data, Hong Kong (pcpd.org.hk).