1. Who is responsible
ReEvent is operated by LIEW KAIY BIN (“ReEvent”, “we”, “us”). For privacy questions, access requests, corrections, or deletion requests, email benliew28262826@gmail.com. You may submit a request at any time; we aim to respond within 24 hours.
2. Information we handle
We handle account information: email address, authentication identifier, display name where supplied, sign-in method, and the fixed ReEvent role assigned to the account. We also handle the event, resource, programme, handover, impact, and uploaded-photo information that you create or are authorised to see.
The app may keep authorised working data on your device for offline use and synchronise it with the ReEvent cloud service when a connection is available. When you contact support, we handle the information you choose to include, such as your account email, app version, device details, and screenshots.
3. Camera, location, and QR scanning
The camera is requested only when you choose to take a resource photo or scan a QR code. Resource photos are uploaded to private ReEvent storage for the authorised workflow. QR recognition uses an on-device barcode model; ReEvent does not upload the camera stream for QR recognition.
Approximate location is optional and requested only when you use nearby discovery. The current device coordinate is used to find nearby programmes and is not stored as a location history. Locations, addresses, and coordinates that an authorised user deliberately adds to an event, resource, or programme are service records and are stored with that record.
4. Why we use information
We use information to create and secure accounts, keep organiser, participant, and partner workspaces separate, coordinate circular event-resource exchanges, synchronise offline work, prevent misuse, provide support, investigate reports, and keep the service reliable.
5. Service providers
ReEvent uses Supabase for authentication, database, private file storage, and server functions. The current ReEvent Supabase project is hosted in the Seoul, South Korea region. If you choose Google sign-in, Google processes the sign-in flow and provides the basic identity information needed to create or access your ReEvent account. ReEvent does not request Google Drive, Calendar, or contact access.
ReEvent uses MapLibre to render maps and MapTiler for map tiles and authorised geocoding. MapTiler may receive a map or geocoding request and network information such as IP address as part of providing that service. Map screens show the applicable map attribution.
6. Sharing, advertising, and security
Information is available only according to the role and permissions assigned to an account. We do not sell personal information, run behavioural advertising, or send marketing messages at present. We may disclose information to the providers above, when required by law, or where necessary to protect people and the service.
We use authentication, server-side Row Level Security, private storage paths, and role-based application boundaries. No online service can guarantee absolute security.
7. Retention and account deletion
We keep account and service data for as long as needed to operate ReEvent, maintain security, resolve disputes, and meet legal obligations. If an eligible account is deleted, its sign-in access and private account media are removed. Completed event, resource, programme, and handover records are retained as operational history; we do not promise that those completed records will be erased. Where feasible, direct association with the deleted account is removed or de-identified while preserving the record history.
Active transactions, resources, listings, programmes, or unsettled holds must be resolved before account deletion. See Delete account and data for the process.
8. Your choices
You may ask to access or correct your personal information, withdraw optional location permission in device settings, or request account deletion. Contact benliew28262826@gmail.com or see the Support page. A Bahasa Malaysia version of this notice is available at Notis Privasi Bahasa Malaysia.
9. Changes to this notice
We may update this notice when ReEvent changes. We will publish the updated version here with a new date before material changes take effect where required.