Privacy — CRÜ

This Privacy Policy applies to the Service, including CRÜ's website, app experience, community features, messaging, Happenings, organiser listings, support channels, and related services.

It should be read with our Terms & Conditions, Acceptable Use & Safety Rules, and any organiser or Happening listing terms that apply.

We collect information that is reasonably necessary to operate CRÜ safely and reliably.

Information you provide

• Account information, such as email, username, and login credentials through our authentication provider
• Profile details you choose to add, including prompts, interests, photos, connection context, and optional identity or community context
• Content you post or share, including posts, comments, profile text, photos, messages, chat requests, saves, replies, reactions, and soft responses
• Reports you submit, including any details you include
• Support requests you send to us
• Happening-related actions, such as saved listings, interest signals, or “I might go” style interactions where available
• Organiser listing information, where you submit or manage a Happening, including event details, organiser details, links, images, accessibility notes, safety notes, price information, and other listing context

Information collected automatically

• Cookies or local storage used to keep you signed in and keep the Service working
• Basic technical data, such as device type, browser type, app environment, IP address, and request metadata
• Usage data needed to operate, secure, and improve the Service, such as error logs, performance telemetry, and request IDs
• Basic security signals used to prevent abuse, such as rate-limiting, fraud prevention, and suspicious activity signals
• Broad location-ish or region context where you choose to provide it or where it is needed to make location-based features useful

We do not sell your personal information. We do not run third-party advertising on CRÜ.

CRÜ is designed primarily for queer community connection. Some information people choose to share may be sensitive, including sexuality, gender identity, pronouns, relationship context, community belonging, safety needs, accessibility needs, event interest, or social comfort.

Where possible, CRÜ treats this kind of information as optional and user-controlled.

How CRÜ uses profile and relevance information

CRÜ uses profile and relevance information to make the app feel less random and more useful. Some information can appear on a member’s profile. Some information stays private and only helps shape what feels more relevant inside CRÜ.

CRÜ does not require members to publicly define their identity in order to belong. Members can choose what they want to share, what they want kept private, and what they do not want used for relevance.

Profile information

Members may add profile information such as their display name, profile photo, short bio, interests, social style, conversation prompts, and what kind of connection they are open to. Some of this can appear on their member profile so other members can get a better sense of them.

Private relevance preferences

Members may also choose private preferences, such as what they would like to see more of, where CRÜ should feel relevant, and what kinds of posts, plans, conversations, or community spaces feel useful to them.

Private relevance preferences are not shown publicly on a member’s profile. They are there to help CRÜ feel more attuned, not to label someone publicly.

Optional identity nuance

CRÜ allows members to add optional identity-related context, such as identity words, gender words, romance comfort, and sex comfort. These fields are optional and can be controlled by the member.

Each group can be set to:

• Hidden, helps relevance: not shown on the profile, but may help CRÜ make the experience more relevant
• Shown on profile: visible to other members
• Do not use: hidden and not used for relevance

This means members can share different kinds of information in different ways. For example, someone may choose to show identity words on their profile, keep gender words private for relevance, and choose not to use sex comfort at all.

Location and area relevance

CRÜ may ask for broad “where-ish” information so the app can understand what feels locally or socially feasible. This can support local relevance, nearby plans, region-based discovery, and online or wider-community options.

CRÜ’s location approach is based on broad relevance, not exact tracking. Location preferences and location visibility are treated separately.

Content and activity signals

CRÜ may use activity signals such as posts, replies, saves, soft responses, follows, profile updates, and other in-app interactions to improve the experience. These signals help CRÜ understand what kinds of content may be useful, but they should not be treated as public identity labels.

CRÜ uses these signals to improve relevance, safety, trust, and community quality.

Privacy and visibility

CRÜ separates what a member shares publicly from what may help relevance privately. Sensitive profile fields are not shown publicly unless the member chooses to show them.

Member-visible profile routes should only expose information that is allowed to be public. Private relevance information and internal signals are not intended to be exposed to other members.

Relevance without identity segregation

CRÜ may use private preferences and optional profile context to make the app feel more relevant, but these signals should be used as soft guidance, not hard filters. CRÜ is designed to support identity-specific relevance without turning the community into separated identity lanes.

The goal is to help members feel seen while still keeping CRÜ connected as a broader queer community.

We aim to separate:

• what you choose to show publicly or to other members
• what is used privately to operate your account or improve relevance
• what is kept internally for safety, moderation, security, support, or legal reasons

CRÜ should never expose internal trust, moderation, seed, debug, raw relevance, exact location, or private social-context data as public profile or public listing information.

We use your information to:

• create and manage your account
• operate core features of CRÜ
• show posts, profiles, comments, messages, Happenings, and other product surfaces
• support safety, reporting, blocking, moderation, and abuse prevention
• respond to support, privacy, account access, account deletion, and Happening listing concerns
• help users understand community and event context without exposing unnecessary personal information
• improve reliability, security, accessibility, and performance
• comply with legal obligations

What you share on CRÜ may be visible to other users depending on the Service design, your settings, and your actions.

You control:

• what you post
• what profile details you choose to add
• whether and how you interact with others
• whether you save or express interest in a Happening, where that feature is available

CRÜ does not guarantee visibility, engagement, replies, attendance, or event outcomes.

