Acceptable Use Policy (Community Guidelines)

Kaegora

Last updated: 24 July 2026

This Acceptable Use Policy (“AUP,” “Community Guidelines,” “this Policy”) describes the standards of behavior expected from everyone using Kaegora. It works alongside our Terms and Conditions, the Terms set out the legally binding rules; this Policy explains, in plain language and with concrete examples, what those rules mean in day-to-day use of the App.

This Policy is incorporated by reference into our Terms and Conditions and forms part of the agreement between you and Mentheris SRL. By using the App, you agree to follow this Policy.

Quick Summary

If you read nothing else, read this:

• Be real. Real name, real photo, real intentions.
• Be specific. Vague Calls, vague pitches, and vague profiles waste everyone’s time.
• Don’t route around the platform. No off-platform payment requests, no using contact details outside their intended purpose.
• Don’t game the system. No fake collaborations, no fake appreciations, no manipulating scores or algorithms.
• Close things properly. Don’t ghost an active collaboration, use the closing flow.
• Report, don’t retaliate. If something’s wrong, tell us. Don’t take it into your own hands.
• One person, one account. No creating multiple accounts to bypass limits, inflate your own reputation, or work around a block.
• Credit real contributions only. Don't tag co-authors who didn't contribute, and don't cite sources inaccurately just to look more credible.
• Respect the process. The two-stage confirmation flow exists for a reason, don't pressure a collaborator to skip it or share contact details early.
• Adults only, always. Kaegora is for professionals 18 and older.
• No hate, no harassment. Zero tolerance for discrimination, threats, or abuse, toward anyone, in any part of the App.
• Think before you post. Most content is only editable for 10 minutes, after that, it's effectively permanent.
• Keep your presence honest. Typing indicators, activity status, and "online" signals should reflect real use, not manufactured activity.
• No scraping, no bots. Access the App the way it's meant to be used, not through automated tools extracting data or actions.
• Messages are for collaboration, not cold pitches. Don't use Direct Messages or Collaboration Workspaces to send unsolicited offers unrelated to the actual collaboration.

The rest of this document explains what each of these means in practice, area by area.

1. The spirit of Kaegora

Kaegora exists to remove the friction between having an idea and finding the right person to build it with and, just as importantly, to give people a space to think, share, and build knowledge together, not only to transact collaborations. It is not another feed to scroll through, not a shortcut to free labor or cheap leads, and not a place to perform expertise for its own sake.

The platform is built for different kinds of people who all want the same thing at heart: Knowledge Builders who produce and structure ideas, Applied Innovators who turn ideas into real projects, and Reflective Professionals who value depth over small talk. Whichever of these describes you, the same standard applies:

Be the kind of collaborator and contributor you would want to work and think alongside.

Concretely, that means:

• Showing up with real intent, whether you're looking for a project partner or genuinely working through an idea
• Being honest about who you are, what you're offering, what you're genuinely looking for, and what you actually know
• Treating other people's time, ideas, and contact information with respect
• Sharing thoughts, questions, research, and experience in the Community Feed, and contributing to the Knowledge base, because you have something genuinely worth adding, not just to build visibility or metrics
• Giving credit where it's due: to co-authors, to cited sources, to people whose ideas you're building on
• Letting your Trust Level, Compatibility Score, and other reputation signals reflect real behavior, the platform is built on the idea that every active user earns a genuine, verifiable trust footprint, not an inflated one

We deliberately favor quality over volume. Features like application limits, rate-limited connection requests, and the reporting system exist so the platform stays a low-noise space for people with genuine intent, not a place optimized for maximum activity at any cost. If a guideline in this Policy ever seems to slow you down, that's usually the point: it's protecting the quality of the space for everyone, including you.

This Policy applies across every part of the App: your profile, Calls, applications, Collaboration Workspaces, Direct Messages, the Community Feed, the Knowledge base (including collaborative reading lists), your interactions with other Users in People & Network, and the notifications you generate for others. These guidelines apply equally whether you use the Free or Pro tier, subscription level changes what features you have access to, never what behavior is expected of you.

2. Your profile and identity

2.1. Real identity, real representation

