> For the complete documentation index, see [llms.txt](https://amore.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amore.gitbook.io/wiki/whitepaper/avoiding-scammers-and-privacy-issues.md).

# Avoiding Scammers and Privacy Issues

User experience is ruined often due to the centralized and controlled nature of contemporary dating platforms. Various spoilers can become very demotivating. Moreover, if caution is not practiced, the risk of getting scammed runs high.&#x20;

The onset of the pandemic was followed by an increase in the online dating demand, and this has also led to a higher fraud rate. Fraud rates have jumped over 7.5% and the dating world alone has witnessed a 40% increase in the fraud ratio from the beginning of the pandemic to April 2021. Since the start of this pandemic, online daters have suffered a loss of approximately $100 Million (£70m). This figure is a conservative estimate, and the real figure is thought to be much higher. Here is a complete list of these spoilers that are a common occurrence in the dating world now:


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://amore.gitbook.io/wiki/whitepaper/avoiding-scammers-and-privacy-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
