Enquiries, applications and registrations
Forms collect your name, email and the information you enter, such as your company, portfolio, project brief or application. We use this information to review and respond to your request. Only authorized MicroX administrators can access the shared inbox.
Hackathon entries and verification records
Hackathon registration collects student contact details, institution, skills, track and optional teammate details shared with their permission. Project submissions collect source, demo and video links for authorized reviewers. A private submission key controls access to an entry; only its hash is stored. Admins can review or remove entries. Verification results show only consented public identity, role, dates and credential status, never private contact information.
Public team profiles
The team directory displays the names, portraits, roles, introductions and optional LinkedIn profiles that authorized admins choose to publish. Portraits are resized and re-encoded before upload. Hidden profiles and their portraits are available only to authorized profile editors. Contact MicroX if a public introduction needs to be corrected or removed.
Team workspace
Workspace access uses an email and password approved by MicroX. Your name, email, role and task activity are stored to operate the workspace. Passwords are stored only as salted hashes. Temporary passwords must be changed on first login. Sign-ins, failed attempts and admin changes are recorded in the activity log. Secure session cookies last up to eight hours; changing or resetting a password ends previous sessions. Owner initialization requires a private one-time invitation.
Storage and service providers
Records are stored in the website database, or Firebase when the owner connects it. If email is enabled, your request is sent through the configured mail provider. If AI is enabled, your chatbot question and public company information are sent to the configured Google Gemini service. Do not submit passwords, financial information or other sensitive personal information in the chatbot.
Retention and requests
Enquiries remain in the admin inbox until an authorized admin removes them. Provider logs and backups may have separate retention periods. To request a correction or deletion, use the contact form and include enough information to identify your request. Do not send identification documents unless the team explains why they are needed.
Cookies and security
MicroX uses essential secure session and request-verification cookies for workspace access and forms. This application does not add advertising trackers. Request limits, role permissions and encrypted integration settings help protect the service.
Contact MicroX