Use your real name (or the professional identity you genuinely operate under) and a real, current photo of yourself. Fake profiles, stock photos, images of other people, or AI-generated faces intended to mislead others are not permitted. A genuine photo isn't just a formality - profiles without one see dramatically lower connection and collaboration rates, because a visible identity is central to how trust works on this platform.

Your biography, domains, focus areas, and "Looking For" / "I Can Contribute" fields should reflect your actual situation, not an aspirational or exaggerated version of it. Your username should also be a genuine, non-misleading identifier - not one designed to impersonate another person, brand, or organization.

2.2. Work email verification

A verified badge means only that you have access to an email address on that domain. It does not mean you hold a specific title, seniority, or authority within that organization.

Do not imply a role or authority you don't actually have just because your domain is verified. If your affiliation changes, update or remove the verification.

2.3. Company and institutional presence

If you post under a company or organizational identity, make sure you are actually authorized to represent that organization.

Your personal Trust Level, appreciations, and responsiveness stay tied to you as an individual - they are never transferred to, or borrowed from, an organization you post on behalf of.

Misrepresenting your affiliation, or posting under a brand you have no real connection to, damages trust for everyone on the platform and will be treated as a serious violation.

2.4. Availability and collaboration intent

Keep your Collaboration Intent (e.g., "Actively seeking," "Open to ideas," "Not now") honest and current. Leaving it permanently on "Actively seeking" when you have no real intention of collaborating creates noise for people who are genuinely trying to find someone available - the opposite of what this platform is for.

Using Quiet Mode or an "Invisible" availability status is completely legitimate. Stepping back from visibility for a while doesn't require an explanation, and isn't itself a red flag.

Examples of what's not allowed:

• Creating a profile with a celebrity's photo or a name that isn't yours
• Claiming a "Senior" title on a Call when your verified work email only confirms you work at the company, with no seniority claim behind it
• Posting Calls under a well-known company's name without any real affiliation
• Keeping your Collaboration Intent set to "Actively seeking" for months while consistently ignoring or declining every application you receive, with no real interest in collaborating

(Legal basis: Terms, Sections 3-5)

3. Posting calls

A Call should give someone enough information to genuinely evaluate whether they want to apply. Before publishing, ask yourself: would I apply to this, based on what’s written here?

3.1. Do

• Be specific about the role needed, compensation type, expected duration, and start date
• Describe the project honestly, including its current stage and any constraints
• Keep your Call updated: archive it once you've filled the spots you need, or once it's no longer relevant
• Use the domain and skill tags accurately, so the right people find it
• If you attach recommended Knowledge base resources, make sure they're genuinely relevant background reading for applicants

3.2. Don’t

• Post vague, exaggerated, or misleading Calls designed to attract applications you don't intend to seriously consider
• Ask applicants to pay you, or arrange to pay collaborators outside the platform in a way designed to bypass Kaegora's subscription model, our automated screening actively checks for this pattern at publication, and repeated attempts to reword around it will be treated as a deliberate violation
• Publish the same Call repeatedly, or post near-identical Calls across multiple domains simply to increase visibility
• Use a Call as a disguised advertisement for a product or service rather than a genuine collaboration opportunity
• Set an unrealistically short deadline solely to create artificial urgency, when there's no real time constraint behind it
• List more open spots than you genuinely intend to fill, just to make the Call appear more active or popular than it is
• Attach Knowledge base resources that aren't genuinely relevant, to promote unrelated content

3.3. Quality matters, not just compliance

Calls with vague descriptions get fewer, weaker applications, that’s not a guideline, it’s just how the platform works. But quality also matters for the community as a whole: a feed full of low-effort Calls makes Kaegora less useful for everyone. Take the extra two minutes to write a clear one.

(Legal basis: Terms, Sections 7.1(a)-(b), (j); Section 9; Section 7.2 on automated screening)

4. Applying to calls and sending invitations

Every application is a real ask for someone’s time and attention. Treat it that way, especially since Free-tier accounts have a limited lifetime number of applications.

4.1. Do

• Write a pitch that shows you actually read the Call and understood what's needed
• Only apply to Calls where you have a genuine interest in collaborating
• If you're re-applying after a rejection, use the opportunity to improve your pitch, not just resend the same one unchanged
• Keep any links or attachments you include genuinely relevant to your application, a portfolio, a related project, or something that supports your pitch

