WardForth / Legal

WardForth
privacy policy.

Privacy, in plain view.

Read the policy ↓
WardForth / LegalFull policy text

1. Who is responsible

WardForth is a moderation bot for Telegram groups. It is operated by WardForth, Sweden, [email protected], which this policy calls "we".

The group you are a member of decides whether to use WardForth, who may moderate, and whom to ban, mute or restrict. For the records the bot keeps about the group's members and moderators, the group is the controller and we are its processor: we process those records on the group's behalf and on its instructions, under a written agreement with the group.

For the data we hold about the customer who signed up for WardForth, such as the owner's contact details and the agreement, we are the controller.

Telegram is a separate company and a separate controller. It gives bots only the data its own privacy policy lists for bots, and it enforces every ban, mute and restriction in the group.

2. What we record, and why

WardForth keeps no running copy of the group's chat. It never stores pictures, video, stickers, audio or any other media, whatever the reason for a ban. A ban, mute, restriction or lift below is made by a person the group has given that power, by a rule the group's owner has turned on (section 8), or by WardForth itself when a ban the bot holds reaches its end. The code also has a route for a WardForth operator to make one, recorded with the operator as its actor; nothing in the running service uses that route today.

WhenWhat is recordedWhy
A moderator bans you with an ordinary reasonYour Telegram user ID and the username you had at the time, never your display name; which group; when; who banned you or which rule applied; the reason code the moderator chose (spam, harassment, off-topic, illegal content or other); any short reason the moderator wrote; how long the ban lasts; and the text of the message the ban was a reply to, if there was one. If there was no message, the entry says so and nothing is invented. The text is kept for requests about your data and for disputes, and the bot does not show it to anyoneTo enforce the ban for its duration, to let the group's moderators recognise a person who misbehaves again, and to let the group review the decision if asked. The text: to answer your requests and to settle a dispute about the ban. The bot has no appeal command or appeal workflow
A moderator mutes or restricts youYour Telegram user ID, which group, when, who acted, the action and its duration, and any short reason the moderator wrote. A mute or restriction stores no username and no reason code. The message that led to it is stored too, for requests about your data and for disputes. The bot does not show it to anyone, you included; the group's owner and moderators see the entry without the messageThe same purposes as a ban
A moderator lifts a ban, mute or restrictionWho, by whom or by which rule, and when. A lift made by a rule also records the rule's reason code; a lift made with /unban or /unmute records noneSo the group's history is complete
You join or leave the groupYour Telegram user ID, your username if you have one, and the timeTo detect raids, waves of spam, and banned people who come back under another account
You send the bot a command you are not allowed to use, for example a moderator command as an ordinary memberYour Telegram user ID, the group, the command's name, the time and why it was refused. Never the rest of the message. If the command came from an anonymous administrator, the sender chat is recorded, together with the administrator title the message carried if it carried one, and no person is inventedTo protect the group and the service against misuse. After repeated refusals, by default five within a rolling ten-minute window, the group's owner is warned, once per person and group. Every Telegram administrator of the group who has opened a private chat with the bot is also told privately that an administrator command was refused
A moderator acts, or a role or setting changesThe moderator's identity is stored on each moderation entry they create. Every ban, mute, restriction and lift is also written to a hash-linked audit log, with the kind of action, the reason code and the end date, never a text or a username. Changes to roles, settings, retention choices and pilot grants are written to the same log with old and new valuesSo the group can see who did what, and to keep an ordered record of these actions and changes
A moderator or rule assigns a point to youYour Telegram user ID, the group, the rule and actor, the number of points, a reason code, when the points expire, and the enforcement outcome. No message text or media is storedTo count recent outcomes and apply the action selected by the group's owner
You apply for the free pilotYour Telegram user ID and username if you have one, the language the bot uses with you, the one to five Telegram group links you send, and the application's state and datesTo review the application, contact you in the bot, and create an activation link if approved
A rule the owner turned on checks a messageWhat the rule found or did, also when it only reports what it would have done: the rule, the result, how long you had been in the group as a band, which of the owner's patterns matched, and the time. No user ID and no text. When a rule that is on mutes, bans or lifts, and the action is recorded, the record carries the same identifier as the record of that action, which points to the moderation entry that names you. When a rule gives you a warning point, the record carries the same identifier as the point, which names you, also while the rule only reports. Any other record, such as one made while a rule only reports what it would have done, or one of a deleted message or of a closed or reopened gate, is linked to no moderation entry and holds nothing that names youTo show the owner what a rule does before and after it is turned on
The owner describes the group or uses its recommendationsThe owner's description of the group, and who gave it; who applied or undid a recommendation; who asked for the weekly summaryTo give recommendations built from the group's own numbers
The owner names the group's invite linksThe names the owner gives the links, which may contain anything the owner types, the links themselves, and how many people joined through each link per hour, never whoTo show the owner which link brings members
A moderator bans you for spam, as a reply to your messageNothing more is recorded about you. The bot may offer the group's owner up to three phrases from the message, in a private chat, to add to a rule the owner turns on (section 8). A phrase the owner approves becomes part of the owner's own rule, which keeps no link to the ban or to you, and it stays while the rule exists. A separate link to the ban's entry is kept only as long as that entry, so that the phrase can be removed if the ban is moved into the category of section 3, and it is deleted with the entry. Phrases the owner does not approve are not stored by us; the offer itself stays in the owner's chat in Telegram (section 5)To catch the same spam again, as the owner chooses
You ask us about your dataThe request, when it arrived, how we checked it was you, the deadline, and the answer. Never the original material you may have attachedTo answer within the legal deadline and to show that we did
The customer signs upThe owner's contact details, the agreement version and the date it was approved, and in the beta a licence entry created by hand with no end dateTo run the service for the customer

