Submission is free. Publication, ranking, and badges are not guaranteed.

Submission

Submit an app without an account

The public submission form accepts an app URL without requiring an account or payment. CurioBeam may match that URL to an existing app instead of creating a duplicate, and the submission enters editorial review rather than publishing automatically.

Submit an app →

Boundaries

What submission does not do

Submission does not automatically publish or index an app, set verified product facts, grant a badge, set an editorial score, or boost organic ranking. CurioBeam independently decides those outcomes under the same editorial and evidence rules used for other products.

Maker accounts

Signing in is identity, not ownership

CurioBeam's gated Maker workflow uses passwordless email sign-in. Creating or signing into a Maker account does not establish ownership or control of any app and grants no app-scoped authority by itself.

When Maker authentication is enabled, the app page can offer a Claim this app entry point. A claim is a request for review, not an automatic verification or transfer of the listing.

Claims and proof

Proof is reviewed; authority is explicit and app-scoped

A Maker can submit bounded proof references such as an official website/DNS/work-email domain, an official GitHub organization/repository label, or a manual-review request. Do not send passwords, API keys, OAuth tokens, DNS challenge secrets, inbox contents, or other credentials through the claim form.

Proof strength and review status remain reviewer-controlled. Even an approved claim does not itself grant editing, analytics, publishing, indexing, ranking, scoring, badge, or editorial-conflict authority. Protected Maker capabilities require a separate live authorization record for the exact app and permission scope.

Shared products

Authorization is not a one-owner shortcut

CurioBeam's authorization model supports more than one authorized Maker for an app and more than one app for a Maker. A work email or shared company domain is not treated as automatic authority over every product associated with that domain.

Authorizations can be revoked or expire. Future protected operations re-check the current server-side grant rather than relying on an old browser state or a previous approval decision.

Corrections

Maker proposals do not overwrite editorial truth

Authorized Makers can provide factual corrections and stronger evidence through scoped workflows as those surfaces are enabled. A correction remains an attributable proposal until CurioBeam reviews it; it does not directly mutate CurioBeam's curated public facts.

CurioBeam should correct factual errors when the evidence supports the change. Disagreement with an editorial judgment, by itself, does not require CurioBeam to change that judgment.

Editorial independence

Maker access cannot publish, rank, score, or self-verify

Maker permissions do not include publishing/unpublishing, index/noindex decisions, ranking, scoring, badges, self-verification of submitted evidence, or resolution of material editorial conflicts. Those remain CurioBeam editorial/admin responsibilities.

Contact

Report an error or send evidence

Until a relevant Maker correction surface is enabled, factual corrections and supporting evidence can be sent to hello@curiobeam.com.