Cookies

The cookies we set

• Your session (“sb-…”). Set when you sign in, so the app knows who you are on each page. It is the only thing that keeps you signed in, and clearing it signs you out. It may last up to four hundred days, but the two times below sign you out long before that. During sign-in a second, short-lived cookie ties the link we emailed to the browser that asked for it.
• When you were last here (“se_seen” and “se_since”). Two times only: when you last used a page, and when you signed in. They sign you out after 2 hours away (15 minutes for operators), and in any case after a week (8 hours for operators), whatever the session cookie says. Eight days.
• Your church (“se_church”). When you belong to more than one church, which one you are working in. A year.
• Your view (“se_view”). Whether you chose the Standard or the Advanced view, so the app opens the way you left it. A year.
• An operator’s look (“se_look”). For the people who run the service only: which church they are looking at, read-only, until they go back to Operations or close the browser.
• Connecting an account (“se_connect”). While an admin connects a social account, which church and person started it, so the connection can only land where it began. Fifteen minutes.
• The preview (“se_site”). Before launch, that this browser has opened the site; it lasts thirty days.
• Where you were going (“se_next”). For an hour after a sign-in, the page to return to.
• A heart on a church’s page (“se_fan”). After you tap the heart on a church’s page, a random id so your like counts once and can be taken back. A year.

Your browser also keeps an unsaved edit in its own storage for the length of the tab, so a reload does not lose it, and the words open in an editor when you are signed out after a while away, until you open that editor again; neither is ever sent anywhere.

On a church’s page your browser also keeps, in its own storage and not as a cookie (“se_likes”), the ids of the pieces you tapped the heart on, so the heart stays filled on this device.

What we do not set

No advertising cookies, no analytics cookies and no fingerprinting. We do not follow you to other sites, and we do not let anyone follow you here.

Other companies’ cookies

When you connect a social account or pay through Stripe, you do so on their pages, and they set cookies under their own policies. The check on sign-in, on a church’s Report and on the contact form runs in a frame of Cloudflare’s own, under Cloudflare’s policy. Nothing they set is read by us.

Your choices

Your browser can clear or block cookies. Block the session cookie and you cannot sign in; the rest of the site still works.