One address, monitored
brandonfoster@me.com
Everything reaches the same inbox. Put the topic in the subject line and it gets routed correctly.
Support & contact
One inbox handles support and privacy. Include only what is necessary, and keep credentials and children’s details out of support messages.
Last updated August 18, 2026
One address, monitored
Everything reaches the same inbox. Put the topic in the subject line and it gets routed correctly.
What to write about
We aim to acknowledge messages within two business days. Verified privacy requests are normally completed within 30 days.
Common questions
Most requests we receive are one of these. If your answer is here, you do not need to wait for a reply.
Open the app, go to Settings, then Account, then Delete account, while signed in to the account you want removed. Deletion is authenticated and is complete only once the app confirms it. Signing out or deleting the app does not remove server-side records. Full steps are on the Delete Your Account page.
Email brandonfoster@me.com with the instructor’s name and enough detail to identify the record. We aim to acknowledge within two business days and to complete a verified request within 30 days. We may ask for proof of guardianship first. Contacting the instructor directly is often fastest.
No, not by default. Records move only when someone takes an explicit SkiLink sharing action and directs it to an intended recipient. Share links expire within 24 hours and can be revoked. Private notes, medical notes, photos, videos, and tips are excluded from what a recipient sees.
Core lookup and lesson logging work offline and sync when you are back in range.
No. The app ships without third-party analytics, advertising, attribution, or tracking SDKs, and its App Store privacy manifest declares no tracking. We do not sell personal data and we do not use client records to train models.
Camera access is used to scan SkiLink codes. Location, when you allow it, is used only to identify a home state or region — not to build a route history. Both are optional to the core workflow.
Never send a password, an access or refresh token, a raw SkiLink token, or more detail about a child than the request actually requires.