> For the complete documentation index, see [llms.txt](https://whitepaper.appics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.appics.com/guidelines.md).

# Guidelines

<figure><img src="/files/hk5EAu19M0Rx50my0lQE" alt=""><figcaption></figcaption></figure>

**Content Regulation**

Although APPICS is a decentralized application without direct censorship, there will still be regulations upheld for the content that can be posted. Any content promoting violence, hate, criminal activity, racism or inappropriate nudity will not be tolerated. Abusive content will be filtered by moderators. Users have the ability to report certain content, which will be reviewed by moderators within 24 hours and if the content doesn’t comply with our regulations, the visibility in the app and rewards will be removed immediately. Furthermore Appics has a decentralized self-governing mechanism through the feature “downvoting”, which allows users to take responsibility and action to remove rewards and visibility from inappropriate content themselves.

**Ownership of Keys**

APPICS users are in ownership and full control over their keys. This allows for appropriate wallet security while at the same time preserving usability.&#x20;

<br>

**Fake Accounts**

While all network transactions will be completely secured by the nature of the Blockchain, APPICS accounts will be secured by passwords and mobile phone number verification.

It’s our priority to provide our users with a platform that is secure and safe in every way. Measures to prevent multiple account creation: A downside of the gamification of social media is that people will attempt to create more than one account, subsequently post and “vote multiple times, thereby manipulating the system and subverting its purpose. Appics will require users to register also through their social accounts. Furthermore, APPICS will ensure the authenticity of accounts through several methods, such as mobile phone verification and e-mail verification.

#### Terms and Conditions

{% embed url="<https://app.gitbook.com/s/UJqG1duxDVgIYPLKKQVL/>" %}

<br>


---

# 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://whitepaper.appics.com/guidelines.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.