Acceptable Use Policy

Reading note. Each section states its Purpose, illustrative Examples, the Prohibited conduct, and the Possible enforcement. Examples are non-exhaustive. Enforcement actions are drawn from the single ladder in §44-§46; naming them per section is indicative, not a fixed tariff.

1. Purpose

Purpose. This Acceptable Use Policy sets out the rules for using the Tirvea platform and services operated by WiseWave Limited. It protects members, the community, and the integrity and security of the Service. It applies in addition to the Terms of Service (/legal/terms) and Community Guidelines (/legal/community-guidelines).

Examples. Using Tirvea to meet people genuinely (permitted); using automated tools to mass-message members (prohibited, §14).

Prohibited conduct. Any use of the Service that breaches this Policy.

Possible enforcement. The full ladder in §44-§46, proportionate to the breach.

2. Definitions

Purpose. This section defines only AUP-specific terms; terms owned by other documents are used with their established meanings (contractual terms - Terms of Service; data-protection terms - Privacy Policy; behavioural terms - Community Guidelines).

"Automated means" - any bot, script, scraper, crawler, macro, or automated process operating the Service without genuine, individual human action.
"Credentials" - any authentication factor used to access an Account.
"Platform systems" - the Service's infrastructure, APIs, verification, moderation, ranking, and security systems.
"Verified account" - an Account that has completed Identity or Photo Verification.
"Content", "Account", "User", "Service" - as used in the Terms of Service (/legal/terms).

Possible enforcement. Not applicable (definitional).

3. Scope

Purpose. This Policy applies to everyone who accesses or uses the Service, by any means, and to all use of Platform systems including websites, applications, and APIs.

Examples. Access via the app, the website, or any programmatic interface is in scope.

Prohibited conduct. Attempting to place activity outside this Policy by using unofficial clients, intermediaries, or technical means.

Possible enforcement. Actions in §44-§46; access by out-of-scope means may be blocked.

4. Permitted Use

Purpose. To state the baseline of acceptable use against which prohibitions are measured. You may use the Service for its intended purpose: to create a genuine profile, discover and match with other adults, message consensually, and manage your Account and subscriptions, all through the official interfaces.

Examples. Browsing Discovery, expressing interest, messaging a match, subscribing to Premium.

Prohibited conduct. Any use beyond the intended, personal, non-commercial purpose of the Service, as detailed in §5-§43.

Possible enforcement. Not applicable to permitted use; misuse is actioned under §44-§46.

5. Prohibited Use

Purpose. To state the general prohibition that the following sections make specific. You must not use the Service unlawfully, deceptively, abusively, or in any way that harms members, third parties, or Platform systems. Sections 6-43 enumerate specific prohibitions; they are illustrative of, not a limit on, this general rule.

Examples. The conduct described in §6-§43.

Prohibited conduct. Anything that breaches this Policy, the Terms of Service (/legal/terms), or applicable law.

Possible enforcement. The full ladder (§44-§46), and referral to authorities where unlawful (§6, §42).

6. Illegal Activity

Purpose. To prohibit any unlawful use of the Service and to support our obligations for illegal content, including under the Digital Services Act.

Examples. Trafficking, unlawful sale of regulated goods (§30-§31 of the Community Guidelines), terrorist content, illegal hate speech.

Prohibited conduct. Using the Service to commit, facilitate, promote, or plan any activity that is illegal under applicable law, or to host or transmit illegal content.

Possible enforcement. Immediate removal of content, suspension or permanent removal (§45-§46), evidence preservation, and referral to authorities (Law Enforcement Guidelines, /legal/law-enforcement). [Legal review required before publication - confirm illegal-content categories and notice-and-action handling against the Digital Services Act and Irish implementing law.]

7. Fraud

Purpose. To prohibit deceptive schemes that harm members or WiseWave Limited. We operate fraud-detection and risk-scoring systems (see Privacy Policy §30-§31, /legal/privacy).

Examples. Romance scams, advance-fee fraud, investment "opportunities", account-takeover attempts.

Prohibited conduct. Any scheme to obtain money, data, access, or benefit by deception, including identity fraud (§11), payment fraud (§29), and scams (§27).

Possible enforcement. Restriction, suspension, or permanent removal (§45-§46), and referral to authorities and payment partners (§6).

8. Impersonation

