Add the right kind of trust signal
Alkax separates two questions:
- Is this place record accurate and useful?
- Is this account responsible for the place?
Verification and claims answer different parts of that trust problem.
Verify a place
Use an upvote only when you have enough local knowledge to confirm that the arrival point and public details are accurate. Check the pin, name, locality, description, entrance context, and photographs that are relevant to finding the place.
An upvote must be independent to count towards trusted progression. Upvoting your own place does not earn points or make it trusted for coverage.
The first valid independent upvote:
- changes the creator's contribution from pending to validated for progression;
- awards the creator 10 Impact Points;
- awards the verifier 5 Impact Points;
- allows the active place to contribute to illuminated map coverage;
- can advance eligible campaign and badge progress.
Additional independent upvotes can strengthen community confidence, but the creator is not awarded another 10 points for the same place.
Verification is evidence of local confidence. It is not legal certification, proof of ownership, or a guarantee that a place is suitable for a high-stakes journey.
Flag a problem
Flag a place when it is misleading, duplicated, unsafe, inappropriate, or located incorrectly. A flagged place may move into review or become hidden, depending on the moderation outcome.
Use the most specific available reason. Do not include sensitive personal information in a public report, and do not use flags to target another contributor or influence campaign rankings.
Moderation and reversals
Trusted progress is not permanent when its supporting contribution ceases to be valid. If a place is hidden, removed, or placed under review, Alkax can recompute:
- creator and verifier Impact Points;
- leaderboard position;
- campaign totals and reward eligibility;
- Pro time previously granted through a campaign.
A reward may become Blocked while work is disqualified or Reversed if it had already been earned or granted. This protects the integrity of the network and discourages coordinated or fraudulent voting.
Control a place profile
A claim requests operational control of a place profile. It does not claim legal ownership of the underlying property. A legitimate controller may be a tenant, occupant, family representative, authorised business manager, institutional administrator, or property owner.
When requesting control:
- explain your relationship to the place and the authority you need;
- provide concise, relevant evidence;
- use the optional contact field only when needed for review;
- avoid publishing secrets or identity documents in a general description.
Requests can be pending, approved, rejected, or withdrawn. An approved request allows the controller to manage the profile, delegate scoped roles, transfer control, and request retirement. It does not replace community verification.
Retirement and material changes
A controller cannot erase a canonical place that may already be used by links, QR codes, deliveries, printed material, or API clients. Normal removal retires the place: it becomes inactive for new use while its identifier, history, and optional replacement redirect remain resolvable.
Permanent removal is restricted to authorised administrators handling confirmed duplicates, fabrication, serious privacy or safety cases, unlawful publication, or binding legal requirements.
Every material edit creates a revision. Low-risk wording changes may preserve verification; a major coordinate or identity change suspends delivery readiness until the current version is reviewed and reverified.
Quality status
Alkax may summarise place quality as Excellent, Good, Standard, or Needs Review. Quality reflects the strength and completeness of the record; it does not replace your own check before a high-stakes journey or service decision.
Use missions, Impact, and rewards →
Understand address quality →