Privacy & cookies

HMDS 2027

HMDS registration and workshop privacy notice

The separate workshop interest form is available. This notice explains how the organizing team handles information for these services.

Last updated: 25 October 2026 · Notice version: 2026-10-25-approved3

Who handles your information

The HMDS 2027 organizing team handles event registration and participant enquiries. The payment-collection partner is KAILINKS LLC, a Wyoming limited liability company operating as KaiLinks. Its mailing address is 30 N Gould St, Ste N, Sheridan, WY 82801, United States. KaiLinks handles payment verification and refunds under the agreed terms. The organizing team manages participation and workshop enquiries; KaiLinks manages payment verification, refunds and the necessary financial records.

For privacy questions or requests, use the conference contact details or reply to your registration email. Do not send passwords, full card numbers, bank login details or identity documents.

HERO is a separate registration service

HERO competition team registration and technical submissions are managed on the HERO website, not by new HMDS registration orders. Review HERO’s privacy notice and participation terms there. Historical competition items in HMDS bookings remain part of those original records.

Latam AI Connect workshop form

The workshop interest and contribution form is separate from paid HMDS symposium registration. It uses Google Forms and a private Google Sheets response file in the organizer’s Google Drive. It collects your name, email, institution, contribution title or interests, a brief summary and, if supplied, a link to your work. The organizing team uses these responses to plan participation, review proposals and contact you about the workshop. Responses are not publicly displayed and are not a marketing subscription.

Google Forms sends a copy of your response to the email you enter. Please check it carefully. The form does not collect payments or identity documents; do not submit confidential research or other sensitive information. For corrections or deletion requests, use the conference contact details. Google also processes technical information under its privacy policy.

Information used for registration

The registration form collects your name, email, affiliation, country, participation category, selected activities and extras, and relevant EasyChair paper IDs. Accompanying-person names and affiliation details are collected when those tickets are selected. Sponsorship enquiries also collect an organization name, contact details, requested services and the selected contribution.

If you claim a discounted rate, we also record your eligibility category and, if applicable, your IFToMM affiliation. We use these details to review your eligibility.

The service records the itemized price, booking reference, payment method and status, payment-provider references, policy acknowledgement version and time, transactional email status, and an organizer activity history. It does not automatically copy your papers or reviews from EasyChair. Please inform accompanying people before entering their details and avoid sensitive personal information in free-text requests.

Booking recovery

Your booking email includes a private code for checking your saved registration and, where available, resuming its unpaid card checkout. The same code can be used for transfer-receipt uploads. A booking reference alone does not grant access. The code is sent in a secure request body, not a website link, and is not saved in browser storage. After you choose to resume checkout, the existing random payment-attempt identifier and reference are saved for that tab so the payment result can be checked. Keep your booking email and code private. A request to change payment method is prepared for you to send to the organizers; the page does not send that request or change the method automatically.

Transfer receipts

When enabled, bank and Wise payers can upload a PDF, JPEG or PNG receipt to their existing booking using the original registration tab or the private code in their email. The prepared limit is 2 MB per file and two files per booking. Exclude unrelated balances, full card numbers, bank login details and other people’s information. Files are stored in private registration tables, not a public website folder. Only authorized organizers can download them. A short review notification is sent to the approved organizers; it does not attach the file or its private code. Uploading a receipt does not confirm receipt of money.

Uploaded receipt files are retained for 180 days from upload. Rolling encrypted backups may retain an older copy for up to 30 additional days. Minimal financial and refund records are kept separately under the retention schedule below.

Why we use it

The prepared service uses this information to administer participation, match payments to bookings, handle registration corrections and cancellations, send booking and payment messages, support participants and keep necessary financial and security records. The form does not enroll you in a marketing mailing list. Any future optional marketing would need a separate choice; it must not be bundled into registration.

We use information to respond to your requests and administer your booking, meet financial recordkeeping requirements, and protect the service. Acknowledging this notice does not give permission for unrelated uses.

