Trust before features

SofterHello should earn trust through clear context, privacy-aware choices, consent, and careful defaults before introducing data-backed product features.

A small group sitting together at sunset.

Current public website state

No tracking

No analytics, cookies, pixels, or tracking scripts are active on this early website.

No live forms

There is no newsletter form, waitlist database, account creation, RSVP flow, or payment flow.

Email only

Contact currently happens through email links. A fuller policy is needed before collecting product data.

Later features need clearer consent

If SofterHello later adds signups, waitlists, RSVPs, or accounts, those features should come with a more complete privacy policy and a simple consent model.

Principles for future product decisions

Collect less

Ask only for information that has a clear purpose in helping someone understand, attend, host, or safely manage a meetup.

Explain the purpose

People should be able to understand why information is requested, how it may be used, and what choices they have before submitting it.

Make consent visible

Important choices—such as contact preferences, photos, sharing details, or future follow-up—should not be hidden inside broad or ambiguous agreement.

Plan for concerns

Any future meetup system would need clear ways to ask questions, report an issue, manage participation, and understand what happens next.

Principles, not completed features

These are standards intended to guide later product work. They do not mean that a finished moderation, identity, reporting, host-verification, or safety system exists today.

For the website's current handling of email contact and technical data, read the plain-language privacy note.