Community Guidelines
Everything that governs participation in the Opekto Contributor Program. Read this before you submit anything.
Effective date: April 2026
One idea at a time
One active submission per email. 150-word minimum per submission. 30-day cooldown after resolution.
Community votes decide priority
Ideas need to cross the public upvote threshold before entering review. No shortcuts.
Revenue share is not guaranteed
It is a discretionary goodwill payment based on real quality metrics over 3 months, not raw traffic.
Manipulation gets you removed
Fake votes, coordinated traffic campaigns, or spam submissions result in a permanent ban.
We can update these rules
Opekto reserves the right to change these guidelines at any time. The version on this page is always current.
This summary is not the full document. The sections below are what actually govern participation. Read them.
01.Submission Requirements
Before your idea can enter the community queue, it has to meet a basic set of requirements. These exist to keep the review process fair and useful for everyone, not to create unnecessary friction.
Minimum description length
Every submission must include a description of at least 150 words. You need to explain what the tool does, what problem it solves, and who benefits from it. Vague submissions things like "a calculator" or "something for formatting" will be declined without review.
The 150 word minimum is a floor, not a target. A well-written 200 word description that clearly explains the tool, the problem, and the audience will always move faster than a padded 300 word one that says nothing specific.
One active submission per email
You can only have one active submission in the queue at a time per email address. Once your current submission is resolved-whether it is approved, rejected, built, or closed-you can submit another after the cooling period has passed.
30-day cooling period
After a submission is resolved, there is a 30 day cooling period before the same email address can submit again. This applies regardless of the outcome. The purpose is to prevent queue flooding and give each idea the attention it deserves.
Email verification
All submissions require email verification before they become visible to the community. An unverified submission does not appear in the public queue and cannot receive upvotes. The verification link expires after 48 hours. If you miss the window, you will need to re-submit.
Using multiple email addresses to bypass the one-submission limit is considered manipulation and will result in all associated submissions being removed and the emails and IP networks being permanently blocked. See Section 6 for the full consequences.
02.Prohibited Categories
The following types of tools will not be accepted under any circumstances. This list is not exhaustive-Opekto reserves the right to decline any submission that conflicts with platform standards even if it does not appear on this list.
Harmful or illegal content
Tools that generate, assist with, or facilitate content that is illegal, violent, threatening, defamatory, or that could be used to harm individuals or groups.
Adult or explicit content
Tools that generate, display, or process sexual, explicit, or adult-only material of any kind.
Closed third-party services with no free tier
Tools that depend entirely on a paid or closed API where users cannot realistically use the tool without a subscription or paid account. If the tool cannot function for a standard visitor without a cost barrier, it will not be accepted.
Privacy-invasive tools
Tools designed to track individuals, harvest personal data, bypass privacy controls, or surveil users or third parties without clear consent.
Tools with no meaningful audience
Submissions for tools that serve a hyper-niche audience of fewer than a few thousand potential users globally, or that would generate no meaningful organic traffic.
Duplicate submissions
Ideas that are effectively identical to an existing Opekto tool or to a suggestion already in the queue. If your idea adds meaningful new functionality to something that already exists, describe that distinction clearly in your submission.
Tools that conflict with platform standards
Any tool that would violate the content standards required to maintain platform integrity, advertiser relationships, or applicable law. Opekto determines this at sole discretion.
If you are unsure whether your idea falls into a prohibited category, err on the side of submitting and explaining your reasoning in the description. The review team will clarify.
03.Upvote Mechanics
Upvotes are how the community signals which ideas matter. They are the primary way a suggestion moves from the public queue into the admin review stage. Here is exactly how it works.
How voting works
Any visitor to the ideas page can upvote a suggestion without needing to register for an account. To ensure fairness, our systems silently enforce a strict one-vote-per-person policy for every idea. If you change your mind, simply click again to remove your vote.
The upvote threshold
Each idea has a public upvote threshold displayed on its page. When a suggestion crosses that threshold, it becomes eligible to enter the admin review queue. Crossing the threshold does not guarantee review-it makes the idea eligible. Review is conducted in batches and prioritised by the team based on overall demand and build capacity.
The threshold number is configurable and may change over time as the volume of submissions grows. The current threshold is always displayed publicly on the ideas page.
What happens after the threshold is crossed
Once an idea crosses the threshold, its status updates to reflect that it is pending review. The original submitter receives an email notification. From there, the review team assesses feasibility, audience fit, and compliance. You will receive a follow-up email regardless of the outcome.
Voting on built ideas
Once a tool has been built and gone live, voting on that idea is permanently closed. Built ideas remain visible in the archive so the community can see what has been delivered.
Coordinated voting campaigns-asking groups of people to upvote a specific idea in order to game the threshold-are a violation of these guidelines. If detected, all votes associated with the campaign will be removed, the submission will be disqualified, and the submitter's network will be blocked. See Section 6.
04.Traffic Quality Standards
Traffic quality standards exist because raw page views are easy to manipulate. These metrics are designed to measure whether a tool is providing genuine value to real users-not whether a contributor can drive a short burst of traffic from a social post.
These standards apply specifically to the revenue share eligibility determination detailed in Section 5. The Opekto team conducts monthly assessments of these metrics to evaluate sustained performance, and we will proactively contact you directly when your tool meets the required thresholds.
Average session duration
≥ 30 secondsUsers need to spend meaningful time with the tool. Sessions that end in under 30 seconds on average indicate the tool is not providing real value.
Return visitor rate
≥ 15%At least 15% of monthly sessions must be from users who have visited before. Return visits are the clearest signal that the tool is genuinely useful.
Organic search traffic ratio
≥ 60%The majority of traffic must originate from organic search. This demonstrates that the tool solves a persistent, highly-searched problem and delivers compounding, long-term value to the platform.
Unknown traffic cap
≤ 60% in any monthIf more than 60% of traffic in a given month comes from unknown, untraceable, or direct sources, that month does not count toward eligibility. This prevents artificial traffic inflation and bot campaigns from illegitimately qualifying a tool.
Observation window
3 consecutive monthsAll metrics above must be met for three consecutive eligible months. A single good month does not qualify. Consistency is what matters.
Meeting these thresholds does not automatically trigger a revenue share payment. It makes a contributor eligible for consideration. Final determination is at Opekto's discretion as described in Section 5.
06.Spam & Manipulation Consequences
The Contributor Program only works if submissions and votes reflect genuine community interest. Any attempt to game the system-whether through disposable emails, coordinated campaigns, or traffic manipulation-undermines that for everyone. Violations are taken seriously and consequences are applied without warning.
Using multiple email addresses to submit more than one active idea
→ All submissions removed. All associated emails and networks blocked.
Coordinating a group of people to upvote a specific submission
→ All campaign votes removed. Submission disqualified. Submitter's network blocked.
Artificially inflating traffic to a tool page to game quality metrics
→ Tool removed from eligibility for the current and all future cycles. If severe, permanent network block.
Submitting ideas with the intent of promoting a personal product or affiliate link
→ Submission removed. Email reviewed for temporary block.
Resubmitting a rejected idea without material changes
→ Submission immediately declined. Repeated offences result in a block.
Submitting deliberately misleading tool descriptions
→ Submission removed. Email flagged. Repeated offences result in a block.
Harassing, threatening, or abusing Opekto staff or community members
→ Immediate permanent block across all associated IP networks.
For correctable violations, Opekto will issue a formal warning notice outlining the issue and providing a specific time limit to resolve it. If the issue is not corrected within that given window, appropriate platform restrictions will be applied. (Note: Severe or malicious manipulation attempts may result in immediate restrictions).
07.Dispute Process
If your submission was rejected, your email or network was penalized, or you believe a decision was made in error, you can contest it. The process is straightforward.
Contesting a rejection
If your idea was rejected and you believe the decision was incorrect, you can submit a dispute via the contact page within 14 days of receiving the rejection notification. Your dispute must include the original submission reference, the specific reason you believe the rejection was incorrect, and any additional information that was not included in the original submission.
Disputes that simply restate the original submission without addressing the reason for rejection will be declined without further review.
Contesting a ban or penalty
If you believe a ban or eligibility penalty was applied incorrectly, you can submit a dispute via the contact page. Include the email address affected, a description of what you believe happened, and any supporting evidence. Disputes are reviewed within 14 business days.
What disputes can and cannot change
Disputes can result in a rejection being overturned, a penalty being lifted, or a clarification being issued. They cannot result in a guaranteed approval of any idea, a guaranteed revenue share payment, or any form of compensation for the time spent in the dispute process.
Submitting a dispute does not pause the 30-day cooling period or the platform block. If the dispute is resolved in your favour, the relevant restriction is lifted at that point.
08.Banned List Criteria
Blocks are applied at the email level and, where necessary, at the IP network level. There are two categories: permanent bans and temporary blocks.
Permanent ban - zero tolerance
The following result in a permanent block with no eligibility for dispute reinstatement:
Operating multiple email addresses to bypass submission limits.
Running a coordinated upvote or traffic campaign on any submission.
Attempting to manipulate quality metrics used for revenue share determination.
Submitting content that is illegal, harmful, or explicitly prohibited.
Threatening, harassing, or abusing any member of the Opekto team or community.
Deliberately providing false identity or contact information.
Circumventing a previous block through a new email address or IP.
Temporary blocks
The following result in a temporary block from the Contributor Program. Blocks are served before eligibility is restored:
Resubmitting rejected ideas without material changes - 90-day block.
Exceeding submission frequency limits - 60-day block.
Submitting ideas that are misleading but not intentionally fraudulent - 30-day block on first offence.
For privacy reasons, restricted accounts are not publicly listed. If you attempt to submit an idea and receive an eligibility error, please reach out to us through the dispute process in Section 7 so our team can review your account status.
09.Code Contributions
The idea submission process described in this document covers community suggestions only. Contributing code - whether to improve an existing tool, fix a bug, or build something new - is managed through our Code Contributions page.
How to submit a code contribution proposal
Code contribution proposals are submitted through the dedicated contribution page. Your proposal should include your GitHub profile, a clear description of what you want to build or improve, the tool or area of the platform it affects, and a brief technical outline of your approach.
Proposals are reviewed by the team and you will receive a response with next steps, clarifying questions, or a decision. Not all proposals will be accepted - priority is given to contributions that align with the current build roadmap.
Attribution and recognition
Accepted code contributors are credited on the tool page and on the Community contributors page, the same as idea contributors. Revenue share eligibility for code contributors follows the same traffic quality standards and discretionary framework described in Sections 4 and 5.
Ownership
Any code contributed to Opekto becomes part of the Opekto platform. Contributors retain no ownership over contributed code and grant Opekto a perpetual, irrevocable licence to use, modify, and distribute it as part of the platform. This is standard for any closed-source platform that accepts community contributions.
Do not submit code for tools that are currently under active development by the Opekto team without first confirming through the contribution page that the area is open for community contribution. Unsolicited pull requests on active builds will be declined.
10.Changes to Guidelines
Opekto reserves the right to update these guidelines at any time without prior notice. When changes are made, the effective date at the top of this page is updated to reflect the new version. Continued participation in the Contributor Program after an update constitutes acceptance of the revised guidelines.
We will not notify individual contributors of every minor update. Significant changes - particularly those that affect revenue share eligibility criteria, submission limits, or banned list conditions - will be communicated via a notice on the Community page. It is your responsibility to check this page periodically.
The version of these guidelines published on this page at the time of any decision, review, or dispute is the version that applies. Previous versions are not archived publicly.
If you have questions about a specific rule or want clarification before submitting, use the contact page. We will respond.
Ready to shape the platform?
Whether you have a concept for a new utility or want to contribute code directly, choose your path below.