Privacy

What the camp’s forms keep, where it goes, and who sees it.

Requesting a week

The request form keeps your name, your email, your phone if you give one, the kind of week and the week you pick, how many people are in your group, the ministry name and dates for a ministry week, and your note.

Contact

The contact form keeps your name, your email, your phone if you give one, and your message.

Guest registration

The registration form keeps your name, mailing address, birthday, occupation, group and week, shirt and boot sizes, who referred you, your sex, and whether you are a US citizen. If you are not, it also keeps your country and passport number. It keeps your email, your phone numbers and whether texts are OK, how you are visiting and the dates, and that you accepted the Acknowledgment of Risk. It keeps your emergency contact, your doctor and the office phone, your insurance company, group, certificate and policy numbers, any medical conditions, medications or food allergies you list, and your signature and date.

Sending a recipe

The recipe form keeps your name, your email if you give one, whether you are a guest, family or crew, and the recipe: its title, credit, one line about it, servings, times, what you cook it in, chapter, ingredients, steps and story. A recipe is not published until the camp approves it. A published recipe shows under the credit you gave, or under your name.

Holding beds

The bed-hold form keeps the names of everyone coming, your email, your phone if you give one, the package and the week. You pay in Stripe’s checkout. The camp keeps the booking and the amount, not your card number. After a hold, the airfare form keeps your home airport and up to two airlines.

A group lead can share a link so each guest fills in their own seat. It keeps the name, email and phone typed for that seat. A guest who signs in with their email sees their own week. A group lead also sees each seat’s name and room, whether that guest has registered, and the group’s payments and balance, and never another guest’s contact details or registration.

Where it goes

The request, contact, registration and recipe forms save what you send to the camp’s own site database first, with the page you sent it from and what your browser calls itself. The camp keeps these until someone deletes them. Nothing on the site deletes them on a schedule.

A short notice is then sent through a mail relay run by JKCA Studio, who made this site. The relay mails it to the camp’s front-desk inbox and to JKCA Studio. A request or contact notice carries what you wrote. A registration notice carries only your name, email, group, week and how you are visiting. Your passport, health, insurance, address and emergency contact details are never emailed. A recipe notice carries your name, your email and the recipe’s title.

If the relay can’t be reached, the notice is skipped and the site database still has what you sent.

The mail relay

The relay checks each notice for junk with an automated check that reads it. A notice it scores as junk, doubtful or a sales pitch is held and is not mailed to the camp. JKCA Studio reviews held notices and can release one. The relay keeps a held notice in full: a junk one for seven days, any other for thirty.

For every notice, the relay keeps its own record: your name, email and phone if you gave one, how long your message was, what your browser calls itself, a scrambled version of your network address, and what the check decided. It does not keep your message in that record. JKCA Studio also files a copy of each notice it mails, message included, in its own mail archive. The relay’s record has no deletion date.

Who reads it

Requests and recipes are read on the camp desk, which opens only with a sign-in. Contact messages are not shown on the desk. For a registration, the desk shows whether the guest has registered, and shows any food and health notes on its week page, for the kitchen. The rest of the registration stays in the database. The housekeeping view shows who is in which bed and no medical or contact details.

Analytics

On alaskafc.com we use Google Analytics 4, which sets cookies in your browser, to count visits. When a request, message or registration goes through, it records that one was sent, and which form, not what you wrote. It also counts taps on call, text and email links. In the shop and at the bed-hold checkout it also records what was viewed, added to the bag, checked out or bought, with item names and amounts. The camp desk, guest portal and group seat pages carry no tag.

Bot check

If the contact page shows a Cloudflare check that you are a person, Cloudflare handles that check.

Apparel orders

Orders from the apparel shop have their own page, shop privacy.

Questions

To ask about something you sent us, including a correction or removal, write to info@alaskafc.com.

Your bag

Items
Shipping
Total

Printed to order, then on its way: arrives in about 16 to 19 days.

Checkout