Purpose. To ensure members are who they claim to be.

Examples. Posing as another real person, a celebrity, or WiseWave Limited staff.

Prohibited conduct. Creating or operating an Account that impersonates any person or entity, or that falsely suggests affiliation with WiseWave Limited.

Possible enforcement. Identity/photo review, suspension, or removal (§45-§46). See Community Guidelines §24 (/legal/community-guidelines).

9. Fake Accounts

Purpose. To keep the community genuine and free of deceptive profiles.

Examples. Fictitious personas, bot accounts, AI-generated identities (§39).

Prohibited conduct. Creating Accounts that do not represent a genuine individual, or that are designed to deceive, defraud, or manipulate.

Possible enforcement. Removal of the offending Accounts (§46); action against linked Accounts for evasion (§32).

10. Duplicate Accounts

Purpose. To enforce the one-genuine-account principle in the Terms (/legal/terms) and prevent duplicate-account farming.

Examples. Operating multiple Accounts; duplicate-account farming to evade limits or enforcement; mass-creating Accounts.

Prohibited conduct. Creating or operating more than one Account without our permission, or generating Accounts in bulk. We use duplicate-account detection (Privacy Policy §30, /legal/privacy).

Possible enforcement. Consolidation or removal of duplicates, restriction, or removal (§45-§46), including action across linked Accounts (§32).

11. Identity Verification Abuse

Purpose. To protect the integrity of Identity Verification (Stripe Identity). How it works is in the Identity Verification Policy (/legal/identity-verification).

Examples. Bypassing verification, submitting forged documents, using another person's identity, or verifying on behalf of someone else.

Prohibited conduct. Providing false, forged, or third-party identity information; attempting to defeat, spoof, or circumvent Identity Verification; selling, buying, or transferring verification or verified status.

Possible enforcement. Failed/fraudulent verification leads to PHOTO_REVIEW_REQUIRED, restriction, suspension, or removal (§45-§46), and referral to authorities (§6).

12. Photo Verification Abuse

Purpose. To protect the integrity of Photo Verification (AWS Face Liveness and AWS Rekognition). Detail is in the Photo Verification Policy (/legal/photo-verification).

Examples. Presenting a photo of a photo, a mask, a screen, or another person; using injection or emulation tools to defeat liveness.

Prohibited conduct. Any attempt to spoof, defeat, or circumvent liveness or photo-comparison checks; verifying with a likeness that is not your own.

Possible enforcement. Verification failure, PHOTO_REVIEW_REQUIRED, restriction, suspension, or removal (§45-§46).

13. Biometric Abuse

Purpose. To prohibit misuse of the biometric processing used solely for Photo Verification. Biometric handling and consent are governed by the Biometric Information Policy (/legal/biometric-data) and Privacy Policy §12 and §28 (/legal/privacy).

Examples. Attempting to enrol or verify as another person; biometric fraud to defeat identity checks.

Prohibited conduct. Submitting biometric characteristics that are not your own; interfering with, extracting, or attempting to reverse biometric processing; any biometric spoofing.

Possible enforcement. Verification failure, restriction, suspension, or removal (§45-§46), and referral where unlawful (§6).

14. Automation

Purpose. To ensure interactions are genuine and human.

Examples. Automated swiping, message automation, fake engagement, and scripted profile actions.

Prohibited conduct. Using automated means to operate the Service, including automated liking/swiping, bulk or automated messaging, and generating artificial engagement, without our express written permission.

Possible enforcement. Rate limiting, feature restriction (LIMITED), suspension, or removal (§45-§46).

15. Bots

Purpose. To prohibit non-human operation of Accounts.

Examples. Chatbots posing as members; automated account operation.

Prohibited conduct. Creating or operating bot Accounts, or using bots to interact with members or Platform systems.

Possible enforcement. Removal of bot Accounts (§46) and blocking of associated infrastructure (§35).

16. Scraping

Purpose. To protect members' data and the Service from bulk extraction.

Examples. Scraping profiles, crawling Discovery, harvesting images or member details.

Prohibited conduct. Accessing, copying, or collecting Content or member data by automated means, or systematically at scale, without our express written permission. This includes collecting data to build datasets (§17).

Possible enforcement. Suspension or removal (§45-§46), infrastructure blocking (§35), and legal action where warranted. [Legal review required before publication - confirm anti-scraping enforceability and interaction with database/IP rights under Irish and EU law.]

