EmberLife
Privacy Policy
Last updated October 30, 2026
Effective date: October 30, 2026. EmberLife (“EmberLife,” “we,” “us”) is operated by ALLEBRUM LLC, doing business as EmberLife.io. This policy explains what we collect, how we use it, and the choices you have — including how we handle text messaging (SMS), data from Google when you connect your Google account, and video calls.
Who we are
ALLEBRUM LLC dba EmberLife.io
2281 Lava Ridge Court, Suite 200
Roseville, CA 95661
hello@emberlife.io
What EmberLife does
EmberLife helps people stay close to friends and family by organizing circles (“fire pits”), people you care about (“embers”), availability, and suggested time together (“Moments”). It is not a public discovery or dating network.
Information we collect
- Account info — name, email, time zone, and sign-in methods (magic link, Google, passkeys).
- Mobile number and text-messaging records — if you add a phone number, opt in to texts, sign in by phone, or verify your number: your mobile number; when you verified it; a record of your opt-in (date, time, method, and the consent wording you agreed to); a record of each code, invite, or scheduling-ask text we send to a number; the messages we send you and any replies; and your STOP/HELP requests. See “SMS / Text Messaging” below.
- My Availability — your schedules, free windows, blackout dates, and related preferences.
- Embers & contacts — names and optional email, phone, social handles, private notes, and gift ideas you store about people you know. Contact details you enter for others are for your use. Adding someone as an ember does not text or email them. We contact them only if you choose to invite them (an email, or — if you have verified your own phone number and confirm it is their mobile phone — one text), as described under “SMS / Text Messaging” and “Invites” below.
- Fire pits, Moments & invites — groups, memberships, invites, and scheduling preferences.
- Invite records — which member invited whom, when, by which channel, and the outcome (accepted, declined, bounced, or STOP). To enforce limits and honor opt-outs we keep only a one-way (hashed) form of the invited email address or phone number, not a list of addresses.
- Connected calendars — if you connect Google Calendar: when you’re busy or free (not the titles or details of your events), and the Moment events EmberLife adds to your calendar. Used only to schedule Moments. See “Google user data” below.
- Contacts you choose — if you use “Choose from Google” (or Outlook) when adding an ember, we read your contact list at that moment to show it to you, and save only the contact you pick. See “Google user data” below.
- Video calls — if you join a Moment’s video room, your name and account ID are passed to our video provider to connect the call. We don’t record calls. See “Video calls” below.
- Usage data — basic logs needed to run and secure the service (for example sign-in events and errors).
How we use information
- Provide, maintain, and improve EmberLife (accounts, schedules, fire pits, Moments).
- Send service messages by email — sign-in links, invites you ask us to send, and Moment reminders.
- Use your mobile number to sign you in (if you choose “Text me a code”), to verify that the number is yours before you can text invites, to send Moment reminders and updates if you opted in, and to deliver the texts described in “SMS / Text Messaging.”
- Limit and review invites (daily limits, per-person limits, review of unusual activity) so EmberLife isn’t used to spam people.
- Protect the service (security, abuse prevention, debugging) and meet legal obligations.
SMS / Text Messaging
EmberLife sends a few kinds of text messages. Reminders and updates go only to members who opt in: on your Settings page you enter your mobile number and check the text-message consent box (unchecked by default and optional). Codes are texted only when you ask for them. Invites and scheduling asks are a one-time text to a person a member has invited or wants to find time with. Program details are also on our SMS program page.
What we collect for texting: your mobile phone number; your opt-in consent record (date and time, method such as the Settings checkbox, and the consent wording); when you verified your number; message history, including the texts we send and replies you send; and your STOP and HELP requests. For a person who is texted an invite, we keep the number with the STOP record if they reply STOP, and otherwise only a hashed form for limits.
The kinds of text we send, and who gets them:
- Moment reminders and fire pit updates. Reminders and confirmations for Moments you’re part of, and updates about fire pits you belong to (for example when a Moment is announced or moved). Sent only if you opted in.
- New-message alerts. A short “<Name> sent you a message” text with a link when a chat message waits unread for a while. Never includes the message itself. Only if you opted in.
- Product updates (occasional, promotional). Occasional product updates and tips, at most 2 per month, only to members who opted in.
- Sign-in and phone-verification codes (you ask for them). A one-time code texted to the number you enter when you ask for it, to sign in or to verify your own number. One text per request; not marketing.
- Ember invite texts (to someone an EmberLife member invites). When a signed-in member who has verified their own phone number invites someone by text, EmberLife sends that person one text naming the member, with a link to accept or decline. The invited person can reply STOP and will not be texted by EmberLife again.
- Scheduling-ask texts (between connected members). When two connected members have no shared free time, EmberLife may text one of them once, asking whether they can open up a time. It names EmberLife and the member and links to a reply page.
- Fire pit invite texts (to someone a member invites to a fire pit). When a member who has verified their own phone number invites someone to a fire pit and confirms the number is that person’s mobile phone, EmberLife sends that person one text naming the member, with a link to accept or decline. Same limits and STOP rules as ember invite texts.
How we use your number: to sign you in when you choose “Text me a code”; to verify it is yours before you can text invites; to send reminders and updates if you opted in; and, if you are the person invited, only to deliver the one invite or scheduling-ask text. We do not sell it or use it for anyone else’s marketing.
Consent to receive reminder and update texts is not a condition of any purchase or of using EmberLife. Message frequency varies: typically up to 4 reminder texts per Moment you’re part of (at the reminder times you choose), plus at most 2 product-update texts per month. Sign-in and verification codes: one text each time you ask for one. Invite texts: one per invite. Scheduling-ask texts: at most 2 per pair of members in 60 days. Message and data rates may apply.
Opt out anytime by replying STOP to any EmberLife text (EmberLife then sends no further texts to that number, including invites from any member), or by unchecking the text-message box in Settings. Reply START to resubscribe. For help, reply HELP or email hello@emberlife.io. Carriers are not liable for delayed or undelivered messages.
We do not share, sell, rent, or provide your mobile phone number, SMS opt-in data, or messaging consent to third parties or affiliates for marketing or promotional purposes. Mobile information is only shared with service providers (such as our SMS provider) as needed to deliver messages, and is never used by them for their own marketing.
Who can see your phone number: you, and EmberLife members you are connected with through an accepted connection. Sharing a fire pit with someone does not show them your number.
Invites
Members can invite people they know to connect on EmberLife or to join one of their fire pits, by email, and by text if they have verified their own phone number. To keep invites from becoming spam:
- Only a signed-in EmberLife member can send an invite. The email is sent by EmberLife on the member’s behalf to the address they enter, names the member, and links to a page where the person can accept or decline. Invite links expire after 7 days.
- Every ember invite email has a “Stop them” link. One confirming click, with no account or sign-in, and no EmberLife member can send an invite to that address again.
- Declining an invite stops that member from inviting that person again for 90 days. An address that rejects our email is blocked from further invites.
- Limits: email invites start at 5 a day per member and rise in steps, up to 80 a day, as invited people accept. The same address can be invited again only after 24 hours, then 3 days, 7 days, and 14 days, and not more than 3 times a week by all members combined. A member can have at most 25 invited people pending or connected before an administrator must review the account.
- Review of unusual activity: if about 10 invitations go out and none are accepted, EmberLife pauses that member’s text and email invites and reviews the account.
- For text invites the member must first verify their own mobile number with a code, and confirms the number they enter is the invited person’s mobile phone. The invited person can reply STOP and is never texted by EmberLife again unless they reply START.
Google user data
You can use EmberLife without connecting anything from Google. If you do, here is exactly what we ask for, what we do with it, and how to take it back.
We ask for Google permissions one step at a time, only when you use the feature that needs them:
- Sign in with Google — only your basic profile: name, email address, and profile picture. We use it to create and sign in to your account. We don’t keep the Google sign-in tokens.
- Connect Google Calendar (on My Availability) — permission to see when you’re free or busy, and to add, update, and remove the events for your EmberLife Moments. We check your free/busy times when finding times for your Moments (other members see suggested times, never your calendar), and we keep your Moments on your calendar up to date. We don’t read the titles, details, or guests of your other events.
- Choose from Google (when adding an ember) — read-only access to your Google Contacts. We read your contacts (names, email addresses, and phone numbers) only while you have the contact picker open, to show you the list. We don’t store your contact list: only the one contact you pick is saved, as an ember in your account, and you can edit or delete it anytime.
Stored securely. The access tokens that let EmberLife reach your Google Calendar or Contacts are encrypted at rest (AES-256-GCM) and used only by our servers for the features above. They are never shown to other users.
Disconnecting. You can disconnect Google Calendar on My Availability and Google Contacts from the contact picker at any time. We delete the stored tokens for that connection right away, and we revoke EmberLife’s access at Google when it was your last Google connection (Calendar and Contacts share one Google permission, so while one is still connected Google may keep listing EmberLife under your account). You can also remove EmberLife anytime at myaccount.google.com/permissions. Deleting your EmberLife account always revokes our Google access.
Limited Use. EmberLife’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data we get from Google is used only to provide the EmberLife features you use; it is not used for advertising, not sold, and not used to train generalized AI or machine learning models. No person at EmberLife reads it unless you ask us to and agree (for example, for support), it’s necessary for security (such as investigating abuse), or the law requires it.
Video calls
Moment video rooms run on EmberLife’s own video pages (on emberlife.io), powered by LiveKit, our real-time video provider, which relays the audio and video between participants. Only people on the Moment can join — signed in, or through their own personal invite link — and a room closes shortly after its Moment ends, or as soon as the Moment is called off or you’re no longer part of it. EmberLife does not record calls. Your camera and microphone are used only while you’re in a room, and only after your browser asks for your permission.
Connecting with a QR code
When you show your QR code to someone you meet, EmberLife makes a fresh random link that works for 10 minutes and for up to 3 people, so a photo or printed copy soon stops working. It does not contain your email, phone number or account number, and anyone who opens it sees only your name and profile photo until you are connected. When someone connects with your code you get a notice in the app and can undo it for 7 days. In Settings you can expire every code you’ve shown or turn connecting by QR code off. To scan someone else’s code, your browser may ask to use your camera; the video stays on your device and is not recorded or uploaded — only the link in the code is read.
Scanning our printed QR codes
Some EmberLife stickers, shirts and other printed items carry a QR code that opens a short emberlife.io link before sending you on. When you scan one, we record that it was scanned: the time, the kind of device, operating system and browser (from your browser’s user agent), your approximate location as country, region and city (estimated from your IP address by our hosting provider), your browser’s language and the website that referred you, if any. To count how many different people scanned a code, we keep a one-way, salted hash of your IP address and browser; we do not store the IP address itself, and the hash can’t be turned back into it. We use these records only to see which printed items people use. The only link we make between a scan and an account is to tell whether that scan led to a new EmberLife account or a camp store order, so we can count sign-ups and orders per printed item; we don’t use scans to track you or connect them to your account in any other way.
If the code takes you to EmberLife, we also set a first-party cookie for 7 days that tells us whether that scan led to a new account or a camp store order. It holds only a random scan ID, is not shared with anyone, and is removed once it’s been checked for a new account.
Ads and links that bring you to EmberLife
When you arrive from one of our ads or a link we’ve tagged (for example a Facebook ad, or a link with “utm_” campaign tags), we remember which ad or campaign sent you so we can tell which ones actually help people find EmberLife. On any other first visit we remember only the website that sent you (its name only, for example facebook.com or google.com), or that you came directly (typed the address or used a bookmark). We set a first-party cookie for up to 90 days that holds only: the campaign tags in the link (source, medium, campaign, ad and keyword), the ad-click ID Facebook or Google adds to the link (fbclid or gclid), the EmberLife page you landed on, the website that referred you (its name only) and when you arrived. We keep the first visit and the latest one that came from an ad, a tagged link or another website; moving around EmberLife doesn’t change it.
If you then create an account, we save that information with your account once and remove the cookie, so we can count sign-ups per ad, campaign or referring website. If there’s no cookie (for example you cleared it or signed up on another device), we just note that the source is unknown. We don’t send it to Facebook, Google or anyone else, we don’t use it to show you ads, and it’s deleted with your account.
On some of our ad landing pages (for example emberlife.io/start) we also keep a simple count of page views and taps on the “Start free” button, so we can see whether an ad’s page works. Each count stores only which page, whether it was a view or a tap, the campaign tags in the link (source and campaign) and the time. It uses no cookies and doesn’t store your IP address, device or browser details, or anything that identifies you, so it isn’t tied to you or your account and works the same whatever you choose in the cookie banner. Automated visitors (search engines, link previews) aren’t counted.
Buying from the camp store
When you buy from the EmberLife camp store (emberlife.io/shop), the seller is ALLEBRUM LLC dba EmberLife.io. To take and deliver your order we collect your name, email address, shipping address, optional phone number, what you ordered and the amounts paid. You don’t need an EmberLife account to buy.
- Payment is processed by Stripe. You enter your card (or use Apple Pay, Google Pay or Link, Stripe’s saved-checkout service) in a secure form provided by Stripe; your card number goes straight to Stripe and EmberLife never sees or stores it. If you pay with Link, Apple Pay or Google Pay, it shares your name, email and shipping address with us for the order (and your phone number, if it has one). Stripe also calculates sales tax from your shipping address. Stripe handles payment information under its own privacy policy (stripe.com/privacy), including to prevent fraud.
- Printify makes and ships your order. We send Printify, our print-on-demand partner, your name, shipping address, email address and phone number (if you gave one), and the items you ordered, so they can print, pack and ship it and tell us when it ships. Printify handles this under its own privacy policy (printify.com/privacy-policy).
- We use your email to send your receipt, a shipping notice with tracking and, if needed, messages about a problem with your order. We don’t add you to a mailing list or send marketing because you bought something.
- Orders in your EmberLife account. If the email address or phone number given with an order matches an email address or phone number you have verified on an EmberLife account (by a sign-in link, Google sign-in or a one-time text code), we link the order to that account, when you pay or later when you sign in. You then see it in the app: a short status bar at the top of the page while it’s on its way, and a list under Settings → Orders. We never link an order on details that haven’t been verified, and an order is linked to one account at most (a verified email match comes before a phone match). The account sees what the order status link in your receipt shows (items, amounts, status, tracking, and the ship-to name and city), never card details. If you close the status bar, that choice is remembered in your browser’s storage until the order’s status changes.
- Your cart is kept in your own browser’s storage (not a cookie) so it’s still there when you come back. While you check out, your shipping details (and, for a wallet or Link payment, a reference to the open order, so a retry can’t charge you twice) are kept in that browser tab only until you close it.
- We keep order records (including name, address, email and amounts) for as long as needed for taxes, accounting, returns and legal requirements, which is generally up to 7 years, even if you delete an EmberLife account.
Your private budget and what you spend
If you choose, you can tell EmberLife a monthly budget and a per-meetup budget, and — after a Moment — how much it cost you. These money amounts are information you provide. They are private: only you can see them, they are never shown to other members, and they are never included in emails, calendar invites, text messages or logs. We use them only to keep suggestions within what is comfortable for the people on a Moment: the lowest budget among them quietly applies, without saying whose it was. Amounts you report about a place may also be pooled, as a median of at least two members, to estimate what that place costs; no one can tell who reported what. A fire pit owner can separately set a group budget that every member of that fire pit can see, clearly labeled. You can change or clear your budget in Settings at any time, and deleting your account deletes it.
How we share information
We do not sell or rent personal information, and we do not share it for cross-context behavioral advertising. We share information only:
- With service providers who operate EmberLife for us — for example hosting, database, email delivery (Resend), text-message delivery (Twilio), video calls (LiveKit), Google APIs you connect, product analytics if you accept optional cookies (HeyCatch), and, for camp store orders, payment processing and tax (Stripe) and printing and shipping (Printify; see “Buying from the camp store”). They may use it only to provide those services to us.
- With other EmberLife members you choose — for example your name and availability with fire pits you join.
- For legal reasons — to comply with law, enforce our Terms, or protect rights and safety, and in connection with a merger or sale of the business (subject to this policy).
All of the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties or affiliates for marketing or promotional purposes.
Private notes
Notes and gift ideas you attach to an ember are private to your account. We do not show them to that person.
Security
We use HTTPS everywhere, encrypt Google and Microsoft access tokens at rest, expire sign-in sessions and sign-in links, and limit how often sensitive actions can be repeated. No system is perfectly secure, but we work to protect your information and will notify you as required by law if a breach affects it.
Retention & deletion
We keep account data while your account is active. Text-message consent records are kept while you’re opted in and for a limited period afterward as proof of consent and opt-out. You may email hello@emberlife.io to request access, correction, or deletion of your data. We may retain limited logs as required for security or law. Sign-in and verification codes are stored only in scrambled (hashed) form and expire after 10 minutes. Invite-limit and unsubscribe records keep only a hashed form of the address or number, for as long as needed to honor opt-outs and prevent abuse.
Combining accounts. If you link two EmberLife accounts of your own (for example one created with your email and one with your phone number), we keep a short security log of each attempt and each completed combination. It records only account identifiers, the type of verification used, a time and a hashed network address, never names, email addresses, phone numbers or message content, and we keep it for as long as needed for security and abuse prevention. Text opt-outs (STOP) always carry over.
Delete your account anytime in Settings → Delete account. When you do:
- We revoke EmberLife’s access to your Google account (Calendar and Contacts), remove any Microsoft (Outlook) connection, and delete the stored tokens.
- We delete your account and what belongs to it: your profile, sign-in methods and passkeys, your embers (with their notes and gift ideas), availability, fire pit memberships, your replies to Moments, journal entries and notes, chat messages you sent, and invites you sent.
- Shared fire pits keep going: a fire pit you own that has other members is handed to its longest-standing other member, so your friends don’t lose their group. Fire pits where you’re the only member are deleted.
- Some records aren’t yours alone and stay, no longer linked to your account: an ember that someone else created for you stays in their account, and our text-message consent and opt-out records, cookie-choice records, feedback you sent us, and calendar-reply logs are kept as described above.
- Moment events we already added to your Google Calendar stay there for you to keep or delete, and emails or texts already sent can’t be recalled.
Your choices & California privacy rights
You can update your profile, turn reminders and texts on or off in Settings, disconnect Google Calendar or Google Contacts at any time, and delete your account in Settings. California residents may request to know, access, correct, or delete personal information by emailing hello@emberlife.io. We do not sell or share personal information as those terms are defined under California law, and we will not discriminate against you for exercising your rights.
Cookies & similar tech
We use essential cookies and similar storage to keep you signed in, protect accounts (CSRF / OAuth), and remember basic preferences; after you scan one of our printed QR codes, a 7-day cookie described in “Scanning our printed QR codes”; and, when you arrive from one of our ads or tagged links, a cookie of up to 90 days described in “Ads and links that bring you to EmberLife.” You can choose “Essential only” or “Accept all” in the banner on first visit; we store your choice on your device and, when you are signed in, keep an append-only record of that decision.
Analytics. Only if you choose “Accept all,” we use Google Analytics (provided by Google LLC) to understand which pages are visited and how people find us. Google Analytics sets cookies and collects information such as pages viewed, referring sites, approximate location, and device/browser details. We may enable Google signals and demographics & interests reports, which use aggregated data from Google accounts whose owners have turned on ad personalization; we only see aggregated reports, never individual identities. Until you accept, Google Analytics is not loaded at all (Google Consent Mode defaults to denied). We strip query strings and the private parts of invite, moment, and sign-in links before anything is sent. You can change your choice at any time by clearing this site’s data, and you can opt out of Google Analytics on all sites with Google’s browser opt-out add-on.
Product analytics (HeyCatch). Also only if you choose “Accept all,” we use HeyCatch to understand how EmberLife is used so we can improve it. HeyCatch collects pages viewed, clicks on buttons and links (on our public pages, including their visible text; inside the signed-in app, the text of what you click is removed before anything is sent), referring sites and campaign tags, approximate location, and device/browser details, and stores a random identifier in your browser so visits can be tied together. When you are signed in, we also send your EmberLife account ID, name, and email address so that activity is linked to your account, and we note when you finish setting up your account. HeyCatch processes this as our service provider. Until you accept, the HeyCatch code sends nothing and stores nothing on your device; if you switch to “Essential only,” it stops. We strip query strings and the private parts of invite, moment, and sign-in links before anything is sent. Links of the form emberlife.io/ followed by a single letter or number are short links that we tag with the channel they were shared on.
Children
EmberLife is not directed at children under 13, and we do not knowingly collect their information. Do not create an account for a child under 13.
Changes
We may update this policy. We’ll change the effective date above and, for material changes, provide additional notice when appropriate.
Contact
ALLEBRUM LLC dba EmberLife.io · 2281 Lava Ridge Court, Suite 200, Roseville, CA 95661 · hello@emberlife.io