PROPOSED LAUNCH OFFER
Founding support. $5 once.
One optional contribution, no subscription and no gameplay advantage. It would help cover reviewed daily-question runs, edge and database operations, and privacy and safety maintenance while the product stays broadly free.
- No account required
- No recurring charge
- No paid score boost
- No artificial deadline
This is a non-binding interest signal. Nothing is charged, and no payment or contact detail is collected.
The useful core stays free.
People
Daily choices, the 24-question Know Me quiz, the 21-choice profile, private friend comparisons, and safety controls remain playable without payment.
Public experiment
Thresholded country aggregates, methodology, frozen-edition data, and ledger verification remain public rather than becoming donor-only evidence.
Agents
Discovery documents and bounded public participation contracts remain open, subject to the same safety and rate limits.
Supporters
The proposed $5 option is a thank-you contribution—not a better score, higher rank, or claim of scientific validity.
A signal is evidence, not revenue.
Clicking the button submits one allowlisted aggregate support_intent event and stores yes in this browser so result pages remember the choice. It does not create a pledge, reservation, donation, account, mailing-list entry, or verified-unique-person record.
The event count can be compared directionally with aggregate completed-result counters. It must not be reported as customers, donors, unique people, or money. A real checkout should open only after repeated price-specific interest and after a payment provider, payout path, refund policy, and updated privacy terms are ready.
This page shows no countdown, fake scarcity, invented backer total, or funding progress bar. Until money can actually be accepted, revenue is $0.
The smallest credible revenue path.
- Now · test willingness.Measure one clear $5-once signal after people receive a result. Keep acquisition and sharing separate from payment intent.
- Then · hosted checkout.If demand is real, use a reputable hosted payment page so ViewsMeet does not handle raw card details. Preserve no-account play and publish the provider and refund terms before launch.
- Later · validate paid tools separately.Only after the free product has repeat use, test optional group-hosting or creator conveniences at an explicit price. Do not quietly move current free results behind a paywall.
PRODUCT HELP
When a view doesn’t load.
ViewsMeet has no password or private-link recovery flow. Most issues are temporary service errors, expired private links, connectivity, or a control token stored on another browser.
Email hello@viewsmeet.com for product feedback, accessibility issues, directory verification, or a safety concern that cannot be sent through the in-product report control. Include the page and request ID when available. Never email a private challenge code, management URL, deletion token, answer sheet, password, or payment detail. Individual response times are not guaranteed.
Today’s five will not load.
Check connectivity
An offline badge means the current screen can be read but new picks cannot be submitted.
Retry once
Use the retry button. Repeated rapid retries can trigger a protective rate limit.
Use the labeled demo
Add ?demo=1 to inspect interface behavior. Demo values are visibly labeled and are never live counts.
Keep a request ID
If an error displays a request ID, preserve it when reporting the problem through the channel that provided this deployment.
A friend link is unavailable.
It may be mistyped, deleted by its creator, or expired. Private links deliberately do not appear in search results. Ask the creator for a new link or make today’s challenge your own.
A private challenge is being misused.
Open “Report this challenge” on its landing card and choose a fixed safety reason. Reports contain no free-text message and do not expose your identity to the challenge creator. Repeated reports from the same coarse network are deduplicated.
For immediate danger, contact the appropriate local emergency or platform service; ViewsMeet is not an emergency channel.
I cannot see delete controls.
Creator and response controls rely on opaque tokens stored in the browser that created or submitted the challenge. They do not follow you to another browser or device. Clearing site storage removes local access to those controls.
Never send a management URL or token to someone else; possession grants its limited control.
Keyboard, motion, and screen readers.
All game choices are native buttons and can be reached with Tab, activated with Enter or Space, and reviewed with the Back control. Status changes are announced through a polite live region. The interface follows reduced-motion and increased-contrast preferences.
If focus appears lost after a transition, press Tab once; the active question and controls remain in document order.
Machine clients.
Inspect OpenAPI for current field requirements and use the links on the Agents screen. Treat 429 as a retry-later response. Preserve error code and optional request ID. Never silently substitute demo data for a failed live response.