Terms of Service

CLOVERA TERMS OF SERVICE
Last updated: October 21, 2026
Contact: kitteniversestudios@gmail.com

1. Acceptance of Terms
These Terms of Service govern access to and use of Clovera, a service operated by Kitteniverse Studios, including its websites, applications, community features, feed, direct messaging, and related services. By creating an account, accessing, or using Clovera, a user agrees to these Terms. A user who does not agree must not use the service.

At registration, and again whenever these documents are materially revised, each user is asked to confirm acceptance of these Terms, the Privacy Policy, and the Community Guidelines, and to confirm that they have read the KVKK Privacy Notice, which describes how personal data is processed under Turkish Law No. 6698 and is available in-app at /legal/kvkk-notice. The KVKK Privacy Notice is an information notice rather than a contract; confirming it records that the user has been informed, and does not by itself constitute explicit consent to any processing for which the KVKK requires separate explicit consent.

2. Eligibility
Users must be at least 13 years old, or older if the law in their country requires a higher minimum age for use of online services. If a user is under the age of legal majority in their jurisdiction, the service may only be used with permission from a parent or legal guardian. Users who are prohibited by law from using online services may not use Clovera. The registration form asks for a date of birth, which is used in that request to check this minimum age and is then discarded; Section 10 of the Privacy Policy says what is and is not kept. Clovera may refuse or remove an account where it has reason to believe its holder is below the minimum age.

3. Account Registration and Security
Registration requires a username and a password. Clovera does not ask for an email address or telephone number, and holds none for any account. Users should understand what follows from this: there is no password reset by email, and no way for Clovera to verify that a person is the holder of an account other than through the account itself.

Because of that, account recovery rests on two things the account itself can prove. At registration Clovera issues a set of single-use recovery keys and displays them once; only a digest of each key is stored, so a key that is not saved cannot be recovered from Clovera, and a new set can be generated at any time in settings, which invalidates the previous one. Alternatively, a user still signed in on another device can approve a reset request from that device; that device is shown when the request was made, what browser made it, and whether it came from an address the account has signed in from before, and the request expires thirty minutes after it is made if it is not answered. Anyone can make such a request against any username, so it must be refused unless the person deciding on it made it themselves. A user who has neither a recovery key nor a device that is still signed in will lose access to the account permanently, and Clovera cannot restore it. Users are responsible for maintaining the confidentiality of login credentials and recovery keys, and for activities that occur through their accounts, and must not share credentials in a way that creates security risks.

Upon each successful login, Clovera records which account signed in, when, the User-Agent string of the browser, and a digest of a random identifier Clovera places in that browser. Section 12 of the Privacy Policy describes that identifier: it lets Clovera's administrators see which accounts have been used from the same browser, which is treated as a lead and never acted on automatically, and it lets the termination of an account extend to the browsers that account was used from. Clearing the site's cookies removes it. The login record holds nothing derived from the IP address of the connection. The address is used while the request is being handled — to apply rate limits, to check the address against a ban, where the operator has enabled bot protection to verify a challenge with the provider identified in the Privacy Policy, to which the address is transmitted in full for that check, and to keep the short-lived Kitguard counts described in Section 7 — and is afterwards kept only as a one-way keyed digest, and only in the records Section 12 of the Privacy Policy lists: the address used at registration, the address of each active session, the address of a failed login attempt or a refused recovery key, the address stored with a persistent-session token, an address recorded as banned, the address a request to reset a password was made from, the counters that enforce rate limits, and, while a Kitguard stop, wait or temporary block is in force, the record of it, which is kept so that a restart does not lift it and is deleted when it ends. The raw IP address is never stored by Clovera; only its irreversible digest is retained. These records are used for account security, unauthorized access detection, and enforcement purposes.

Clovera also offers an optional persistent session feature, offered at login as "Keep me signed in on this network". When a user selects it, Clovera places a device token in a cookie on that browser and stores a digest of that token, together with a one-way digest of the address the user was connecting from, against the account. The session is restored when that browser returns and presents the token. Users should understand that restoration is not in fact limited to the same network: the device cookie alone restores the session, from any address. The address digest stored with the token is not used to restore the session; it is kept so that, if the account is later banned, the same address can be refused. Section 13 of the Privacy Policy sets this out in full. Because the cookie alone restores the session, a user should not enable this feature on any device that is not under their exclusive control, and Clovera strongly recommends against it on shared or public devices. The raw IP address is never stored; only its one-way cryptographic digest is retained. The feature may be turned off at any time by logging out, by signing out of all other devices, or by revoking the individual token in Settings → Sessions.

