The website code includes no analytics or advertising trackers, sign-in form or location request. Email links open your email application; no message is sent automatically. Our hosting provider processes technical request information to deliver these pages. The Hoodlo app policy follows below.
1 Our privacy commitment and contact
Jasply Pty Ltd (ABN 99 702 948 687; ABN active from 19 October 2026) operates Hoodlo. Hoodlo accounts are for adults aged 18 and over. This Policy describes information handling by Hoodlo; outside navigation, map and app-store services have their own privacy policies.
Privacy requests, access, correction, account deletion and complaints: admin@jasply.com. Acknowledging this Policy is not blanket consent to marketing, sensitive-information processing or unrelated tracking.
We collect your date of birth during account creation to check the minimum age requirement. Your date of birth and mobile number are private account information and are not displayed on your public profile. A stated birth date and SMS verification do not independently prove age or identity. No additional age-bracket posting restrictions are introduced by this version.
2 Information we collect
Account information includes email, your mobile number and verification status when provided, display name, avatar, membership and trust information, authentication and security records, and the document version and time of your legal acceptance. Authentication credentials are handled by our authentication provider. Do not send your password or authenticator code to support.
When you use reporting and community features we collect the information you submit: categories, descriptions, incident coordinates, observation information, comments, replies, reactions, confirmations, reports to moderators and uploaded media. Device location and, where applicable, the photo capture location and time support proximity, authenticity and placement checks. Uploaded originals may contain identifying details and location metadata.
Saved and followed items, fuel choices, map and hood preferences, notification preferences and push delivery tokens may be used to provide the features you choose. Technical request, security, moderation and administrative audit records help operate and protect the service.
Optional organisation and drone-pilot features may collect representative details, contact information, aircraft details, qualifications, insurance and verification documents, flight schedules and media. These are collected when you apply for or use those features, rather than being required for ordinary browsing.
3 Location, permissions and choices
With device permission, live device location is used for your map position, nearby results, distance and reporting or participation checks. Location updates while the app is in use can move your marker. A device permission does not authorise unrelated tracking. This Policy does not state that Hoodlo records your journeys or shares your live position publicly by default.
You can manage location, camera, photo and notification permissions through your device and the preferences available in Profile. You may browse available information without granting every permission, but features requiring precise location or media will be limited. Incident coordinates you publish can be public even if you keep your own location private.
4 How information is used
We use information to create and secure accounts; show relevant alerts, facilities, fuel and other information; publish and maintain your contributions; calculate eligibility and trust indicators; deliver chosen notifications; administer optional organisations and flights; investigate reports and complaints; maintain records of acceptance; and comply with legal obligations.
We do not treat a Terms checkbox as permission for unrelated marketing. Any optional use requiring separate consent must be presented separately. Avoid submitting sensitive medical, victim or child information that is unnecessary for the report. Where sensitive information is necessary, an appropriate collection basis or separate consent is required.
5 What other people can see
Public posts can display their content, incident location, category, timestamps, media, displayed author name and avatar, trust information, comments and reactions. Published organisation profiles and flight listings expose their designated public details. A display name or photo may identify you. Other people can copy public material beyond our control.
Account email, authentication secrets and private verification documents are not intended as public profile fields. Authorised administrators and service providers may access information needed for their duties. Media may require review or processing, but you must not assume that every image has been automatically blurred or stripped of all identifying metadata. Check what you upload.
6 Service providers, disclosures and overseas handling
Hoodlo uses Supabase for authentication, database and storage services, Google Maps for map features, Expo for app build and related delivery services, and Cloudflare for website and configured media services. Providers receive information necessary for the services being used. Opening external directions sends the chosen destination to the navigation provider. Your device, network and app store may also process information under their own policies.
When SMS verification is used, Supabase and our SMS delivery provider Twilio process your mobile number, verification message and delivery information to send and check the code. Telecommunications carriers and routing providers also process information needed to deliver the message. This may involve processing in the United States and other countries used for message routing or support. Twilio’s privacy information is available at twilio.com/en-us/legal/privacy. Your mobile number is not displayed on your public Hoodlo profile. Verification messages are for account security and are not consent to marketing.
If automated moderation or verification processing is enabled for a feature, the applicable notice must explain that processing and the provider before additional information is sent. Human review and technical checks do not establish that content is accurate or lawful. Do not assume that every post is automatically scanned.
Hoodlo’s primary Supabase project is hosted in Tokyo, Japan (region ap-northeast-1, checked 16 October 2026). Database hosting in Japan does not mean that every provider or every support and delivery operation stays in that country. Providers may also process information in the United States and other countries in which they operate their infrastructure or support services. Current provider information is available at supabase.com/privacy, expo.dev/privacy and expo.dev/privacy/subprocessors, cloudflare.com/privacypolicy, and policies.google.com/privacy. These distributed services do not provide an Australian-only storage guarantee. We will update this Policy when a material change to known overseas handling occurs.
We may disclose relevant information to authorised representatives, advisers, insurers or authorities where needed to resolve a complaint, protect rights or safety, or comply with a lawful obligation. Requests are considered against applicable law; a complaint alone does not make an entire private account public.
7 Storage, security and retention
We use access controls, authenticated requests, private storage where applicable and secure session storage on supported devices. No system can guarantee absolute security. Tell us promptly if you suspect a compromised account or inappropriate disclosure.
We retain information while reasonably needed to provide the service, manage disputes, security, moderation and legal obligations. Different records have different needs: expiring a map alert does not necessarily delete the underlying post, audit record or backup. We must not retain personal information merely because storage is available. Information no longer needed should be deleted or de-identified, subject to lawful retention and backup processes.
Account closure or deletion requests are reviewed with identity verification proportionate to the request. We explain any information that must be retained and why. We cannot remove copies independently made by other people. We will explain any applicable retention period and lawful limitation when responding to your request.
8 Access, correction, deletion and complaints
Use the privacy contact in section 1 to request access to or correction of your personal information, request account closure/deletion, or complain about handling. Describe the request without sending unnecessary sensitive evidence. We may ask for reasonable identity verification and will explain any lawful refusal or limitation.
We aim to acknowledge privacy complaints promptly and respond within a reasonable time, ordinarily within 30 days. If more time is needed, we will explain why. If you remain dissatisfied, you may contact the Office of the Australian Information Commissioner at oaic.gov.au. Nothing in this Policy removes rights or complaint avenues available under applicable law.
9 Changes to this Policy
The published version and effective date appear with this Policy. Material changes are explained through an appropriate notice. Earlier acceptance records retain the version acknowledged; a document change does not create retrospective consent. Additional consent will be requested where required.