17. Data Mining

Purpose. To prohibit the aggregation and exploitation of member data.

Examples. Building datasets of profiles, images, or messages; compiling member directories; training AI using Tirvea content.

Prohibited conduct. Mining, aggregating, or repurposing Content or member data, including using Content to train, fine-tune, or evaluate machine-learning models, without our express written permission and any required consent of the members concerned.

Possible enforcement. Suspension or removal (§45-§46), and legal action. See Privacy Policy (/legal/privacy) for data-protection consequences. [Legal review required before publication - confirm the AI-training prohibition and its interaction with text-and-data-mining exceptions under EU copyright law.]

18. Reverse Engineering

Purpose. To protect the security and intellectual property of the Service.

Examples. Decompiling the app, probing internal APIs, extracting model logic.

Prohibited conduct. Reverse-engineering, decompiling, or disassembling the Service, or attempting to derive source code or the design of Platform systems, except to the limited extent that applicable law permits and cannot be excluded.

Possible enforcement. Suspension or removal (§45-§46), and legal action. See the Terms §36 (/legal/terms).

19. Security Testing

Purpose. To channel security research responsibly while prohibiting unauthorised testing.

Examples. Permitted: testing within the scope and rules of the Vulnerability Disclosure Policy (/legal/vulnerability-disclosure). Prohibited: unauthorised penetration testing, exploitation, or attacks on production systems or other members.

Prohibited conduct. Any security testing, probing, or exploitation of Platform systems outside the authorisation and scope of the Vulnerability Disclosure Policy; accessing data or accounts that are not yours.

Possible enforcement. Suspension or removal (§45-§46), and referral to authorities (§6). Good-faith research conducted within the Vulnerability Disclosure Policy is handled under that policy. [Legal review required before publication - confirm the security-research safe harbour and its scope against the Vulnerability Disclosure Policy and applicable computer-misuse law.]

Purpose. To keep Accounts secure and attributable to one person.

Examples. Sharing your password or authentication factors; publishing Credentials.

Prohibited conduct. Sharing, selling, or transferring your Credentials, or using another person's Credentials. You are responsible for your Account's security (Terms §5, /legal/terms).

Possible enforcement. Forced re-authentication, restriction, suspension, or removal (§45-§46).

Purpose. To enforce one-person-one-account and prevent trade in accounts.

Examples. Sharing verified accounts, selling accounts, selling verified/premium accounts, or operating an Account on another's behalf.

Prohibited conduct. Sharing, renting, selling, buying, or transferring any Account, including verified or Premium Accounts; operating Accounts as a marketplace.

Possible enforcement. Removal of the Accounts involved (§46) and reversal of any associated verified/Premium status.

22. API Misuse

Purpose. To protect the Service's programmatic interfaces. The Service exposes a versioned API surface; access is only through official, authorised means.

Examples. API abuse, unauthorised API access, exceeding granted scopes, or automating actions via the API without permission.

Prohibited conduct. Accessing the API without authorisation; exceeding rate or scope limits; reverse-engineering or abusing API endpoints; using the API to scrape (§16), mine (§17), or automate (§14).

Possible enforcement. Throttling, key/scope revocation, suspension, or removal (§45-§46), and infrastructure blocking (§35).

23. Spam

Purpose. To keep interactions genuine and wanted.

Examples. Bulk or repetitive messaging; unsolicited promotional messages.

Prohibited conduct. Sending spam, unsolicited bulk content, or repetitive automated messages (§14). See Community Guidelines §26 (/legal/community-guidelines).

Possible enforcement. Rate limits, feature restriction (LIMITED), suspension, or removal (§45-§46).

24. Commercial Promotion

Purpose. To keep Tirvea personal and non-commercial.

Examples. Advertising, recruitment, solicitation, sex work, promoting external paid services.

Prohibited conduct. Using the Service to advertise, promote, sell, recruit, or solicit, or to direct members to commercial or paid services, without our express written permission.

Possible enforcement. Content removal, restriction, or removal (§45-§46). See Community Guidelines §27 (/legal/community-guidelines).

25. Malware

Purpose. To protect members and Platform systems from malicious code.

Examples. Sharing links or files containing viruses, trojans, ransomware, or spyware.