A ban may apply to all groups of the same customer if the moderator chooses so when banning; it never reaches another customer's groups. In a group where such a ban was applied from another of the customer's groups, the entry carries a mark that it came from another group, never which one; only a person who is an administrator in both groups sees which.

3. The category "Serious violation of Telegram's terms"

A moderator may ban with the reason "Serious violation of Telegram's terms" (in Swedish "Allvarligt brott mot Telegrams villkor") when a message is content that Telegram itself does not allow. Then:

  • the bot asks the moderator to confirm first, because nothing of the message can be recovered afterwards;
  • the bot tries to delete the message at once and tells the moderator if Telegram does not delete it. WardForth keeps none of the message itself: no text, no media, no file identifier, and no setting of the group can change that. If the deletion fails, the bot keeps only the chat ID and the message ID, never any content, while it retries and for at most 48 hours;
  • the only record is the entry: who was banned, in which group, when, by whom or by which rule, and the reason, which the bot stores as Violates Telegram's ToS. "Who" is your Telegram user ID; no username is kept with an entry in this category;
  • the ban has no end date and is lifted only by the group, never automatically;
  • the entry is kept for the group's chosen period, counted from the ban, and removed like every other entry in the group.

If a ban made earlier with another reason is moved to this category, the text and its live key are removed from the live service at the same time. An older database backup can retain a matching copy of both for up to 15 days. Anyone who may ban in the group may move a ban into this category and back. A ban that applies to several of the customer's groups and is moved into this category in one of them is moved in all of them. If a ban is moved back after a mistake, it becomes an ordinary ban again with its original end date; if that date has already passed, the ban is lifted at once; deleted text never comes back.

Deciding to ban, and reporting the content to Telegram or to the police, is the group's decision and responsibility. We send no report of our own.