4. Prohibited Conduct
Users must not use Clovera to:
(a) violate any applicable law or regulation;
(b) engage in fraud, phishing, impersonation, or scams;
(c) harass, threaten, stalk, bully, or abuse others;
(d) distribute malware, malicious code, or harmful files;
(e) share or promote child sexual exploitation material or exploit minors in any way;
(f) promote, support, organize, glorify, or recruit for terrorism or violent extremist activity;
(g) traffic illegal goods, services, or contraband;
(h) attempt to interfere with the security, stability, or operation of the platform;
(i) send spam, bulk unsolicited messages, or manipulate the service through bots without permission;
(j) infringe intellectual property or privacy rights.

5. User Content
Users may create, upload, send, or post content, including text, media, profile information, and messages. Users retain ownership of content they own. Before posting, users should be clear about who will be able to see what they write: a post marked public, a published blog article and the front page of a publicly listed community can be read by anyone on the internet without an account and are offered to search engines, and the channels and forums inside a publicly listed community can be read by anyone who has the link. Section 14 of the Privacy Policy sets out exactly what is readable by whom, and Section 8 of these Terms explains which content is stored in a form the operator of the service can read. By submitting content to Clovera, users grant Clovera a non-exclusive, worldwide, royalty-free license to host, store, reproduce, adapt for technical formatting, display, and transmit that content solely as needed to operate, secure, improve, and provide the service.

6. Responsibility for Content
Users are solely responsible for content they post or send and for the consequences of that activity. Clovera does not endorse user content and may not pre-screen all content.

7. Moderation and Enforcement
Clovera uses automated tools, user reports, and human review to detect and address violations. Automated content review runs on the categories of content listed in the Privacy Policy and may block, remove, or restrict content without prior human review; a user may contest such a decision and ask for human review by writing to kitteniversestudios@gmail.com. Automated review also looks, at intervals, for accounts used for spam, for communities and groups set up to deceive or to organise attacks, and for coordinated attacks, in the manner the Privacy Policy describes; it may place a community on hold — hidden from discovery and closed to new members, its existing members unaffected — until a human administrator has looked at it, and that hold is reversible. Automated review also includes the serious-crime screen described in Section 8, which flags what falls within the closed list of categories that screen covers: what is written in a community's channels wherever it is written, and never a direct or group message. A flag removes nothing, restricts nothing, places no community on hold, and opens a case for a human administrator. Automated review never suspends or terminates an account, closes a community, dissolves a group, or removes a private message; those decisions are taken by a human administrator. Clovera may remove content, restrict features, suspend accounts, terminate accounts, preserve records where appropriate, and take other reasonable enforcement action to protect users, the platform, and legal compliance. In serious cases, action may be taken without prior notice.

Kitguard. Clovera runs an automated check, Kitguard, that stops a connection or an account whose behaviour strongly suggests automated abuse — requests arriving faster than a person can make them, sign-in attempts that continue after a lock-out, registrations beyond the limit for one address, probing for weaknesses — including requests carrying well-known attack patterns, request methods no browser sends, requests for the administration pages by anyone who is not an administrator, and following a link hidden from people — repeatedly running into the limits on posting and messaging, or content of a new account that automated review keeps blocking — and asks it to pass a verification before it continues. A single mistyped password, typing quickly, or a mistake by automated review on an established member's content is not counted. A signed-out visitor is assessed by the address they connect from until their browser has passed the verification, and then by what that browser does; a signed-in account by its own behaviour, and, while the account is new, also by requests from its address that arrive too fast or probe for weaknesses. Nobody is stopped because of sign-in failures or limits reached by others who share their address. Passing the verification lifts the stop at once. It has to be passed within five minutes of the page first being shown; a visitor who does not is asked to wait, ten minutes the first time and at most an hour, and then gets a new five minutes. Where the stop is on an address, that clock runs for each browser separately. Repeated stops of a browser used without signing in lead to a short wait of at most an hour; a signed-in account that is stopped again after passing the verification three times within an hour is referred to an administrator instead, who decides whether anything is done under these Terms; and an address that keeps sending requests while it is stopped may be refused for a limited time, never more than a day, unless someone has passed the verification from it within the last hour, and without any account being affected. While the operator has switched on attack mode, every visitor who is not signed in is asked to pass the verification before entering. Kitguard never restricts, suspends or terminates an account and never removes content. The page shows a reference code, and a user who believes they were stopped wrongly may send it to kitteniversestudios@gmail.com and ask for the stop to be looked at by a person. Section 12 of the Privacy Policy describes what Kitguard counts and how briefly it keeps it.

New accounts. For a period after registration — 24 hours unless the operator sets another — an account cannot post links or upload files, can send direct messages only to people who are its friends, who follow it, or who have written to it first, and is checked by automated review before its profile text, profile photo and banner are shown. Where that check cannot be completed at the time, what the account wrote is not published and it is asked to try again shortly. Where the operator has switched it on, such an account also cannot join a community until it has completed the probation the service already applies before an account may create one, which is completed by writing a few posts or blog articles of its own. When the service is under strain the operator may pause new registrations, lower the number of accounts that can be registered from one address, and change these limits or the length of the period; the registration page says when registrations are paused.