CRÜ does not read private messages as a matter of course.

However, we may access or review content, messages, reports, or account activity where reasonably necessary to:

• enforce our Terms or Rules
• respond to reports or support requests
• protect users or the integrity of the Service
• investigate abuse, spam, scams, coercion, harassment, privacy breaches, or technical misuse
• comply with legal obligations

Happenings help users discover real-world community events and understand what kind of room they may be walking into.

CRÜ may collect and process Happening listing information, such as:

• event title, date, time, suburb or broad location, organiser name, and event link
• price, access, age, alcohol, noise, social energy, first-timer, and safety context where provided
• organiser-submitted images and listing text
• save, interest, or “I might go” style interactions where available
• reports or concerns about a listing or organiser

Happening interest signals are private by default unless CRÜ clearly says otherwise. CRÜ should not publicly show attendee lists or expose a user's event interest in a way that identifies them without a clear product reason and appropriate user control.

Organisers are responsible for the accuracy of event details they provide. CRÜ may review, edit, hide, remove, or decline listings to protect clarity, safety, privacy, trust, or legal compliance.

Tickets, refunds, venue entry, cancellations, event delivery, and organiser conduct are generally handled by the organiser, venue, or ticketing provider, not CRÜ.

CRÜ may use broad location-ish information to make community discovery and Happenings more useful.

CRÜ's location principle is connection feasibility, not precise tracking.

Where possible, we use broad regions, suburbs, state-level context, or user-controlled preferences rather than exact GPS-style information. Public surfaces should not expose raw latitude, longitude, geohash, exact location, or internal location precision.

CRÜ uses a combination of automated systems and human review to maintain a safer environment.

Information may be reviewed or acted upon where:

• content is reported
• behaviour appears harmful, abusive, coercive, discriminatory, fraudulent, or technically suspicious
• a Happening listing appears inaccurate, unsafe, misleading, discriminatory, impersonated, scam-like, stale, or privacy-invasive
• required to protect users or the platform

We take reasonable steps to protect your information, including:

• access controls
• encryption in transit and other security measures where appropriate
• secure infrastructure practices
• safe response contracts and user-facing data shaping where appropriate
• internal separation between public/member-visible data and private operational data

No system is completely secure, but we design CRÜ to minimise risk and exposure.

CRÜ relies on trusted third-party service providers, such as infrastructure, hosting, authentication, storage, logging, security, email/support, and related operational tools.

Some providers may process data outside Australia. Where that occurs, we take reasonable steps to use reputable providers and appropriate safeguards.

We retain information only for as long as reasonably necessary to:

• operate the Service
• enforce our Terms and Rules
• protect users and the integrity of the platform
• comply with legal obligations
• resolve disputes
• maintain safety, abuse-prevention, moderation, support, and audit records

Retention periods vary depending on the type of information.

For example:

• safety logs, reports, moderation records, and audit records may be retained longer to prevent repeated abuse or preserve evidence
• messages may be retained where needed for conversation continuity, recipient context, safety review, abuse handling, or legal reasons
• event listing reports and organiser-related records may be retained where needed for safety, trust, audit, or legal reasons
• technical logs may be retained for reliability, security, and incident diagnosis

You can request account deletion through the Service, including the account deletion settings page where available. If you cannot access your account, you can contact us for help.

CRÜ may apply a cooling-off period before processing deletion. During that period, you may be able to cancel the request.

After the cooling-off period, account data may be deleted, hidden, cleared, tombstoned, de-identified, or anonymised depending on the data type and the need to preserve safety, legal, abuse-prevention, moderation, audit, or recipient context.

For example:

• public/member-visible profile identity should be hidden or de-identified
• profile fields, photos, profile context, location-ish data, and notification tokens should be removed or anonymised where appropriate
• posts and comments may be hidden, tombstoned, detached from identity, or preserved in a deleted-user state depending on product and safety needs
• messages may be retained for the other participant's conversation context and safety record, but the deleted user's profile should not remain reachable
• reports and moderation records may be retained where needed for safety, abuse prevention, legal compliance, and audit integrity

Account deletion is not the same as hiding a profile, logging out, or deactivating temporarily.

See our Account Deletion page for more information.

You may:

• update your account information
• adjust visibility and interaction settings where available
• edit or remove profile information where available
• stop using CRÜ at any time
• request access to or correction of personal information we hold about you
• request account deletion

We may need to verify your identity before responding to access, correction, privacy, or deletion requests.

CRÜ uses trusted third-party services to operate.

These providers process data only as necessary to support CRÜ and are subject to their own privacy obligations.

The Service may also link to third-party event pages, venues, ticketing providers, social media pages, organiser websites, or other external services. Those third parties are responsible for their own privacy practices, terms, ticketing, refunds, venue entry, and event operations.

We may update this Privacy Policy from time to time.

If changes are material, we will take reasonable steps to notify users. Continued use of CRÜ after changes take effect constitutes acceptance of the updated policy.

If you have questions about privacy, data use, access, correction, account deletion, or a Happening listing privacy concern, contact us through the Service or on our Contact page (/contact).

You can also email support@cruspace.com.au and use the subject line “Privacy request”.

If you are not satisfied with our response, you may also be able to lodge a complaint with the Office of the Australian Information Commissioner (OAIC).