Prohibited conduct. Uploading, transmitting, or linking to malware or any code intended to disrupt, damage, or gain unauthorised access to systems or data.

Possible enforcement. Immediate content removal, suspension or removal (§45-§46), infrastructure blocking (§35), and referral to authorities (§6).

26. Phishing

Purpose. To protect members from credential theft and deception.

Examples. Fake login pages, links impersonating WiseWave Limited, requests for Credentials or verification codes.

Prohibited conduct. Attempting to obtain Credentials, payment details, verification codes, or personal data by deception, or linking to phishing content (Community Guidelines §28, /legal/community-guidelines).

Possible enforcement. Link/content removal, suspension or removal (§45-§46), and referral to authorities (§6).

27. Scams

Purpose. To prohibit financial and romance scams, a primary safety risk.

Examples. Romance scams, blackmail, sextortion, extortion, catfishing to defraud.

Prohibited conduct. Any scheme to obtain money, data, or benefit from a member by deception or coercion.

Possible enforcement. Suspension or permanent removal (§45-§46), and referral to authorities (§6). See Community Guidelines §22 (/legal/community-guidelines).

28. Financial Abuse

Purpose. To prohibit exploitation and abuse involving money or financial information.

Examples. Soliciting money or gifts under false pretences; laundering; misuse of others' financial information.

Prohibited conduct. Using the Service to financially exploit members or to process, conceal, or facilitate unlawful funds.

Possible enforcement. Suspension or removal (§45-§46), and referral to authorities and payment partners (§6).

29. Payment Abuse

Purpose. To protect the payment and subscription systems. Payments are processed by Stripe (Privacy Policy §36, /legal/privacy).

Examples. Payment fraud, use of stolen cards, credential stuffing against payment flows.

Prohibited conduct. Using stolen, unauthorised, or fraudulent payment methods; manipulating pricing or billing; circumventing payment controls.

Possible enforcement. Reversal of benefits, restriction, suspension, or removal (§45-§46), and referral to authorities and payment partners (§6).

30. Chargeback Abuse

Purpose. To prevent abuse of the chargeback process.

Examples. Chargeback abuse - disputing legitimate charges in bad faith after using the Service.

Prohibited conduct. Initiating fraudulent or bad-faith chargebacks; using chargebacks to obtain the Service without payment.

Possible enforcement. Suspension or removal (§45-§46), recovery of amounts due, and loss of access pending resolution. Legitimate refund rights are unaffected - see the Refund Policy (/legal/refund-policy).

31. Subscription Abuse

Purpose. To protect the integrity of Premium subscriptions.

Examples. Subscription fraud, abusing trials or promotions, referral abuse, exploiting billing errors.

Prohibited conduct. Manipulating subscriptions, trials, promotions, or referrals to obtain benefits you are not entitled to; sharing or reselling Premium access (§21).

Possible enforcement. Reversal of benefits, restriction, suspension, or removal (§45-§46). See the Subscription Terms (/legal/subscription-terms).

32. Circumventing Restrictions

Purpose. To prevent evasion of enforcement and technical controls.

Examples. Creating new or duplicate Accounts after enforcement (duplicate-account farming, §10); ban evasion; using proxies or spoofing to bypass blocks.

Prohibited conduct. Circumventing, or attempting to circumvent, any restriction, suspension, ban, rate limit, or technical control, including via new Accounts, altered identifiers, or intermediaries.

Possible enforcement. Escalation up the ladder, action against linked and evasion Accounts, and permanent removal (§46). See Community Guidelines §46 (/legal/community-guidelines).

33. Rate Limit Abuse

Purpose. To protect Platform systems and fair access.

Examples. Rate-limit abuse, request flooding, enumeration attacks that probe identifiers.

Prohibited conduct. Exceeding or evading rate limits; automated high-frequency requests; enumeration or brute-force patterns against Platform systems.

Possible enforcement. Throttling, blocking, suspension, or removal (§45-§46), and infrastructure blocking (§35).

34. Platform Integrity

Purpose. To protect the systems that keep the Service fair, safe, and trustworthy.

Examples. Manipulating matching, Discovery, or ranking; interfering with moderation or verification; fake engagement (§14).

Prohibited conduct. Manipulating, gaming, or interfering with Platform systems, including ranking, verification, moderation, and safety systems.

