Trust & Security
NomadShare is a non-profit, volunteer-run community. This page describes the controls currently enabled in the app and is honest about what we don't do. It is not a certification or independent audit.
What we DO
- Protect your account with short-lived tokens
- Apply row-level security on every user table
- Strip exact coordinates before public search
- Screen every listing with automated moderation
- Scope realtime channels to only the two participants
- Let you delete your listings any time
- Run as a non-profit — no fees, no ad revenue
What we DON'T
- Sell or share your data with advertisers
- Hold real money or provide payment escrow
- Run background checks on users
- Mediate disputes or provide insurance
- Track you across other sites
- Guarantee any listing's description matches reality
- Offer legal support for exchange disputes
Use NomadShare at your own risk. Every exchange is a direct agreement between two travelers. There is no insurance, no real-money escrow, no background checks, and no dispute mediation. See the terms of use for details.
How NomadShare is run
NomadShare is a non-profit community project, not a company. We don't charge fees and don't hold real money. The points balance is a coordination tool to keep exchanges balanced — it is not money and has no cash value.
What NomadShare does NOT do
- No insurance on items — damage and loss are between the two users.
- No real-money escrow or refunds — only internal points move.
- No background checks or ID verification on users.
- No in-person dispute mediation or legal support.
- No guarantee that a listing's description matches reality.
Account & authentication
Sign-in is handled by our managed authentication provider. Sessions use short-lived bearer tokens that are refreshed automatically; the browser never stores your raw password.
Privileged actions (moderation, balance adjustments, verification approvals) are gated server-side by a role check — client-supplied role claims are ignored.
Data access controls
Every database table that holds user data has row-level security enabled. Policies restrict reads and writes to the owning user, the other party of a conversation or exchange, or volunteer staff.
Realtime channels for messages and conversations are scoped per conversation: only the two participants receive change events.
What we store
Profile data (display name, handle, avatar URL, optional Couchsurfing handle), listings you publish, messages you send, exchange history, and the points ledger. We do not store payment card data — this project runs on an internal points balance.
Approximate listing coordinates are rounded before being returned to the public search API so exact addresses are not exposed. See the privacy notice for the full list.
Moderation & abuse
New and edited listings are screened by automated moderation against our listing rules. Borderline items are queued for human review; hard-rejected categories (weapons, drugs, sexual content, counterfeit goods, hazardous or stolen items) are blocked.
You can report messages, block other users, and appeal a rejected listing once from your profile. To report illegal content, email meowtogetfood@gmail.com.
Hosting & subprocessors
NomadShare runs on the Lovable Cloud platform, which provides managed database, authentication, file storage, and edge compute. Automated moderation is powered by the Lovable AI Gateway. We do not use an external maps provider — locations are text-only and matched against a city list bundled with the app.
Retention & deletion
You can delete your own listings at any time. To delete your account and associated data, email the address below and we will action the request manually. Because the project is volunteer-run, please allow up to 30 days.
Report a security concern
If you believe you have found a vulnerability, please email meowtogetfood@gmail.com with steps to reproduce. Please do not publicly disclose the issue before we have had a chance to respond.
Cryptographic guarantees vs. operational promises
A guarantee is enforced by code and math; a promise is enforced by the humans running NomadShare. Both matter — knowing which is which matters more.
| Layer | Technical execution | Impact on you |
|---|---|---|
| Passwords | Salted + hashed by the managed auth provider. The server never sees or stores your raw password. | A database leak yields hashes, not credentials. |
| Direct messages | X25519 key exchange + XChaCha20-Poly1305. Ciphertext-only storage; keys stay in your browser. | Even volunteer staff cannot read your DMs. |
| Listing coordinates | Public API rounds lat/lng to 2 decimals (~1 km) server-side before returning to anyone but the owner. | Your exact address is never sent to other users. |
| Visitor analytics | Ephemeral per-tab id in sessionStorage. UA is bucketed to a browser family; referrer query strings are stripped before storage. | No cross-session, cross-site, or cross-device tracking. |
| Retention & deletion | Operational promise: staff processes requests manually within 30 days. | Trust-based, not cryptographically enforced. |
Regional variations
NomadShare adapts its consent flow to the strictest law that plausibly applies to you, based on your browser locale.
- Strict (EEA, UK, Switzerland, Brazil, Quebec): opt-in bottom sheet on first visit. Aggregate counters and email notifications stay off until you choose.
- Medium (US-California, Australia, Japan, South Korea, Malaysia, Vietnam, Singapore, others): one-line notice with a Manage link.
- Baseline (everywhere else): sensible defaults; same controls at /settings/privacy.
Ephemeral guest sessions
If you visit without signing in, NomadShare creates no database row for you. UI state (filters, last city) is kept in your browser tab only and evaporates when you close it. There is no persistent "visitor cookie" that survives across sessions.
Last reviewed July 2026. Manage your choices anytime at /settings/privacy.