Email subscribers
People can subscribe to a trip and get email updates when it starts, while it's active, and when it ends. They don't need a Where Is Tereza account — just an email.
What gets sent
Five email types, each opt-in / opt-out per subscriber:
| Type | When | Default |
|---|---|---|
| Subscribe confirm | Immediately on subscribe | always |
| 7 days before | One week before the trip's start date | on |
| 24 hours before | The day before the trip starts | on |
| Tracking started | When live tracking actually begins | on |
| Daily digest | Each evening during an active trip | off |
| Trip completed | When the trip ends — with full summary | on |
| Photo added | Each new photo uploaded to the trip | off |
Every email is on-brand (gold accent, dark mode), short, and includes a one-click unsubscribe link plus a personal portal URL where the subscriber can flip individual preferences.
Per-trip subscriber list
Each trip has its own subscriber list; subscribing to one trip doesn't subscribe to anything else. The trip page on the public map has a "Subscribe" link that opens an email-only form (no account needed).
In the org admin → trip detail → Subscribers, you can:
- See the full list with subscribe date.
- Manually invite (paste an email).
- Manually unsubscribe.
- Send a one-off message to all subscribers (Nomad plan).
- Export the list as CSV.
Personal portal
Each subscriber gets a unique token URL like
app.whereistereza.com/o/yourname/follow/{token}. The portal lets them
toggle individual preferences ("yes to daily digests, no to
photo notifications") without an account. Tokens are long-random;
nobody else can guess another subscriber's preferences.
What we don't do
- We don't share your subscriber list with anyone.
- We don't email subscribers between trips ("come back to our product!" newsletters). Only the seven trip-bounded events above ever fire.
- We don't track open rates or click rates per subscriber. The Resend API gives us aggregate delivery stats only.
Plan limits
Subscribers are unlimited on every plan. Storage of subscriber preferences is tiny (a JSON file per trip).
Email service
We use Resend for delivery. SPF + DKIM are
configured for whereistereza.com. Sender address is
iknow@whereistereza.com.
If a subscriber's email bounces twice in a row, the address is marked dead and skipped on subsequent sends — they don't see a broken email, you don't see your sender reputation tank.
Related
- Trip management — visibility, share links.
- Privacy & data control — what we keep, what we don't.
Need help? Contact support · Where Is Tereza?