Reported posts and comments. A post or a comment reported by several established members — five unless the operator sets another number, or two where its author's account is new — is taken down automatically and placed before a human administrator, who restores it if the reports were wrong. An established member, for this purpose, is an account at least seven days old that has completed the new-account period; reports from accounts that are newer, or that have not completed it, are not counted toward that number, several reporting accounts registered from the same address or used from the same browser count as one, and content written by administrators is not taken down this way. The reporters are told that their reports were acted on, and the author may contest the take-down in the way the DSA Information document describes.

8. Private Messaging and Safety Review
Clovera provides direct messaging, group messaging, community channels, one-to-one calls, and voice channels in which members can speak and share a screen. Only direct messages between two people are stored encrypted; group messages, community channel messages, forum threads and replies, and polls are stored in plain text, so that they can be examined when they are reported, when a community is being investigated for organising abuse, and when a lawful order requires it. Section 8 of the Privacy Policy sets this out in full, and a user should treat anything written to a group or in a community as content the operator of the service can read. General automated content review — the review that judges whether content breaks the platform rules — does not run on a user's direct messages or group messages, and in a community it runs only where that community has switched moderation on; the categories it covers are listed in the Privacy Policy. Separately from it, Clovera runs a serious-crime screen, described in full in Section 15(e) of the Privacy Policy. It covers what is written in a community's channels — messages, forum threads and forum replies — wherever it is written, and a community's own moderation setting does not reach it: the owner of a community cannot decide that the place they run is not screened for grave crime, and only the operator of the service can switch that screen off, for the whole service. It never covers direct or group messages, and no setting extends it to them. The screen asks one question only, whether a piece of text is a step in organised or other grave crime within a closed list of categories; it is not general moderation and does not act on insults, hate, harassment, or other unpleasant but non-criminal content; it never opens a file attached to anything; it keeps nothing where no category is found; and it cannot delete anything, block its delivery or publication, place a community on hold, or restrict an account. Where it does find a category, what was written stays where it was written, and a case is opened for a human administrator, who decides whether to remove it and whether any enforcement follows. The name of a group chat is covered, and the number of distinct people an account sent direct messages to, whether they wrote back, and whether they blocked the sender are counted for spam detection without the messages themselves being read. Private and group messages are read by a human administrator only where they are reported or where review is otherwise reasonably necessary for safety, abuse prevention, or legal compliance. Separately, as Section 9 explains, a conversation is transmitted to the AI provider when a participant in it uses an AI feature on it. Calls, voice channels and screen sharing stand outside all of this. What is spoken in a call and what is shown on a shared screen are not recorded, not stored, and not reviewed, by an automated system or by a person: every participant's stream passes through Clovera's own server, which forwards it to the others and keeps no copy, and is sent to no third party. Because it is forwarded by that server rather than passing directly between the participants, it is not end-to-end encrypted, and a user should treat a call as a conversation carried by the operator of the service rather than one the operator cannot reach. What Clovera keeps is a record that a call took place and, while it lasts, who is in a voice channel; Section 8 of the Privacy Policy sets this out in full. Since nothing is retained, a report about what someone said in a call can be acted on only through what the person reporting it can show, and Clovera may restrict or remove access to calls and voice channels in response to such a report.

Clovera may extend automated review to further categories of content in future; where that materially changes the processing, the Privacy Policy will be revised and acceptance sought before it takes effect. Where the operator disables the serious-crime screen for communities, or enables it again, the state of that switch is reflected in the Privacy Policy and in the service.

9. KittenAI and AI Features
Clovera includes built-in artificial intelligence features under the name "KittenAI", including conversation summaries, message translation, Live Translation, reply suggestions, Catch-Up digests, the KittenAI chat assistant, writing assistance, the translation of live captions in voice channels, and automated content moderation. The chat assistant can look something up on the web while answering, unless the operator has switched that off, and where it does so the substance of the question reaches Anthropic's web search tool, and any search provider it engages, as well as the model, and the pages the answer came from are shown under it. No other KittenAI feature can search, so nothing a user wrote to somebody else is turned into a search query; Section 15(b-bis) of the Privacy Policy sets this out. KittenAI is powered by Anthropic's Claude models, accessed through the Claude API, and content submitted to these features is processed by Anthropic, PBC as a third-party processor.