Possible enforcement. Restriction, suspension, or removal (§45-§46). See Community Guidelines §48 (/legal/community-guidelines).

35. Infrastructure Abuse

Purpose. To protect the Service's infrastructure and third-party providers.

Examples. Overloading systems; abusing hosting, authentication (Supabase), payment (Stripe), or verification (AWS) infrastructure.

Prohibited conduct. Any activity that damages, overloads, or interferes with the infrastructure of the Service or its providers, or that abuses provider systems.

Possible enforcement. Blocking of infrastructure and Accounts, suspension or removal (§45-§46), and referral to authorities (§6).

36. Availability Attacks

Purpose. To prohibit attacks on the availability of the Service.

Examples. DoS attacks, distributed denial-of-service, session hijacking, and connection flooding.

Prohibited conduct. Any denial-of-service or availability attack, session hijacking, or attempt to degrade or disrupt the Service for others.

Possible enforcement. Immediate blocking, suspension or removal (§45-§46), and referral to authorities (§6). See the Security Policy (/legal/security).

37. Privacy Violations

Purpose. To protect members' personal information. WiseWave Limited's own data handling is in the Privacy Policy (/legal/privacy); this section prohibits members from violating others' privacy.

Examples. Doxxing; sharing others' images, messages, or personal data without consent; unauthorised recording (Community Guidelines §33-§34, /legal/community-guidelines).

Prohibited conduct. Collecting, publishing, or misusing another person's personal information without a lawful basis and consent.

Possible enforcement. Content removal, restriction, suspension, or removal (§45-§46), and referral where unlawful (§6).

38. Intellectual Property Abuse

Purpose. To protect intellectual-property rights.

Examples. Posting infringing images or text; misusing the Tirvea brand.

Prohibited conduct. Uploading or sharing Content that infringes copyright, trademark, or other IP rights, or misusing WiseWave Limited's IP. IP complaints follow the Copyright Policy (/legal/copyright).

Possible enforcement. Content removal, action against repeat infringers, suspension or removal (§45-§46). See Terms §36-§38 (/legal/terms).

39. AI Abuse

Purpose. To prevent misuse of AI tools on the Service.

Examples. AI-generated fake profiles (§9); AI used to deceive, defraud, or harass; using Tirvea Content to train models (§17).

Prohibited conduct. Using AI to create deceptive identities or Content, to automate abuse, or to exploit members; using Content for AI training without permission.

Possible enforcement. Photo/identity review, restriction, suspension, or removal (§45-§46). See Community Guidelines §35 (/legal/community-guidelines).

40. Synthetic Content Abuse

Purpose. To prohibit deceptive or harmful synthetic media.

Examples. Synthetic personas, manipulated images used to deceive (Community Guidelines §37, /legal/community-guidelines).

Prohibited conduct. Creating or sharing synthetic or manipulated Content designed to deceive about identity or appearance, or to harm others.

Possible enforcement. Content removal, restriction, suspension, or removal (§45-§46).

41. Deepfake Abuse

Purpose. To prohibit deepfakes that impersonate or violate others.

Examples. Deepfakes impersonating a real person; synthetic intimate imagery without consent.

Prohibited conduct. Creating or sharing deepfakes that impersonate any person or that constitute non-consensual intimate imagery; any synthetic sexual content involving minors is prohibited absolutely (§42).

Possible enforcement. Immediate removal, suspension or permanent removal (§45-§46), and referral to authorities (§6). See Community Guidelines §36 (/legal/community-guidelines).

42. Child Safety

Purpose. To state, in this Policy, the absolute prohibition on any child-safety violation. Full detail is in the Child Safety Policy (/legal/child-safety).

Examples. CSAM; grooming; sexualisation of minors; any content or contact that exploits or endangers a child; use by anyone under 18.

Prohibited conduct (absolute). Any child sexual abuse material, grooming, exploitation, or sexualisation of minors, and any use of the Service by a person under 18. There is no permitted context.

Possible enforcement. Immediate permanent removal (§46), evidence preservation, mandatory reporting to the appropriate authorities and hotlines, and full cooperation with law enforcement (Law Enforcement Guidelines, /legal/law-enforcement). [Legal review required before publication - confirm mandatory-reporting obligations and designated bodies for the launch jurisdictions.]

