Common questions, common fixes

Yes. Permanently. No paid tier, no premium features, no upsell. Same app for every account.

SafeCircle uses Supabase (Postgres) for storage. Servers are hosted in the US West region. Auth is handled by Supabase Auth. Push notifications use the user's browser push service (Apple, Google, Mozilla, Microsoft) — we never see message content stored on those services.

Only members of circles you belong to. People outside your circles cannot see anything about you. Members of your circles can also see your name, profile email, and any plan you've shared with that specific circle.

No. For any life-threatening emergency, call 999 (UAE) first. SafeCircle is for staying connected with the people who care about you, before, during, and after — it isn't a way to summon emergency services.

Because it doesn't need them. SafeCircle doesn't request location, contacts, microphone, or camera. The only permission it asks for (optionally) is push notifications.

Visit /login and tap Forgot? next to the password field. Enter your email, then click the link we send you.

Your browser may have blocked it. Allow popups for mysafecircles.app, or use the email + password path instead.

SafeCircle auto-confirms accounts created with email + password — you can sign in immediately. No confirmation email is needed.

This isn't self-service yet. Email b.evariste@gmail.com from the address tied to the account; we'll remove it within 7 days, including all your circles, plans, and statuses.

No hard limit. Practically, 1-3 active circles is healthier than 10 inactive ones. Owners: see Owner guide for curation advice.

Not directly — the Owner can't leave their own circle. Either delete the circle (Profile → circle → Delete) or have someone else create a replacement and migrate.

Invite links expire after 14 days. The Owner can generate a fresh one in seconds (Profile → circle → Invite → Generate invite link).

Not today. Workaround: ask the new owner to create a fresh circle, invite the same people, then delete the old one.

You (the Author) and any collaborators you've added by email. Members of the circle the plan is shared with can read the plan but can't edit unless they're also collaborators.

Not at the same time. A plan can be shared with one circle. If you need the same content in two circles, build two plans (you can copy the contents manually).

Only you can see it. Even people you've added as collaborators — wait, those are an exception: collaborators can always see the plan, regardless of the "Shared with" setting. Setting it to Just me only hides it from a circle.

Three things to check, in order:

• Profile → Notifications: device shows Active? If not, tap Enable here.
• Browser permission: if the card says Notifications were blocked, you need to unblock in your browser's site settings (Chrome: lock icon → Site settings → Notifications → Allow).
• Account preference: not on Off. Emergency only means you only get woken for Help statuses, not regular ones.

Subscriptions are per-device. Open the app on the phone, go to Profile → Notifications → Enable here. iPhone: the app must be installed to home screen first (Safari → Share → Add to Home Screen).

All updates = Safe statuses, Help statuses, plan shares. Emergency only = only Help statuses. Useful if you want to stay reachable for emergencies but not be pinged every time someone in your circle clocks off for the night.

SafeCircle uses notification tags so updates from the same person collapse. If you see duplicates, your service worker may be cached at an older version — close all tabs of the site and reopen.

Runbook for an admin investigating a suspected push outage:

• Open /admin/push. Pick any active subscription (last_used_at within the past 7 days). Tap Test push.
• If the test push arrives → delivery is fine; the issue is upstream (someone's preference is set to Off, or their browser revoked permission).
• If the test push fails with a 401 in the action log → check the Vercel env vars: VAPID_PUBLIC_KEY, NEXT_PUBLIC_VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY, VAPID_SUBJECT all present and matching.
• If many subscriptions are returning 410 in /admin/audit → expected; sendPushToUsers auto-deletes them. A spike means a recent SW update or VAPID key rotation invalidated old subscriptions.
• If the last_used_at column on /admin/push shows old timestamps for everyone → the touch path may be failing. Check Supabase logs for push_subscriptions UPDATE.

That's expected on iPhone, iPad, and Mac Safari — those browsers don't expose a one-tap install. Follow the on-screen Share → Add to Home Screen / Add to Dock guide.

You probably installed before the latest version shipped. Browsers cache the old start_url for ~24h. If you want it sooner: uninstall (long-press the icon → Remove / Delete) and re-add to home screen.

Two requirements on iOS: the device must be on iOS 16.4 or newer, and the app must be opened from the home screen icon (not from a Safari tab) when you enable notifications. Reopen from the home screen, then Profile → Notifications → Enable here.