By using a KittenAI feature, the user instructs Clovera to read the relevant content on its servers — decrypting it first where it is stored encrypted — and transmit it to Anthropic for processing. Live Translation is an optional setting that the user may turn on or off at any time; when enabled, incoming messages in the user's conversations are transmitted for translation. Automated content moderation runs without a specific user request. It applies to feed posts and post comments — including posts that are not public — blog articles, usernames, profile text, profile photos, banners, server icons, post attachments, messages sent by creator bots, the name, description, welcome message, and channel names of a community, the name of a group chat, and, where a community has enabled moderation, messages and forum posts in that community's channels. It does not apply to a user's private messages or group messages, and neither does the serious-crime screen described in Section 8 or any other automated review. No KittenAI feature is applied to a call or a shared screen, and Clovera transmits nothing spoken or shown in a call, a voice channel or a shared screen to the AI provider. Where a voice channel has switched on live captions, each speaker's own browser writes down what they say, using its own speech recognition, which may be its vendor's speech service; Clovera receives only that text, keeps it for at most six hours, and gives it to KittenAI only to translate it for someone in the channel who reads another language. Section 15(b-ter) of the Privacy Policy sets this out.

Users acknowledge that content they send in a conversation may be processed by KittenAI when another participant uses an AI feature on that conversation (for example, translation, summarization, or Catch-Up), or when the content is subject to automated safety moderation.

AI-generated output (including summaries, translations, suggestions, and moderation decisions) may be inaccurate, incomplete, or inappropriate, and is provided for convenience only. It does not constitute professional advice, and Clovera does not guarantee its accuracy. Users may contest an automated moderation decision by contacting kitteniversestudios@gmail.com. AI features may be rate-limited, modified, suspended, or discontinued at any time. Details of the personal data processing involved are described in the Privacy Policy and GDPR Notice.

10. Blocking, Reporting, and User Controls
Users may be offered tools to block, report, mute, or restrict contact from other users. Clovera may rely on reports and block patterns as safety signals when enforcing platform rules.

11. Service Availability
The service is provided on an "as is" and "as available" basis. Clovera may modify, suspend, or discontinue part or all of the service. Where a change removes or materially limits a feature users rely on, or where the service is to be discontinued, Clovera will give reasonable advance notice inside the service unless it is prevented from doing so by a legal requirement, a security incident, or a circumstance outside its control; where the service is discontinued, that notice will allow a reasonable period in which users can retrieve or delete their content. Clovera does not guarantee uninterrupted availability, error-free operation, or permanent retention of content, and users should keep their own copies of anything they would not want to lose.

12. Termination
A user may stop using Clovera at any time. A user who wants their account and its data erased can do so from the account settings, under "Delete account"; the erasure is carried out immediately and cannot be reversed. Confirming it requires the account password and the account's own username, and an account that owns a community with other members in it must first hand that community over to another member or close it, so that a community is not taken down with the account that happened to create it. The Privacy Policy describes what is erased and what may be retained. A user who cannot reach the control may still send a request to kitteniversestudios@gmail.com from, or while signed in to, the account concerned, and it will be carried out manually. Clovera may suspend or terminate an account if the user violates these Terms, creates risk or liability, harms others, abuses the service, or if continued provision of the service is no longer feasible. Where content a user posted or sent is removed by an administrator, the user is told inside the service, on which ground, and how to have the decision reviewed. A user whose account is suspended or terminated is told the reason, unless telling them would obstruct the prevention or investigation of a serious offence or is prohibited by law. In either case the user may contest the decision and ask for it to be reviewed by a person, by writing to kitteniversestudios@gmail.com; the DSA Information document describes that route. Suspension or termination is not used as a way to avoid an obligation Clovera owes the user under these Terms or under applicable law.

13. Disclaimer of Warranties
To the maximum extent permitted by law, Clovera disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation.

14. Limitation of Liability
To the maximum extent permitted by law, Clovera will not be liable for indirect, incidental, consequential, special, exemplary, or punitive damages, or for loss of profits, data, goodwill, or business opportunities arising from use of the service. Nothing in these Terms excludes liability that cannot lawfully be excluded.

15. Indemnity
Where permitted by law, users agree to indemnify and hold harmless Clovera from claims, liabilities, losses, and reasonable expenses arising from their misuse of the service, content, or violation of these Terms.

16. Governing Law and Disputes
Unless mandatory local consumer law provides otherwise, these Terms are governed by the laws of the Republic of Türkiye. Courts located in Türkiye will have non-exclusive jurisdiction, subject to any rights a consumer may have under mandatory law in their country of residence.

17. Changes to These Terms
Clovera may update these Terms from time to time. Where a change is material, Clovera will ask each user to review and accept the updated Terms before continuing to use the service, and will identify the substance of the change at that point. Access to the service is withheld until that acceptance is given; a user who does not wish to accept may instead stop using the service and request erasure of the account as described in Section 12. For changes that are not material, such as corrections of typographical errors or clarifications that do not alter any party's rights or obligations, Clovera may publish the revised Terms with an updated revision date without seeking renewed acceptance.

Each revision is identified by the revision date shown at the top of this document.

18. Contact
Questions about these Terms may be sent to kitteniversestudios@gmail.com.