Service providers and international processing

  • Vercel: website hosting and the server-side registration service. Requests may generate operational/security logs, including IP address and request metadata. Analytics scripts have been removed from this version.
  • Supabase: private registration records and organizer authentication. Approved organizers use Google sign-in; attendees do not need an account. The Google login requests basic identity information, not access to Gmail or Drive.
  • Stripe: hosted card checkout and payment processing for KaiLinks. Card details are entered on Stripe's checkout, not in the HMDS form. HMDS stores payment references/status rather than full card numbers.
  • Resend: transactional registration and payment emails. Message content, recipient address and sending records are handled by the provider. The conference keeps delivery records for up to 90 days. Resend also applies its own provider retention policy.
  • Cloudflare Turnstile: anti-bot verification when a live registration form is enabled. It processes technical browser/network information under its Turnstile Privacy Addendum.
  • KaiLinks, banks and Wise: transfer receipt checks, payment administration and any agreed refunds. A payment screenshot alone does not establish receipt of money.

These providers may process information outside Japan. The providers listed above operate internationally; KaiLinks is based in the United States. Access is limited by role; a sponsor is not automatically given participant contact information.

Cookies and browser storage

This version does not load advertising or analytics scripts. Fonts are served from our own website. Functional browser storage is still used; “no analytics” does not mean that the browser stores nothing. The inventory below covers our application code, not a certification of every provider's behavior.

Application browser storage
ItemPurpose and duration
hmds-theme
hmds-background-motion
Local storage for your display and animation choices. No names or payment information. No application-set expiry; retained until cleared by you or the browser.
hmds-active-payment-registration
hmds-active-payment-sponsorship
Session storage for a random attempt identifier and booking reference, helping recover an interrupted payment attempt in the same tab. No form contact details or card data. Usually lasts for the tab session; browser session restoration may retain it.
hmds-organizer-auth, its PKCE verifier and hmds-organizer-idle-untilOrganizer-only session storage for sign-in tokens, the temporary login verifier and the inactivity deadline. Sensitive authentication information, not a public attendee list. Cleared by sign-out; 15 minutes of inactivity signs out the running dashboard, including when an expired tab is reloaded. Blocked storage can limit persistence across reloads. This does not guarantee immediate expiry of an already-issued token.

Google sign-in, Turnstile and the externally hosted payment services may use their own cookies or storage. Their own privacy notices explain their cookies and processing. External links load the destination's services when you follow them. We have not added a blanket “accept cookies” button: any future nonessential storage or tracking must first be assessed under the applicable rules and, where required, blocked until you opt in.

This clears only your theme and animation preferences. It does not cancel a booking, clear a payment recovery reference, or sign out an organizer.

How long we keep information

  • Ordinary attendee and workshop contact information: 6 months after the event.
  • Abandoned, unpaid registrations: 30 days.
  • Uploaded transfer receipts: 180 days from upload.
  • Conference email delivery records: 90 days.
  • Rolling encrypted backups: 30 days. Information removed from the active service may remain in a retained backup until that backup expires.
  • Minimal financial and refund records: 7 years, subject to KaiLinks’ accounting obligations and any longer legal requirement.

Only information needed for financial records, an unresolved dispute or a legal obligation is retained beyond the ordinary contact period. Provider operational and security logs follow the relevant provider’s own retention policy. These periods do not delete copies of emails or files you keep yourself.

Questions and requests

Contact the organizers to request access to, correction of, or deletion of information relating to you, or to ask about processing and available rights. We may need to verify your identity without collecting unnecessary documents. We will respond under the applicable rules. Financial-record obligations or an unresolved dispute may limit deletion of particular records; we will explain any such limitation.

Security and your choices

The system uses encrypted connections, server-checked organizer access, private database tables, server-calculated prices and verified payment notifications. These measures reduce risk but do not guarantee absolute security. Only provide the information requested, keep booking messages private, and report suspicious payment instructions using the conference contact details.

Review the separate cancellation and refund terms. Privacy requests do not automatically cancel attendance or trigger a refund.

Back to registration