ProcessingBasis
The group's entries about bans, mutes, restrictions, their lifting, the written reason and the stored message text; the group's historyThe group's legitimate interest in keeping its community free of abuse and in enforcing the bans it has made (Article 6(1)(f)), weighed against your interests in the balancing test the group has adopted
Members joining and leavingThe group's legitimate interest in detecting raids, waves of spam, and banned people who come back under another account (Article 6(1)(f)), weighed in the balancing test
Refused commandsLegitimate interest in the security of the network and the service, which the GDPR's recital 49 names as such an interest
The customer's account dataThe contract with the customer (Article 6(1)(b)). That basis covers the customer's own data only, not a banned member's
An entry in the category "Serious violation of Telegram's terms"Until a lawyer has answered, the group relies on the legal obligation to remove such content under Swedish law (lag (1998:112) 5 §, through förordning (2018:219) 5 § 2) and on the establishment, exercise or defence of legal claims (förordning (2018:219) 5 § 1). A lawyer will confirm which of these applies.

5. Who sees your data, and where it is kept

RecipientWhat they see
The group's owner and moderatorsEvery entry of their group for its whole retention period, including the reason code. They do not see the stored message text of a ban, a mute or a restriction: the bot does not show it. In the pilot they read and act through the bot only. They also see who joined and left in the last 90 days and the refused commands of the last year. A moderator sees only the groups where they hold a role; the owner and a Super User see all of the customer's groups. Every Telegram administrator of the group automatically holds a base role in the bot that lets them ban, unban, mute, unmute, restrict and read the group's history. When the bot leaves a group, that group's data is hidden from everyone at the customer, a Super User included (section 6)
YouYour own entries on request, through the request route of section 7. The bot does not show you a stored message text, the one behind your own mute or restriction included; the answer to an access request contains what we hold about you
Our operations and support person on dutyOnly what a support case or an incident needs. A manual database read is not automatically added to the audit log
UpCloud, in Stockholm, SwedenHosts the database and the bot. Four things are encrypted one by one, each under a key of its own kept apart from the data: the text of a message, a moderator's written reason, the username kept with a ban or a join, and the title an anonymous administrator's message carried. The rest is stored without that encryption: your Telegram user ID, the group, the times, the reason code and the other data in section 2
GlitchTip's hosted EU instance (eu.glitchtip.com), in Frankfurt, Germany, Burke Software (burkesoftware.com)Technical error reports. The application uses fixed error codes and metadata filters intended to exclude user and chat identifiers, message text and file identifiers
Audit-copy code for UpCloud Object Storage in the EUThe application can copy audit entries and their hash chain to a separate host when a bucket and its credentials are configured
Proton AG, in SwitzerlandCarries our e-mail. A request you send to [email protected], our answer to it, and any other message you send us or we send you by e-mail pass through Proton. The European Commission has decided that Switzerland protects personal data adequately (Decision 2000/518/EC), so this needs no further safeguards
TelegramEvery ban, mute, restriction and lifting is carried out by sending a command with your Telegram user ID to Telegram, which enforces it. Telegram also carries the bot's own messages, which stay in the chats they were sent to: a report alert to the group's administrators, in private or in a chat the administrators chose for alerts (the group's title, what the bot's checks found, and a link to the reported message), the phrases offered to the group's owner after a spam ban (section 2), and the one-time code of a request about your data (section 7). Telegram is the platform you use, not a company we engaged; it is a separate controller located outside the EEA that states it stores EEA users' data in the Netherlands
AuthoritiesOnly on a lawful request, and then only the entry we hold. We answer such requests with a lawyer

We keep and process your data in the EU, with one exception: our e-mail, which passes through Proton AG in Switzerland, as the table above says. Switzerland is covered by the European Commission's adequacy decision 2000/518/EC.

6. How long we keep it