4.2. Don’t

• Mass-apply to Calls without reading them, hoping something sticks
• Use the direct collaboration invitation feature to repeatedly cold-pitch people who have shown no interest in working with you, this is treated the same as unsolicited spam, regardless of how the message is worded
• Treat an accepted application as a guaranteed, binding outcome, it is the start of a structured conversation (the two-stage confirmation flow), not a signed agreement
• Include misleading, irrelevant, or deceptive links or attachments in your pitch

4.3. Withdrawing

If you’re no longer interested in a Call you applied to, withdraw your application rather than leaving the owner waiting indefinitely, even though withdrawal still counts against your Free-tier application limit, it’s the respectful thing to do.

4.4. If you're the one receiving applications

Posting a Call comes with its own responsibility. Review applications in good faith, and respond within a reasonable time, a pending application is someone waiting to hear from you.

• Don't leave applications pending indefinitely just to keep a Call looking active without any real intention of accepting someone
• If you're not interested, use "Reject with feedback" or "Reject silently" rather than leaving someone in limbo
• Don't use "Ask a few questions first" repeatedly as a way to stall applicants without any genuine intent to move forward

(Legal basis: Terms, Section 7.1(j); Section 9)

5. Inside a collaboration workspace

Once you’re in a workspace with someone, you’re in a shared space built on the expectation that you’re both serious about working together.

5.1. Do

• Respond within a reasonable time. Your Trust Level and any “Responsive Owner” badge reflect this, but more importantly, it’s simply respectful of the other person’s time
• Be honest during the Agreement stage about scope, timeline, and expectations, this is the moment to raise concerns, not after contact details have been unlocked
• Use the formal “Close Collaboration” flow if things aren’t working out, with a clear, honest reason, rather than going silent

5.2. Don’t

• Use contact details shared inside a workspace for anything beyond that specific collaboration, without the other person's consent, for example, adding someone to a mailing list, or contacting them about an unrelated opportunity, without asking first
• Disappear from an active collaboration without formally closing it, your partner deserves to know where things stand, and the platform's stale-collaboration detection exists precisely because this happens
• Try to edit an agreement after your partner has already confirmed it, hoping the change goes unnoticed, editing resets both confirmations specifically to prevent this
• Send repeated nudges when your partner has clearly indicated they're no longer available, the 24-hour limit is a technical cap, not a target
• Use workspace notes to build a one-sided record against your partner instead of raising concerns with them directly
• Add resources to a shared workspace that aren't genuinely useful to that specific collaboration

5.3. Pause vs. Close

Pausing a collaboration is meant for genuine temporary breaks, not as a permanent way to avoid a proper closure. If a collaboration isn't going to continue, use "Close Collaboration" honestly, rather than leaving it paused indefinitely to avoid the conversation.

5.4. Appreciations

Appreciation messages contribute to someone's Trust Level and public reputation, give them honestly, based on the actual collaboration. Don't give an inflated appreciation as a favor, and don't withhold or weaponize an appreciation out of frustration unrelated to how the collaboration went.

5.5. A note on disagreements

Not every collaboration works out, and that’s fine, the “Partial success,” “Pivot,” and “Cancelled” outcomes exist because real collaboration doesn’t always go as planned. What matters is closing things honestly and respectfully, not the outcome itself.

(Legal basis: Terms, Sections 6.4, 7.1(m), 9–10)

6. Contributing to the community feed

The Community Feed works because people share things worth reading, not because everyone posts constantly. Quality and genuine intent matter more than volume.

6.1. Choosing the right post type

• Thought: a reflection or opinion that adds something to a conversation
• Question: something you genuinely want input on, not a rhetorical setup for self-promotion
• Research: a finding, method, or study summary you can actually back up
• Experience: a concrete story with a real, specific lesson

Using the wrong type to game visibility (e.g., dressing up an ad as a “Thought”) undermines the feed for everyone.

6.2. Research posts, a higher bar

Because Research posts carry academic weight and citation tracking, they come with extra responsibility:

