Privacy Policy

Girilang is operated by Corona Projects Pty Ltd (ABN 33 122 390 023) trading as Girilang. In this policy "Girilang", "we", "us" and "our" mean that company, which is the entity responsible for the personal information described here.

Girilang is an Australian property management platform for people who run their own rentals: self-managing landlords, owners, hands-on managers, and the tenants who live in their properties. It gives every property a working record: rooms, tenancies, leases, inspections, maintenance, keys, documents, and the dates attached to all of them.

The platform is available as a web app and an iPhone app. The tenancy agreement and notice rules built into it are those of New South Wales, though the platform is used by owners across Australia.

This policy explains what personal information we collect, why, how we protect it, and the rights you have over it. By creating an account or using Girilang, you agree to the handling described here. For any privacy enquiry, write to privacy@girilang.com.

Account information

When you create an account we collect your name, email address, an optional phone number, and an optional profile photo. Passwords are hashed by Firebase Authentication and are never stored in plain text or visible to us.

You may instead sign in with a Google, Apple, or Microsoft account, in which case we receive your name and email address from that provider. Changing the address you sign in with always requires confirmation from the new address, so the change only takes effect once you open the link we send there, so the old address keeps working until you do.

If you request a call from a demo, we collect your name, organisation name, email address, optional phone number, preferred contact time, and any message you provide. Girilang platform administrators use these details only to respond to your request and arrange the call.

Passkeys and biometric sign-in

If you set up a passkey, we store a public key, a credential identifier, the credential's transport methods and sign-in counter, and a general description of the device that created it (for example "iPhone" or "Mac") so you can recognise and revoke it later. Your fingerprint, face, device passcode, and the corresponding private key never leave your device and are never transmitted to or stored by Girilang. You can remove a passkey at any time from Account → Security.

Property, tenancy and contact records

Owners and managers enter property addresses, room configurations, and tenancy details, including tenant names, contact details, lease dates, bond amounts, and rent. You may also record other people as contacts: prospective tenants, co-owners, trades, and vendors. This information is held on your behalf, to deliver the service to you, and you are responsible for having collected it lawfully.

Financial information

We record the financial details you enter or import: rent amounts, invoices, payment statuses, expenses, and the transactions in any bank statement you upload. This is your own tenancy data, and Girilang neither processes nor holds rent or bond money.

Your subscription to Girilang is billed through Stripe, a PCI-compliant payment provider. Starting a free trial requires a payment method. Card details are entered into Stripe-hosted secure fields and never reach our servers: we receive and store only the card type, its last four digits and its expiry, so you can recognise which card is on file. To prevent repeated free-trial use, we also store a one-way hash of Stripe's card fingerprint and associate it with the account that claimed the trial. Stripe holds the card itself, issues your invoices, and acts as an independent controller of that information under its own privacy policy.

Signatures and signed documents

When you sign a document through the platform, we capture your electronic signature as a digital image together with a timestamp, IP address, and device information. These details form the audit trail attached to each signed document, and are what make it admissible evidence of the signing act. If an agreement is later revised and re-sent, the superseded terms and the signatures collected against them are both kept, because a signature attests to the document a party was actually shown.

Photos, video and other media

Users upload photographs and video in connection with inspections and condition reports, maintenance jobs, room and property records, and listing material, and may place images in a lease they write. Images are downscaled on your device before upload, stored privately, and served only to signed-in users your organisation's permissions allow. They are never given a public link. An image placed in a lease is embedded in that agreement, so the people asked to sign it see it on the signing page and in the signed copy.

On iPhone you can also report a maintenance issue by sharing photos to Girilang from the Photos app or another app. Only the photos you choose to share are read. They are downscaled on your device and uploaded under your own signed-in account, exactly as if you had taken them inside the app; nothing is sent until you create the issue.

Inspections, maintenance and communications

Inspection findings, condition report entries, maintenance job descriptions, status changes, vendor details, notes, and the messages and notifications sent through the platform are stored so the property has a continuous history rather than a set of disconnected events.

Each organisation also has an email address of its own on giri.email, and can add more. These addresses receive mail and never send it: an organisation can forward its own business mailbox to one, and some replies to the email it sends arrive at them. Mail sent or forwarded to these addresses, such as a tenant's reply or an enquiry from somebody the organisation has not dealt with before, is received by our email provider, Resend, which keeps a copy in Tokyo, Japan. It is then stored, with its attachments, in the organisation's inbox in Girilang. We process that mail on the organisation's behalf: we match the sender to the organisation's tenant, contact and vendor records, check whether the message was authenticated as coming from the sender's domain (SPF, DKIM and DMARC) and mark it when it was not, and file it under any of the organisation's buildings it names.

