Customer accounts

Every public app in your project can sign customers in. Spark runs the accounts for you: the sign-in screen, the codes, and the emails that carry them. You never set any of it up, and the whole flow carries your business’s name — as far as your customers can tell, they’re signing in to you.

How sign-in works

A customer enters their email address. Spark emails a code to that address, the customer types it in, and they’re signed in. That’s the whole flow.

The first sign-in creates the account. There is no separate registration step, and customer accounts have no passwords — nothing for them to create, forget, or reset. (Your own builder account is separate and does use a password.)

One sign-in across your project

Your project’s apps share one sign-in. A customer who signs in on your chat app is already signed in when they open your online store, and the other way around. To the customer it reads as one business with one account, which is exactly what it is.

What a signed-in customer gets

• Their conversations and data are kept. What they build up in your apps — chat history, files, saved work — stays with their account between visits.
• Purchases follow them. Anything they buy through your features and offers travels with the account across your apps.
• An account screen in the chat app. It shows the email they signed in with and carries two controls: the Manage billing button and account deletion.

You can see who has signed up, and what they’ve been doing, in the Users tool.

Manage billing opens Stripe’s own hosted billing portal. There the customer can update their card, see their invoices, and cancel a subscription — all on Stripe’s page, then back to your app. Changes made in the portal can take a minute to show up in the app.

Account deletion

Customers can delete their account themselves, from the same account screen. Deletion is immediate and permanent: their conversations and files with your apps are removed, and any active subscription is canceled on the spot, with no refund for the remainder of the period. The confirmation dialog says all of this before they commit.

Deletion is scoped to your apps. Accounts the same person holds with other businesses are untouched, and the same email can sign up with you again later, starting fresh.

Supported sign-in methods

Email codes are the one way in. Spark offers no Google or other social login, no SSO, and no password option — for the full list of things Spark leaves out, see what Spark doesn’t do.

Test sign-in yourself

On the chat app and the online store, use the Preview as control in the preview to try the app as a signed-out visitor, a free user, or a paying customer — no account needed.

On your other apps, the preview’s sign-in is real: enter your own email and type the code we send you. The account it creates is a real customer account with your business, and anything you make while previewing lives alongside the app’s real data — see preview and publish.

If codes stop arriving

Spark delivers the sign-in code emails itself. When a customer says a code never came, their spam folder is worth one look first. If codes still aren’t arriving after that, contact support — delivery happens on Spark’s side, and support can trace it.