• Only tag people as co-authors who genuinely contributed to the work. Tagging someone purely for visibility or reciprocity, without real involvement, is a misuse of the co-authorship feature, and remember, the tagged person must explicitly accept before it appears on their profile
• Cite your sources accurately. Citation counts and “cited N times” indicators are meaningful signals other researchers rely on, don’t inflate them through inaccurate, circular, or self-serving citations
• If your research evolves, use the edit and versioning system honestly, don’t quietly rewrite conclusions and hope no one checks the version history

6.3. Question posts

• Check whether a similar question already exists before posting a duplicate, the App will suggest similar questions before you publish
• If your question gets a good answer, mark it as answered. It helps every future reader, not just you

6.4. Experience posts, honesty about outcomes

The value of an Experience post comes from its honesty, including when things didn't go well. Don't only post polished success stories while omitting failures, and don't misrepresent how a collaboration or project actually ended just to make yourself look better. A well-told failure or "Pivot" is often more valuable to readers than a curated success.

6.5. Reply settings and polls

Restricting who can reply, or requiring approval, is a legitimate way to manage your own space, but don't use these settings repeatedly to make provocative or questionable claims while shielding yourself from any pushback. If you're not open to being challenged on something, consider whether it belongs in a more private format.

When creating a Poll, design it to genuinely learn what the community thinks, not to construct a set of options that predetermines the answer you want.

6.6. What’s not allowed, across all post types

• Purely promotional or advertising content disguised as a Thought, Question, Research, or Experience post
• Exaggerated, misleading, or clickbait titles designed to drive engagement rather than genuine interest
• Flooding the feed with near-identical posts, or reposting the same content across multiple post types
• Using reactions or comments in bad faith to inflate engagement on your own or a coordinated group’s content

(Legal basis: Terms, Sections 6.8-6.9; Section 7.1(b)-(c), (k))

7. Contributing to the knowledge base

The Knowledge base is a shared resource maintained collaboratively, treat additions to it the way you’d want others to treat it.

7.1. Do

• Add resources you'd genuinely recommend to a colleague working in that domain
• Write an accurate, useful overview in your own words, not a copy-pasted abstract
• Write academic notes (Insight, Critique, Question, Extension, Application) that genuinely engage with the resource, not just to accumulate a note count
• Use "Suggest an edit" constructively when you spot an error or a gap, rather than just flagging the resource
• Keep reading lists organized and clearly described, especially collaborative ones shared with others

7.2. Don’t

• Add resources you don't have the right to reference or link to (see Terms, Section 6.7, on your responsibility for third-party rights)
• Submit knowingly false or bad-faith quality flags to push down a resource you have a personal or professional disagreement with, the flagging mechanism exists for genuine quality issues (misleading titles, wrong categorization, poor detail), not for settling disputes
• Post a "Critique" or other note in bad faith, without a genuine intellectual basis, to discredit a resource or its author
• List yourself as an author or contributor on a resource you didn't meaningfully work on
• Add resources to a collaborative reading list that aren't genuinely relevant to its stated theme, simply to gain visibility from being included in it
• Suggest a replacement URL for a "dead link" that isn't a genuine, accurate replacement
• Use the export feature to redistribute other Users' academic notes or contributions as if they were your own work

8. Connections and networking

• Send connection requests to people you have an actual, articulable reason to connect with, a shared domain, mutual interest in a Call, something in their profile or content that resonated with you
• If someone declines or ignores your request, respect that. Don't use the direct collaboration invitation feature, or a new account, as a workaround to reach them anyway
• Don't try to work around the 14-day cooldown after withdrawing a request, for example, by creating a new account or sending a direct collaboration invitation instead
• If you're a Pro user, use the personal message feature on connection requests to genuinely explain your interest in connecting, not as a vehicle for sales pitches or marketing messages
• Sending connection requests up to your monthly limit as a matter of routine, rather than because you have a genuine reason for each one, defeats the purpose of the limit and may be treated as spam-like behavior
• Blocking is available any time you need it, with no explanation required, and it's private, it won't notify the other person
• Reporting is there for when something needs our attention, not just yours. Reporting and blocking are separate tools for separate purposes, use whichever fits the situation, or both

(Legal basis: Terms, Sections 7.1(j), 11)

9. Respectful conduct toward other users

This applies everywhere on the platform, profiles, Calls, messages, comments, and notes:

