Content Moderation Policy — Tairu Maps
1. In summary
Tairu Maps allows the Members of an Expedition to exchange messages with one another, in the group chat and in direct conversations. That content is written by users, not by us, and this policy states what is not accepted there, how to report it, what happens after a report and how long it takes.
Four mechanisms, all available inside the application:
| Mechanism | Where it is | Immediate effect |
|---|---|---|
| Hide | comes with the report | the message disappears for whoever reported it, at once |
| Report | long-press the message → Report | opens a case for human review |
| Block | in the chat, or under Contacts | ends the direct conversation and hides the person |
| Contact | this page and the app stores | direct channel to the officer |
Deadline: reported content is reviewed and, when the report is well-founded, removed within 24 hours.
2. What is not allowed
In the Tairu Maps chat, it is forbidden to publish:
- harassment, threats, intimidation or stalking of any person;
- hate speech or incitement to violence against people or groups;
- sexually explicit content, and any content involving minors in a sexualized manner;
- spam, unsolicited advertising and fraudulent schemes;
- personal data of third parties without consent;
- content that is illegal under Brazilian law.
The account that publishes such content may be deactivated, with or without prior notice, according to the severity.
3. How to report a message
- Press and hold the message in the chat.
- Choose
Report. - Select the reason:
Spam,Harassment,Inappropriate contentorOther. - If you wish, also tick
Also block this person. - Confirm.
The message disappears from your screen immediately, before any review. This depends neither on a connection to our servers nor on the moderator's decision: it is a hiding of your own, on your own device.
You cannot report your own message. To delete what you yourself wrote, use the chat's own delete option.
4. What happens to the report
The report opens a case recorded with the author of the message, the reported text, the reason chosen and the exact address of the message. No application, of any user, is able to read, alter or delete these cases — not even whoever reported it. They are accessible only to the moderation officer.
Once the case is open, the officer is notified automatically, by two independent channels: a notification on the device and a log alert on the server. The second one exists so that the report does not stall if no operator device is available.
The review is human and results in one of three decisions:
| Decision | What happens |
|---|---|
| Keep | the report is considered unfounded and the case is closed. The message remains hidden for whoever reported it |
| Remove | the message is deleted for everyone, and starts displaying "This message was deleted" |
| Remove and deactivate | the message is deleted for everyone and the author's account is deactivated, losing access to the application |
Removal is carried out on the server, with administrative privilege. This is a necessity, not an architectural choice: the security rules of the message database allow only the author themselves to write to the node of their message, so that removing reported content is impossible from any application — including the moderator's.
5. Blocking someone
Blocking is a decision of yours, immediate, and does not depend on review. Its effect, however, differs according to the place, and it is important to know this before relying on it:
In a direct conversation, the block holds on the server. Permission to send a direct message derives from the contact relationship between the two people; upon blocking, that relationship ceases to hold and the server refuses new messages from that person to you.
In the Expedition chat, the block hides, but does not prevent. The group chat is authorized by participation in the Expedition, not by the contact relationship. The blocked person can still publish there, and the other Members go on seeing what they write — it is you who stop seeing it. To remove someone from an Expedition, the decision belongs to the owner of the map.
The block is reversible under Contacts → Blocked.
6. Limits we state frankly
- There is no automatic content scanning. We do not analyze messages by keyword or by automatic
classifier. Moderation is reactive: it depends on someone reporting.
- There is no follow-up on the report inside the application. Since no client is able to read
the cases, you neither see the progress nor receive notice of the outcome. Whoever wants a reply should write to the address in section 8.
- The block in the Expedition chat is local, as stated in section 5.
- Messages are not read by us outside of a report. Reported content is the only content the
moderation officer examines.
7. Deactivated account
A deactivated account loses access to the application. The data that was only on the device, in Expeditions without cloud synchronization, remains on the device — the deactivation is of the account, not of the device.
Anyone who considers the decision mistaken may contest it through the address in section 8, describing what happened. The reply is given through the same channel.
8. Contact
danielhsmartin@gmail.com
Use this address for reports that do not fit within the application's flow, to contest a moderation decision, or to report illegal content. It is the same address published in the Privacy Policy, in the Terms of Use and in the app store listings.
9. Scope and effect
This policy applies to user-generated content inside Tairu Maps — group and direct chat messages — on every platform where the application is distributed.
It complements the Terms of Use and the Privacy Policy, and does not replace them. Changes take effect on the publication date of the new version.