Personal mailboxes

If you are on an organisation's team, you can connect your own Google (Gmail) or Microsoft (Outlook) mailbox in the web app, at Account → Email accounts, to read your email beside your work and to send the email you write in Girilang from your own address. This is optional, and nothing is connected until you do it yourself. Girilang asks Google for the gmail.readonly and gmail.send permissions, and Microsoft for Mail.Read, Mail.Send, Mail.ReadWrite, User.Read and offline_access, and besides your mail it reads only your account's email address and identifier. Girilang sends email from your mailbox only once you allow it to, and then only the email you send in Girilang and, if your organisation's owner chooses your mailbox for it, your organisation's own mail, such as lease invitations and invoices. On Microsoft, Girilang uses Mail.ReadWrite only to create each message you send from Girilang as a draft, add its attachments and send it, and to delete that draft if it cannot be sent. It never deletes or changes the mail already in your mailbox. Your provider keeps a copy of everything sent from your mailbox in your Sent folder, your organisation's mail included, and removing the mailbox from Girilang does not delete those copies.

Girilang copies the latest 100 messages in your Inbox and in your Sent folder, and the latest 100 from any Gmail labels or Outlook folders you choose. It keeps the copy up to date: who each message is from and to, its date, its subject and text, and the name, type and size of each attachment. You can ask it to keep only the mail that matches filters you set, such as mail from your organisation's tenants or naming one of its buildings. An attachment itself is fetched from your provider only when someone with access opens it. Email Girilang sent from your mailbox is kept in the conversation it belongs to rather than in this copy. The copy is stored with the rest of your Girilang data in Sydney, and the tokens that grant Girilang access are encrypted before they are stored, with a key held separately in a secrets manager.

The copy belongs to you rather than your organisation, and is private to you. Girilang compares the addresses, subject and text of your mail with your organisation's tenant, contact and vendor records and its buildings, and shows you which records a message concerns; those matches are shown to you alone. A reply to an email sent through Girilang joins the conversation it answers, where your team can read it. That includes a reply to your organisation's mail sent from your mailbox, and your own answer to it written in Gmail or Outlook. Anything else reaches your colleagues only if you share it: with the Share action, by applying a Gmail label or Outlook category you have chosen for sharing, or by mentioning a colleague on the message. You can withdraw a share for ten minutes, unless a colleague has already answered it. A message you share, or a reply that joins a conversation, is copied into the organisation and stays with it after you remove the mailbox. It is kept until somebody in your organisation deletes the conversation. You can also share the mailbox itself with your organisation's team, showing who each message is from and to and when, the subjects as well, or everything, and give individual colleagues full access.

Removing a mailbox deletes Girilang's copy of its mail and the stored tokens, which ends Girilang's access, and stops your organisation's mail being sent from it. For a Google account, Girilang also asks Google to revoke that access, unless someone else still has the same account connected. Microsoft offers no way for an app to withdraw only its own access, so you may also want to remove Girilang from your Microsoft account's app permissions. If you close your account, the mailbox stops updating during the 60 days before deletion and is removed at the end of them.

Mail and account details Girilang receives through a mailbox connection are used only to show you your mailbox, to send the email you send from it, to link it to your organisation's records in your own view, and to put in your organisation what you share and the replies that answer its email. They are never used for advertising, never used to train AI models and never sold, and nobody at Girilang reads them unless you agree to it for particular messages, it is needed for security, such as investigating abuse, or the law requires it. Girilang's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Documents

Lease agreements, condition reports, house rules, disclosure statements, and other documents you upload or generate are stored with access controls that restrict visibility to authorised parties.

Support enquiries

When you submit the support form on our website, which you may do without an account, we collect your name, email address, any organisation name you supply, and the topic, subject, and content of your message. The enquiry is stored so we can track and answer it, and a copy is emailed to our support team with your address set as the reply-to address. To stop the form being used to flood our inbox, we also record a one-way cryptographic hash of your email address and of your network address together with a submission count; neither underlying address is stored or written to our logs.

Feature requests