• No harassment, threats, hate speech, or discrimination on the basis of race, ethnicity, nationality, religion, gender, sexual orientation, disability, age, or any other protected characteristic
• No sexual content or unwanted sexual attention in any context
• No coordinated harassment, brigading, or organizing against another User off-platform
• Harassment doesn't need to happen in one place to count, a pattern of hostile behavior spread thinly across messages, comments, notes, and reactions toward the same person is still harassment, and we assess it as a pattern, not as isolated incidents
• Disagreement, critique, and challenge are welcome, especially in Research and Question posts, but they must be directed at ideas and work, not at people. Repeated, disproportionate "Critique" notes or hostile comments targeting the same person's work, beyond what genuine intellectual disagreement would call for, may be treated as harassment rather than legitimate critique

(Legal basis: Terms, Section 7.1(d))

10. Automated systems, don’t try to game them

Kaegora relies on several automated systems (Trust Level, Compatibility Score, Contributor Tiers, and others described in Terms Section 8) to help people find genuinely compatible collaborators. These systems only work if they reflect real behavior.

Not allowed:

• Coordinating with others to exchange fake appreciations or manufacture completed collaborations
• Creating multiple accounts to inflate your own reputation signals, saves, or reactions
• Deleting and recreating accounts to repeatedly exploit the temporary "New" account visibility boost
• Responding quickly but superficially to applications solely to preserve a "Responsive Owner" badge, without genuinely evaluating them
• Coordinating with other Users to exchange Call boosts, applications, or saves purely to manipulate visibility or Compatibility Score signals, rather than out of genuine interest
• Attempting to reverse-engineer or probe the scoring logic behind Trust Level or Compatibility Score in order to exploit it
• Any other attempt to manufacture signals that don't reflect genuine platform activity

We assess this kind of behavior based on patterns, not just isolated incidents, a string of small, technically-within-limits actions that add up to gaming the system will still be treated as a violation.

(Legal basis: Terms, Sections 7.1(k)-(l), 7.3, 8)

11. Enforcement

We look at behavior in context. A single honest mistake is rarely the issue, patterns of behavior are what we act on, though severe individual incidents (harassment, fraud, impersonation) can result in immediate action.

This table is illustrative, not exhaustive, the specific action taken depends on severity, intent, and impact on other Users, at Mentheris's reasonable discretion.

These standards apply equally to Free and Pro users. An active subscription does not affect how a violation is assessed or enforced.

If your account is suspended or terminated, you have the right to appeal within 30 days, as described in our Terms and Conditions, Section 18.5. The same appeal right applies to a decision to remove or restrict specific content (a Call, a post, a resource) without a broader account action, as described in Terms, Section 12.5.

(Legal basis: Terms, Sections 7.4, 18)

12. Reporting concerns

If you see something that doesn't sit right, a fake profile, a misleading Call, harassment in a Collaboration Workspace or Direct Message, an abusive comment, report it.

Reporting is:

• Directed to our moderation team, not just a personal action (unlike blocking)
• Not immediate removal, reported content stays visible while we review it
• Not going to notify the person you reported, to reduce the risk of retaliation
• The only way something comes to our attention, if you only block someone, we never see it

You can report a User, a Call, an individual message (in a Collaboration Workspace or a Direct Message), a Community Feed post or comment, or a Knowledge base resource, from wherever you encounter it in the App. Each report moves through a review queue (Pending → Reviewed → Resolved or Rejected), and you can't submit more than one report for the same piece of content.

Reporting vs. quality flagging. Reporting is for conduct and abuse issues covered by this Policy. Flagging a Knowledge base resource for quality reasons (a misleading title, wrong category, insufficient detail) is a separate, distinct mechanism, see Section 7.2, and is not a substitute for reporting genuine abuse, nor should reporting be used to settle a quality disagreement.

13. Changes to this policy

We may update this Policy as the platform evolves and as new situations arise. Material changes will be communicated through an in-app notice and/or by updating the “Last updated” date at the top of this document, consistent with how we handle changes to our Terms and Conditions.

14. Questions

If you’re ever unsure whether something is appropriate before you post it, ask us:

MENTHERIS SRL

Email: [email protected]

This document works alongside, and is incorporated by reference into, the Kaegora Terms and Conditions. In case of any conflict between this Policy and the Terms and Conditions, the Terms and Conditions govern.