DataKeptThen
A ban entryFor the ban plus the group's chosen period, counted from the day the ban ends. The period is one year unless the group chose two years, or three years with a prepaid subscription. The bot's reply to a ban or a mute names its end date, and the line the bot posts when it is activated names the group's periodHidden from the moderators, kept for up to 60 days in a store used only to answer your requests, then deleted. The 60 days count from the day the entry should have moved there, not from a late move
A mute, restriction or lifting entryFor the group's chosen period, counted from the event. A lifting entry for a ban stays as long as that ban does, even past its own period, and then leaves with it; if that is more than 60 days after its own period ended, it is deleted at once instead of moving to the storeAs above
The message text behind a ban90 days, or less if the entry itself goes earlierDeleted, and the key that protected it is destroyed
The message behind a mute or restrictionAt most 90 daysDeleted
The short reason a moderator wroteAs long as the ban, mute or restriction lastsDeleted; the reason code stays in the history
An entry in the category "Serious violation of Telegram's terms"For the group's chosen period, counted from the banRemoved like any other entry. The ban itself stays until the group lifts it
Joining and leaving90 daysHidden, kept for up to 60 days in the store used only to answer your requests, then deleted
A refused commandOne yearHidden, kept for up to 60 days in the store used only to answer your requests, then deleted
Your data while you have a request pending with usThe periods in this table still run. The deletion jobs can pause for a recorded hold, but nothing in the service records one yet, so a pending request does not pause deletion todayAs the other rows
Points assigned with /warn or by a ruleThey count until the rule's configured expiry. They are kept for the group's chosen period, counted from when they were given, then hidden for up to 60 days before deletion. No command shows them as history today. The person's active points are shown in one place only: the bot's reply in the group where a /warn was sent, when that /warn finished with the rule on. No total is shown when the rule only reports, when the same command arrives again, or when the mute or ban the ladder chose was refused, failed or did not finish; the reply then says only that the warning did not finish. A point given by a rule without /warn would show no total either; no rule gives one today. If the bot leaves the group, they are deleted at the end of the 7 days once Telegram confirms the bot is no longer in the group, even if the group's period has not endedDeleted after the hidden period, or at the end of the 7 days after the bot leaves the group, unless a recorded hold pauses deletion
A pilot applicationPending applications are deleted after 30 days. A declined application is deleted when it is declined. An approved application is deleted after all activation links have been used or 90 days after approval, whichever comes firstDeleted
What a rule found or didNothing deletes it today, also not after the bot leaves the groupNot deleted today
The group's description, recommendation changes and the weekly-summary choiceThe description and the summary choice while the group is active, then until 67 days after the bot leaves it (the 7 days plus 60); a recommendation change for 60 daysDeleted
Invite link names and their hourly countsThe hourly counts for 60 days while the group is active. When the bot leaves the group, the names, the links and all their counts are kept through the 7 days and deleted at their end once Telegram confirms the bot is no longer in the group, also counts younger than 60 days; until Telegram confirms it, nothing deletes themDeleted
BackupsEarlier copies of both data and the matching key can remain in the database's backups for up to 15 days after deletion. Restoring a backup that contains both can make that earlier copy readable again until the backup expiresGone when the backup expires
The audit record of bans, mutes, restrictions and lifts, and of changes to roles, settings, the retention choice and the grantThe configured period is stored with the group, but the current application does not automatically delete audit entries when that period endsNo current automatic deletion
A phrase the group's owner approved from a spam banAs long as the owner keeps it in the rule. Nothing deletes a rule itself today, so a phrase the owner does not remove staysDeleted when the owner removes the phrase
A group's history, when the bot leaves the group: its bans, mutes, restrictions and liftings, joins and leaves, and refused commandsHidden at once from everyone at the customer. Kept for 7 days in case the group comes back, then, once Telegram confirms the bot is no longer in the group, moved to the store used only to answer your requests and kept there for 60 days. While no check gets an answer from Telegram, nothing moves. At that same point the group's warning points, invite links and their hourly counts are deleted (the rows above); other data about the group keeps the period this table gives itDeleted. Bans the bot would have lifted itself stay in Telegram, and the group's owner is told
The 7 days after the bot leaves a groupThe licence holder can bring the group back. The same group comes back automatically if the bot is added to it again within the 7 days; the data goes to another group only if the licence holder chooses that, in a private chat with the bot, and only to a group of the same customer; that move is recorded in our audit log. In the other group, the bans, mutes, restrictions and warnings recorded in the earlier group come along only as the earlier group's history: the bot does not apply them there, and earlier warnings do not count there. The licence holder is also offered an export: a file the bot sends in a private chat to the licence holder only, with the group's description, the names of its invite links, its settings and rules, the history of bans, mutes and restrictions with their dates, reason codes and written reasons, joins and leaves, refused commands, roles, statistics and applied recommendations. The export never holds the text of a message, which moderator acted, network bans (bans that apply in the groups of all WardForth's customers), or bans in the category "Serious violation of Telegram's terms"After the 7 days, as the row above

Periods are counted on the calendar: a date that does not exist is read as the last day of that month, so 29 February plus one year is 28 February.

7. Your rights

You have the right to ask for access to your data, to have it corrected, to have it erased, to have its processing restricted, and to object to processing that rests on legitimate interest. These rights are not a choice, and no group setting can switch them off.

RightWhat it means here
AccessYou get confirmation of what the group holds about you, a copy of it, the purposes, who received it, how long it is kept and where it came from. The copy does not reveal who the moderator was or what other people wrote
ErasureWhile a ban lasts, the stored message text and the written reason are deleted on your request; your user ID and the reason code are kept until the ban ends, because the ban cannot be enforced without them. A request to delete is not a request to be unbanned. After a ban has ended, a request to delete what we hold about it is not granted while the group's owner has a paying subscription and for 60 days after the subscription ends. What our retention periods in section 6 delete earlier is deleted on that schedule. In the free pilot, the group's pilot grant counts as the subscription: such a request is not granted while the grant lasts and for 60 days after it ends
ObjectionYou may object to processing that rests on legitimate interest. The group then stops unless it shows compelling legitimate grounds that override yours, or needs the data for legal claims
RestrictionWhile an objection is assessed or you contest accuracy, you may ask that your data be stored but not used
CorrectionA wrong entry is corrected by the group. A ban moved to the category "Serious violation of Telegram's terms" by mistake can be moved back by anyone who may ban in the group; if its original end date has already passed, it is lifted at once; deleted text does not return

How to ask: send your request to [email protected]. Because we process on the group's behalf, we pass your request to the group; we prepare the answer, the group approves it, and we send it to you on the group's behalf, so you get one answer. We need to be sure the request comes from the account it concerns. To check that, the bot sends a one-time code to that Telegram account in a private chat, and you return the code by the channel you wrote from; if the account has never opened a chat with the bot, you are asked to send it /start first. Nothing else is collected for the check.

You get an answer within one month. In a complex case that can be extended by two months, and we tell you within the first month if so and why. If a request is refused, we tell you why within one month, and you may complain to Integritetsskyddsmyndigheten (IMY), the Swedish supervisory authority.

8. Rules the owner turns on

A ban, mute or restriction is decided by a person the group has authorised, or by a rule the group's owner has turned on. WardForth itself only lifts a ban the bot holds when it reaches its end, and the operator route of section 2 is unused today. A rule acts only on what the owner set. A ban, mute or restriction a rule makes is recorded with the rule as its actor, a moderator can undo it, and you can ask the group to review it.

9. Age

Telegram requires users in the EU to be 18 to sign up. WardForth has no age information of its own and treats every member the same.

10. Changes and contact

Questions go to [email protected].

Coming

Not available yet. A feature moves up when it ships and its tests exist.

1. Who is responsible

How you were told about the bot: the group's owner pins a message in the group that names WardForth and /privacy, and the bot posts one line in the group when it is activated.

7. Your rights

In a private chat with the bot, /privacy shows this policy and that address.

10. Changes and contact

We change this policy when the service, the law or the lawyer's review requires it, and we publish the new version on the same page and through /privacy.