When you suggest a feature, from the request form on our website (which needs no account) or from inside the app, we collect your name, email address, any organisation name you supply, and your message. If you are signed in, the request is linked to your account. Requests are stored for our team to read and triage; they are not emailed anywhere. To stop the form being used to flood us, we record a one-way cryptographic hash of your network address together with a submission count; the address itself is not stored or written to our logs.

Location information

Some features can use your device's location: on the web, suggesting the nearest property on the Keys page; in the iPhone app, showing the access codes of a property you are standing at and suggesting an inspection of the house you have arrived at. This is off until you turn it on, and the browser or operating system asks separately before granting it. The iPhone app offers once, after you first sign in on a device, to ask for this permission; declining changes nothing else. It asks only for access while the app is in use, never in the background.

Your coordinates are compared with your organisation's property locations on your device, and are never transmitted to or stored on our servers. The maps in the iPhone app are drawn by Apple Maps, which is described under “Service providers” below. You can withdraw the permission at any time from Account → Privacy, or in your browser or device settings.

Device and security identifiers

To protect the platform against automated misuse and fraudulent access, we use device attestation technology that collects limited device and application identifiers. This is processed solely for security and is never used for advertising.

Push notifications

If you allow notifications in the iPhone app, we store a push token for that installation (the address Apple's notification service delivers to), together with the app version and when it was last registered. We use it only to send the notifications you have chosen in Account → Notifications, which today are about maintenance issues. The token is removed when you sign out on that device, and deleted with your account. You can turn notifications off at any time in the app or in your device settings.

Usage and technical data

We automatically collect limited technical data when you use the platform: device type, browser type, IP addresses recorded in activity and audit logs, and interaction logs. This is used to keep the platform reliable, diagnose errors, provide the audit trail described above, and improve the service.

How you found us

The first time you visit our website, your browser keeps a note of how you arrived: the campaign tags in the link you followed, the website that sent you (its name only, never the full address), the page you landed on, and whether you came from one of our ads. For an ad we note only that an ad click brought you, never the ad's own identifier. The note stays in your browser and is not replaced by later visits.

If you create an account, we attach the note to it, once, so we can tell which of our marketing brings people to Girilang, and remove it from your browser. It is visible only to Girilang platform administrators, is never attached to an account made more than two hours earlier, and is deleted with your account.

Our notes about account holders

Our staff keep notes, records of calls and meetings, and follow-up stages about account holders, so we can support them and sell them the service. They are visible only to Girilang platform administrators and are deleted with your account.

Sign-in records

Each time you sign in we record the date and time, the sign-in method used, the IP address the request came from, a description of the device and browser, and an approximate location (city and region) resolved from that IP address by a third-party geolocation lookup. We keep the twenty most recent sign-ins for your account and delete older ones automatically.

This is a security record. It lets us and you tell an ordinary sign-in from an unfamiliar one, and it is what we look at when an account is reported as compromised. It is visible only to Girilang platform administrators, and you may request a copy of your own records under “Access and correction” below.

Account security activity

We also record changes to how your account signs in: confirming your email address, requesting or completing a password reset, changing your password or sign-in address, and adding or removing a passkey. Each record holds the date and time, the IP address, a description of the device and browser, and an approximate location resolved from that IP address. We keep the hundred most recent for your account and delete them with it.

Emails we send you

The emails Girilang sends to your account — confirmations, password resets, billing, storage and deletion notices, team invitations and similar — carry a small image that tells us when the email is opened. Each time it loads we record the date and time, the IP address, a description of the device and an approximate location. Some mail apps load images automatically, and some route them through their own servers, so this shows that an email was probably delivered and read rather than proving it. You can stop it by turning off remote images in your mail app. We keep these records for about thirteen months and delete them with your account. Emails your property manager sends you through Girilang carry no such image.

If you hold an account, we may also email you about it and about your trial: help getting set up, a note before your trial ends, or news about Girilang. Each one is sent to you alone, carries the image described above, and has an unsubscribe link. One press stops them for good, for that email address, including for any account you open with it later. It does not stop the emails your account needs, such as billing notices and password resets.

We use personal information to:

• Provide, operate, secure and improve the Girilang platform.
• Send transactional messages such as lease signing invitations and reminders, rent and maintenance updates, invitations to join an organisation, and security notices such as password resets.
• Email account holders about their account and trial, with an unsubscribe link in every such email, and learn which of our marketing brings people to Girilang.
• Receive the email sent or forwarded to your organisation’s giri.email addresses and file it in the organisation’s inbox, send the email you write in Girilang from a mailbox you connect, and show the mail in that mailbox to you and to any colleagues you share it with.
• Let owners, managers and tenants collaborate on the properties they share.
• Generate lease documents, condition reports and other records on your behalf.
• Maintain the audit trail behind signed documents and consequential administrative actions.
• Draft listing and marketing copy from details you supply. This runs on our own servers from a template. Your data is not sent to a third-party AI service and is not used to train anyone’s model.
• Meet our obligations under applicable Australian law, including privacy, tax and consumer law.
• Answer support enquiries, triage feature requests, and resolve technical problems.
• Authenticate you, verify registered passkeys, and detect and prevent fraud, spam and automated abuse of our sign-in, public support and feature-request forms.

We do not sell, rent, or trade your personal information, and we do not use it for third-party advertising. We use what we know about an account holder — how they found us, how far they have set up, and our notes — to follow up on their trial and account, with an unsubscribe link in every such email. Girilang does not publish rental listings, screen tenants, or operate a rental marketplace, so your property and tenancy records are never surfaced to the public.

We share personal information only in the following circumstances.

Within your organisation

Owners, managers and tenants in the same organisation can see the information their role allows. Access is enforced by role-based security rules on the server, not only in the interface, and an organisation's owner controls who is invited and when access is revoked. A personal mailbox is the exception: it is private to the person who connected it, and colleagues see only what that person chooses to share and the replies that answer the organisation's email.

Parties to a document

When a lease or other agreement is sent for signing, the names and email addresses of the signatories are visible to the manager and to the other parties to that document, as the execution process requires.

Service providers

Google Firebase and Google Cloud provide authentication, database, file storage and server-side functions; Google, Apple and Microsoft process information when you choose their sign-in services, and send and deliver the email sent from a Gmail or Outlook mailbox you connect; Resend sends the email we send, and your organisation's email when it is not sent from a connected mailbox, and receives the mail addressed or forwarded to giri.email, from its Tokyo region in Japan; ipapi.co resolves the approximate location on a sign-in, account activity or email-open record from its IP address, and is sent nothing else; Firebase Cloud Messaging and Apple's push notification service deliver notifications to the iPhone app; Apple Maps draws the maps in the iPhone app and places your organisation's property addresses on them; Google Analytics, Ahrefs Web Analytics and PostHog measure use of our website, and PostHog measures use of the app; and Google Ads measures which of our ads lead to a trial, as described below. Each processes information under its own terms and on our instructions, and we require protections consistent with this policy and with Australian privacy law.

Optional integrations

You can connect a personal Google or Microsoft mailbox, as described under “Personal mailboxes” above. It is off until you connect it yourself. It brings a copy of your mail into Girilang, and the only thing Girilang sends Google and Microsoft from your records is the email sent from your mailbox. If we add an integration that shares your records with another service, accounting software for instance, it will be off by default, and nothing will be shared until you connect it yourself.

Legal requirements

We may disclose information where required by law, regulation or valid legal process, or where necessary to protect the rights, property or safety of Girilang, our users, or the public.

Business transfers

If Girilang is acquired or merges with another entity, your information may transfer as part of that transaction. We will notify registered users before any such transfer, and before information becomes subject to a different privacy policy.

Your records and uploaded files are stored on Google Cloud infrastructure in Sydney, Australia. Our server-side functions and the web app's server routes run in the same Australian region, so day-to-day processing of your records stays onshore. Your sign-in account (your email address, your name and, if you use one, your hashed password) is held by Firebase Authentication, which Google runs on global infrastructure, so it may be processed outside Australia. Email is processed in Japan: Resend sends and receives it from its Tokyo region and keeps a copy there. That covers the email we and your organisation send, and the mail that arrives at your organisation's giri.email addresses, attachments included. Some of our other providers also operate globally, notably the identity providers you may choose to sign in with, and information handled by them may be processed overseas under their own privacy commitments.

Data is encrypted in transit and at rest. Access is governed by role-based security rules evaluated on the server for every read and write, so an authorisation check cannot be bypassed by the client. Private files, signed leases, signature images, inspection and maintenance photos, are never given a permanent public link; each request is authorised against your own session before the bytes are returned.

Consequential administrative actions on the platform are written to an append-only audit log that no user can edit or delete.

No internet-based service can be guaranteed completely secure. If you find a vulnerability or suspect a breach, please tell us at security@girilang.com. We will investigate promptly, and where a data breach is likely to result in serious harm we will notify affected individuals and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires.

Under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, you may:

Access your information

Ask for a copy of the personal information we hold about you. Much of it is already visible in the app, and the iPhone app can export your account profile and sign-in details as a file from Account → Privacy. Organisation, property and tenancy records are not part of that file. For anything else, write to privacy@girilang.com.

Correct your information

Update anything inaccurate, incomplete or out of date. Your own profile, contact details and sign-in address can be changed at any time from Account.

Delete your account

You can delete your account yourself at Account → Security → Delete account, in the web app or the iPhone app. Your account closes straight away and is permanently deleted 60 days later; nothing is destroyed before then, and you can restore it at any point in between from the link in the email we send you. At the end of that period we remove your sign-in credentials, your profile, your personal files, your sign-in history, any personal mailbox you connected and Girilang's copy of its mail, and your membership of every organisation. A connected mailbox stops updating in the meantime. Your name is replaced with an anonymous marker in administrative logs rather than those logs being deleted.

Records owned by an organisation, such as properties, tenancies, signed leases and financial records, belong to that organisation and are retained under the retention clause below. If you own an organisation you must either transfer ownership to another member first, so its records do not become unreachable, or choose to close the organisation alongside your account.

Delete your organisation

An organisation owner can close the whole workspace at Organisation → Delete organisation. We build you an archive of everything first — properties, rooms, tenancies, contacts and financials as spreadsheets, plus every signed lease and uploaded image — and the 60 days do not begin until it is ready. Everyone with a seat is emailed when it is scheduled, again a week beforehand, and once more when it is done. At the end, every property, room, contact, application, photograph and document is permanently deleted, along with the workspace itself. Tenancy, lease and financial records are sealed instead, and destroyed individually as the retention period for each expires.

Control optional collection

Location sharing and iPhone notifications are off until you enable them, and a personal mailbox until you connect one. Each can be turned off again at any time, and removing a mailbox deletes Girilang's copy of its mail. Analytics can be switched off in your browser as described below. None of these affects your ability to use the platform.

Complain

Raise a complaint about how we have handled your personal information with us at privacy@girilang.com. If you are not satisfied with our response, you can escalate it to the Office of the Australian Information Commissioner at oaic.gov.au.

We acknowledge requests promptly and respond within 30 days. Where the information you are asking about was entered by an organisation you belong to rather than by us, we will tell you so and, where we can, put you in touch with the right person there.

We keep personal information for as long as your account is active or as needed to provide the service. Specific periods by type:

• Tenancy records, signed leases and financial records: kept up to seven years after the end of the relevant tenancy, to satisfy Australian tax and tenancy record-keeping obligations, including after an individual account is closed.
• Archived properties: retained for 30 days, together with their rooms, documents and media, then permanently and irreversibly deleted.
• Closed accounts and organisations: archived for 60 days, during which the deletion can be reversed, then permanently deleted along with every stored file and image. Tenancy, lease and financial records are the exception — they are sealed at that point, unreachable by anyone including us, and destroyed as the retention period above expires for each one.
• Demo workspaces: cleared automatically, usually within a day. The record that somebody requested a demo — a name, organisation and email address — is kept for 24 months as a sales enquiry.
• Inspections, condition reports and maintenance records: kept for the duration of the tenancy and any further period applicable legislation requires.
• Email in your organisation’s inbox: kept until someone in your organisation deletes the conversation, then permanently deleted, with its attachments, 30 days later. Anything still in the inbox is deleted with the organisation.
• Personal mailboxes: the latest 100 messages in each of Inbox and Sent, and the latest 100 from the labels or folders you choose, kept while the mailbox is connected and deleted when it is removed. If you close your account, they are kept, no longer updated, until the 60 days are up, then deleted. A message you shared, or a reply that joined a conversation, is the organisation’s email from then on, and is kept like the rest of its inbox.
• Audit logs for signed documents and administrative actions: retained indefinitely; they are the record of what was done and by whom, and are deliberately not deletable.
• Unsubscribes from our emails about your account and trial: kept after your account is closed, as a one-way hash of the email address and nothing else, so we never send that address those emails again.
• Passkey credentials: kept until you remove the passkey or delete your account, whichever comes first.
• Push notification tokens: kept until you sign out on that device, the token stops working, or you delete your account.
• Support enquiries: kept up to two years, so we can refer back to your support history. The hashed identifiers behind rate limiting are counters only, and reset when the limiting window expires.
• Feature requests: kept up to two years, so we can see what has been asked for over time. The same rule applies to the hashed identifiers behind their rate limiting.
• Usage and technical logs: kept up to 90 days for diagnostics, then deleted.

When information is no longer required, it is deleted from our systems and from our service providers' systems under our data processing arrangements with them.

Girilang uses cookies and browser local storage to keep you signed in and to remember application preferences such as your theme. These are required for the platform to work and cannot be switched off while you are using it.

Our website also keeps one note in your browser's local storage: how you first arrived, described under "How you found us" above, so we can tell which of our marketing works. It is not required, and the site works the same if your browser refuses or clears it. It has no expiry of its own: it stays until it is attached to an account you create, when it is removed, or until you clear your browser's storage. A later visit starts a new one.

We use Google Analytics on girilang.com to understand which pages people visit and how the platform is used. This sets cookies and sends Google the page address, a randomly generated identifier, and general device and approximate location information. Google Signals and advertising personalisation are switched off, so the data is not used to build advertising profiles. Page addresses are stripped of private identifiers before they are sent, so signing links, invitation links and sign-in codes never reach Google. You can opt out entirely with the Google Analytics opt-out browser add-on, or through your browser's cookie controls.

We advertise on Google Search, and use Google Ads to see which of our ads lead people to start a trial. When you arrive by clicking one of those ads, the page address carries an identifier for that click, and Google Analytics records it with your visit. If you then start a trial, Google Analytics tells Google Ads that the click led to one, along with how that visit used our public pages, so we can see which ads work and what each trial cost. Visits that never came from one of our ads are not reported to Google Ads. It is never sent your name, email address, phone number or anything from your account, and what it is sent measures our own ads only: it is not used to choose the ads you see, on our site or anywhere else.

We also use Ahrefs Web Analytics to see how our public pages perform in search. It runs on those public pages only and is never loaded inside the app, it sets no cookies and stores no identifier on your device, and it is sent the page address, the page title, the address of the page you arrived from, your browser language and your screen size. As with any request to another service, Ahrefs also sees the IP address your browser connects from, which it uses to derive an approximate location. Page addresses are redacted in the same way as above.

We also use PostHog, hosted in the European Union, to see how visitors move from our website to starting a trial, and how the app is used once they are in it. It stores a randomly generated identifier in your browser and is sent the same redacted page addresses and the same sign-up and trial steps as Google Analytics. Inside the app it is also sent which pages you open and when you leave them, where on a page you click, and a session recording. A recording shows the layout of each screen and where the pointer moved and clicked, with every field you type in and every picture hidden before it leaves your browser. On our public website it also shows the words we wrote on the page; inside the app every word is hidden too, including labels, tooltips, image descriptions and link addresses that are not drawn on the screen, so it never contains the names, addresses, amounts or documents you see. Page titles inside the app are not sent, and link addresses are redacted in the same way as page addresses. Once you sign in, it is also sent your account's internal identifier and role, so a visit can be connected to the account it created. It is also told when your account reaches a few first steps — adding a property or a tenant record, sending a lease, and a lease being fully signed — by name only, with nothing about the property, the people or the agreement. When something in the app goes wrong, it is also sent an error report: the technical error message and where in our code it happened. Before a report leaves your browser, email addresses, phone numbers, long numbers, quoted text, record identifiers and the query part of any web address are removed from it. Beyond that, it is never sent your name, email address or anything you type, and it is never loaded on signing, invitation, application or condition report links.

Measuring our own ads is the only advertising use we make of this information. We use no third-party advertising cookies, run no retargeting, and share nothing with other advertisers or ad networks.

Girilang is intended for adults aged 18 and over. We do not knowingly collect personal information from anyone under 18. If you believe a minor has given us personal information, contact us and we will delete it promptly.

We may update this policy from time to time. When we do, we revise the "last updated" date at the top of this page. Where a change is material, a new category of information, a new purpose, or a new recipient, we will notify registered users by email before it takes effect. Continuing to use the platform after that date means you accept the updated policy.

Privacy questions, access requests and complaints go to privacy@girilang.com. Security reports go to security@girilang.com. Anything else reaches us at support@girilang.com.

Please do not send passwords, access codes or full identity documents to any of our inboxes.