43. Reporting Abuse

Purpose. To protect the integrity of the reporting and appeals systems.

Examples. Appeal abuse - repeated or manifestly unfounded appeals; mass or false reports intended to harass (Community Guidelines §38, /legal/community-guidelines).

Prohibited conduct. Submitting knowingly false, bulk, or abusive reports, or abusing the appeals process, to harass members or overwhelm moderation.

Possible enforcement. Restriction of reporting/appeal privileges, and, consistent with the Digital Services Act, suspension after warning for members who frequently submit manifestly unfounded reports (§44-§46). [Legal review required before publication - confirm misuse-suspension drafting against DSA Art. 23.]

44. Enforcement

Purpose. To explain how we enforce this Policy. We apply a proportionate, graduated ladder based on the severity of the breach, intent, harm, and history, using automated and human systems described in the Trust & Safety Policy (/legal/trust-safety) and AI Moderation Policy (/legal/ai-moderation). Consistent with those policies, automated systems do not impose permanent bans on their own; a permanent outcome involves human review. The most serious breaches (such as child safety, §42) result in immediate permanent removal regardless of history.

Examples. A first minor breach may warrant a warning; a serious breach may warrant immediate removal.

Prohibited conduct. Evading or retaliating against enforcement (§32).

Possible enforcement. The graduated actions in §45-§46, and the account states described in the Account Suspension Policy (/legal/account-suspension). We provide a statement of reasons for significant decisions, consistent with the Digital Services Act. [Legal review required before publication - confirm statement-of-reasons and notice-and-action drafting against the Digital Services Act.]

45. Temporary Restrictions

Purpose. To limit harm while preserving the possibility of return and to hold Accounts pending review.

Examples. Feature limits after spam; photo review after a verification anomaly; suspension pending investigation.

Prohibited conduct. Evading a restriction via new or duplicate Accounts (§32).

Possible enforcement. Temporary states include feature limitation (LIMITED - read access retained, outbound engagement removed), photo review (PHOTO_REVIEW_REQUIRED - uploads blocked until cleared), and suspension (SUSPENDED - no app access, reversible and appealable), including emergency suspension where necessary. See the Account Suspension Policy (/legal/account-suspension).

46. Permanent Suspension

Purpose. For the most serious or persistent breaches, permanent removal ends access to the Service.

Examples. Child-safety violations (§42), serious fraud (§7), availability attacks (§36), or repeated serious breaches.

Prohibited conduct. Returning through new or duplicate Accounts after removal (§32).

Possible enforcement. Permanent removal (BANNED - a terminal state) which remains appealable (§47). Data handling after removal follows the Data Retention Policy (/legal/data-retention) and Privacy Policy (/legal/privacy).

47. Appeals

Purpose. To give a fair route to challenge an enforcement decision under this Policy.

Examples. Appealing a suspension you believe was mistaken.

Prohibited conduct. Abusive or manifestly unfounded appeals (§43).

Possible enforcement. On appeal we may uphold, reverse, or modify a decision, providing a statement of reasons and information about out-of-court dispute resolution where applicable. The process is in the Appeals Policy (/legal/appeals). [Legal review required before publication - confirm internal-complaint-handling and out-of-court dispute settlement drafting against the Digital Services Act.]

48. Changes

Purpose. To explain how this Policy changes. We may update this Acceptable Use Policy to reflect changes in the Service, abuse patterns, security needs, or the law. We will update the "Last Updated" date and, where a change is material, take reasonable steps to notify you. Because this Policy is incorporated into the Terms of Service (/legal/terms), material changes are handled consistently with the Terms' change process.

Examples. Adding a prohibition to address a new abuse technique.

Prohibited conduct. Relying on a superseded version to justify a breach.

Possible enforcement. The current Policy applies to use after it takes effect.

49. Contact

Purpose. To tell you how to reach us about this Policy.

Entity: WiseWave Limited (Company Number 762171)
Registered office: 39 Cooley Park, Dundalk, Co. Louth, A91 AP2V, Ireland
Email: info@tirvea.com

To report abuse, use the in-product reporting tools (Community Guidelines §38, /legal/community-guidelines). For security vulnerabilities, use the Vulnerability Disclosure Policy (/legal/vulnerability-disclosure). For appeals, see the Appeals Policy (/legal/appeals).