Your choice. Your pace.

Introductions

You are welcome whether you are single or in a relationship. We do not judge your relationship status; what matters is consent and respect between adults.

Members must be 18+. Verify your email, complete your profile, choose a WA postcode, upload at least one photo clearly showing your face and submit it for administrator approval.

Accounts created in Friendly Introductions are also able to login at Discreet Introductions with the same credentials.

Friendly Introductions is for friendship. Members who select Friendship on Discreet Introductions can cross-match with compatible members on Friendly Introductions, subject to both people’s preferences, availability, hides, blocks and sister-site opt-outs.

Anyone who is not a woman cannot initiate conversations with a woman.

You need a profile photo clearly showing your face before initiating a conversation with another member. You can contact Admin before approval.

Your shared nickname, age, postcode, gender, profile text and photos can be shown to others when you match. Private matching choices stay private.

Your account records which site it was created on, and which site is your main site. Under My profile you can change your main site and tick the option to stop matching with people whose main account is on the other site. If either person opts out, you will not be introduced across different main sites. This preference applies on both websites; existing conversations remain open.

Photos and conversations

At least one profile photo must clearly show your face. Administrators can view account details, private matching fields and profile photos for approval, support and account administration. Passwords and authentication secrets are protected in the Admin interface. The face photo accepted for approval must be retained until an administrator approves a replacement. Public photos can be seen by approved members who can view your profile. After you send ten messages to one person, all your private profile photos become accessible to that person, including any future additions. Previously viewed photos cannot be recalled. This counts messages you send, not the combined conversation. Blocking or hiding prevents further contact and photo access. Hiding is mutual and can be undone under Hidden people. Unavailable profiles are excluded from Discover and new introductions; existing conversations remain open.

Profiles and profile photos must contain no sexually explicit content. Private messaging is text-only. Conversations are not routinely monitored. Reports can be reviewed against retained messages; upheld abuse results in a permanent ban. Scams, impersonation, and non-consensual material should also be reported to police.

Optional mutual verification

Checks are in person against a WA driver’s licence and face, with phone and email ownership checked by the administrator. This is not a background check or assurance of safety. The requester is checked first, free. Once approved, the other participant can pay by bank transfer and complete their check. In a woman/non-woman pairing the woman is the requester. For other pairings, agree who requests and who pays.

Both consent before disclosure. After both pass, each can view the other’s preferred first name, verified surname, phone number, and email. Legal document details are not shared with the other member. Verification does not restrict your conversations or prevent exchanging contact details yourself.

Optional meeting records

Both participants accept the details, and the administrator confirms the bank transfer before the service is active. The deadline is two hours after the scheduled end, Perth time. Each participant must independently mark themselves safe. If either does not, the administrator sees an overdue alert for human review. This service does not notify police, provide emergency monitoring, or guarantee an administrator response. In an emergency call 000.

Data handling

New accounts confirm inbox access using a six-digit email code. This is separate from authenticator two-factor authentication and in-person identity verification. Under Account security, you can opt into emails about new matching profiles and unread member messages. Member notification emails contain no profile names, private matching answers or chat text. Operational emails to administrators can include account identifiers, email addresses, aliases, creation details and login dates for account administration. Notification settings are shared across the sister sites; matching notifications use the site where those choices were last saved.

Cloudflare proxies the public sites and handles connection information to deliver and protect the service. Outgoing email is delivered through the configured Microsoft 365 relay using the shared mail service. Profile approval and site-wide safety rules apply to both sites. There is no fee for profiles, introductions or member messaging; optional paid identity and meeting services are separate.

Verification contact records are held on a separate system. This application does not collect or store copies of identity documents. If the administrator keeps document copies outside the application, they are deleted after three months unless a complaint is outstanding. Verification contact details expire twelve months after completion unless on hold. Account email and profile information remain for account operation; these are separate from verification contact records.

Messages are retained for as long as both accounts are active. When either account becomes inactive, the conversation is automatically deleted three calendar months later by scheduled maintenance. Admin support follows the member account’s inactivity deadline; messages from an inactive administrator also expire after their inactivity deadline. Open complaints or unresolved paid meeting records can delay deletion until resolved. Inactive means deactivated, banned or marked for removal by an administrator or the unconfirmed-account cleanup; it does not mean merely a period without signing in. A self-deactivated account may be reactivated by signing in before its three-month deadline, explicitly choosing Yes and completing a fresh 2FA check. Reactivation cancels that account’s scheduled deletion; simply signing in or choosing No does not. Banned accounts cannot use this option. Meeting details are kept for three months after the scheduled end, unless an incident or complaint remains unresolved. When an active account has not logged in for more than twelve months, the administrator is notified. This does not automatically delete or deactivate the account. The administrator may separately remove an account without advance notice; removal disables access immediately and removes personal data, photos and associated messages unless an outstanding complaint or meeting record requires a hold. A minimal non-personal record may remain for database references. Self-deactivation instead follows the three-month reactivation and deletion period described above. New accounts that have never confirmed their email address are removed one week after creation without a further message to the account holder. The administrator receives the account details and removal outcome. Complaint or meeting holds may delay personal-data erasure.

Banning retains a keyed hash of the banned email address to prevent its reuse after personal data is removed. Scheduled deletion depends on the maintenance jobs running. Protected backups can retain historical records until their configured rotation expires; restoring a backup must be followed by maintenance to reapply deletion deadlines. Contact Admin to ask about access to or correction of your details or a privacy concern.

No analytics, advertising trackers, or third-party fonts are used. Registration uses a built-in image CAPTCHA, or Cloudflare Turnstile if configured by the administrator. Two-factor authentication may be delayed until seven days after account creation, then becomes compulsory. Authenticator keys are encrypted in the application database. Trusted-browser tokens expire after 30 days and can be revoked under Account security. An additional random browser-identity cookie lasts up to one year to group repeat trust choices; its hash is stored with trust records, and it cannot sign you in on its own. Turnstile contacts Cloudflare for the anti-bot check.

Contact: [email protected] · Contact Admin through the site.