Trust and safety

How a location is verified before it can be booked

Public listing queries require approved status. Approval status is a publication gate, not proof of legal signage compliance or current fulfillment availability.

• The address is geocoded and the host places a private pin for placement and installation planning. Public maps use a privacy-safe approximate location.
• New listings receive a location-type traffic estimate or planning assumption. An AI reasonableness check may compare it with typical ranges, but Nakovia does not directly measure or independently verify traffic.
• Hosts confirm property authority and known lease, HOA, zoning, permit, and signage restrictions. Nakovia does not provide or guarantee a complete legal signage review.
• Listing photos are submitted for the placement. The repository does not prove an automated stock-photo detection guarantee.
• Material listing edits should return through the applicable approval workflow. Production behavior and audit completeness must be verified before making an absolute claim about every edit.
• A listing's public page never shows the exact street address. Advertisers see the neighbourhood and the map area until a booking is confirmed.

How an ad design is reviewed

Every design passes two separate gates before it is printed, and the second one belongs to the person whose property it goes on.

First, Nakovia reviews it. An automated content scan runs first and flags anything questionable, then a person makes the decision. The scan does not approve anything on its own; it exists to tell the reviewer where to look.

Second, the property owner reviews it. A host is shown the exact artwork that would go on their fence and can approve it or decline it, from their dashboard or from a link sent to their phone. A design Nakovia approved and a host declined does not get printed. This is the gate that actually decides what goes up, and it belongs to the person who owns the property.

Hosts can also set standing rules on a listing. A listing being paused, blocked-out dates and a minimum booking length are all enforced at booking: a booking that breaks one is refused, with the reason. So are the industries a host will not take and the specific businesses they name, because advertisers declare both. Three limits stated plainly: an advertiser who has not declared yet is asked the first time they try to book, the declaration is self-reported, and on a bulk corporate campaign the named-business rule is checked while the industry rule is not. The artwork approval is a separate gate on every booking regardless, and it always has been.

Nothing is sent to the printer until both gates are clear.

How we prove the ad is actually up

This is the part of the product that decides whether an advertiser was told the truth. An installed ad is not marked live because somebody said so. It is marked live because a fresh, location-stamped, time-stamped set of evidence was submitted and a person looked at it.

The current verifier uses live camera capture and requested location/time context, then a human reviewer checks the complete evidence set before go-live.

• A close shot where the product and approved artwork are readable.
• A wide shot showing the product at the property.
• A shot from the curb, showing that somebody on the road can actually see it.
• A shot of the mounting: the stake, the zip ties, the bracket. Proof it is attached to something rather than propped against it.
• A 5 to 10 second video pan tying the road to the sign in one unbroken take.

What the verification checks catch

The submitted set is checked automatically before a reviewer sees it, and the reviewer is shown exactly which checks failed and why.

• Location: the capture GPS has to be within 75 metres of the listing. A fix too fuzzy to prove anything is rejected rather than accepted.
• Time: the capture timestamps have to be within 15 minutes of real time.
• Artwork match: the sign in the photo has to be the design that was approved, not a different one and not a faded or torn version of it.
• Distinctness: four frames of the same view is one piece of evidence, not four. Near-identical shots are detected and rejected.
• Movement: a set captured in eight seconds was captured from one spot without walking anywhere. The capture has to span enough time to be four real positions.
• Scene consistency: all the shots have to read as the same property.
• Verification links expire after 72 hours, so a link that leaks is not a permanent key.

An admin decision is required

The automatic checks produce an advisory verdict. They do not put an ad live. The current verification route requires an authenticated admin pass or fail before go-live approval and rent capture.

An admin action is not, by itself, proof of the quality or duration of a manual review. Audit records and operating procedures should support any stronger human-review claim.

Damage, weather and replacement exceptions

Pilot damage, loss, and replacement exceptions require documented operator review. Fault recording does not automatically allocate a charge, refund, or credit.

The operator preserves damage, delivery, installation, and verification evidence and determines next steps from actual costs, responsibility evidence, and approved policy.

A damaged, lost, or failed-delivery item is not automatically reprinted or charged. Every supplier action still requires separate human authorization.

Property damage and responsibility questions are handled manually. This page does not promise an unapproved cost allocation or insurance coverage.

Cancellations

Before irreversible third-party work, avoidable and unearned amounts are cancelled, voided, refunded, or released subject to provider mechanics.

After documented irreversible supplier, production, or installation work begins, only nonrecoverable costs Nakovia actually incurred may reduce a refund, after operator review.

If a host backs out or fulfillment fails, remaining work stops. An unverified campaign is not treated as completed, and payout remains blocked while actual costs and provider state are reconciled.

No cancellation or takedown amount is allocated automatically. The booking record must support work actually performed and any amount charged or retained.

Disputes

There is no self-service dispute button. Pilot disputes are handled manually; contact support with the booking reference.

Nakovia reviews the booking's own record: the verification evidence, the message history, the payment and payout ledger, and the timestamps on every state change. That record is not editable by either party, which is the reason it is worth having.

No response time is promised here because the repository does not contain measured dispute-response performance.

Nakovia preserves booking, clickwrap, payment, artwork approval, fulfillment, communication, and verification evidence and does not claim control over bank or card-network outcomes.

Payments

Card details are handled by the payment processor and never touch Nakovia's servers. Nakovia stores a reference, not a card.

Rent is not captured when a booking is made. It is authorised, and only charged once the ad is verified as live. If the ad never goes up, the authorisation is released and the money was never taken.

A host payout becomes eligible only after rent capture and approved verification. Payout-account readiness, the dispute window, and admin approval also apply. Bank posting time varies.

Reporting something

Anything on this platform can be reported: a listing, an ad, a host, an advertiser, or a sign you have driven past that should not be there. Use the contact page and include the listing or booking reference if you have one. A report about a sign that is currently up is treated as urgent. There is no in-page report control yet, which is why this says the contact page rather than pretending otherwise.