Who operates the service
The service is operated by Foil Is Life, located in South Lake Tahoe, California, United States, for riders aged 16 and older. We intend to serve riders worldwide, subject to applicable legal availability. Privacy contact: privacy@foilislife.com.
Information used to provide Foil Is Life
Foil Is Life helps riders keep a foiling journal, record their equipment, review saved rides, and contribute to a shared gear catalog.
Account sign-in is handled by Clerk. Our application associates your journal and other saved information with your Clerk account identifier; it does not store a separate copy of your sign-in password.
When you choose Google sign-in, Google and Clerk handle authentication. The Google connection is configured for basic sign-in permissions: openid, https://www.googleapis.com/auth/userinfo.email, and https://www.googleapis.com/auth/userinfo.profile. These provide an account identifier, email address and verification status, and available basic profile information such as name and profile picture. This information supports sign-in and the Clerk account associated with Foil Is Life. The application has its own public profile, which you create and edit separately. Your Google email address is not part of that public profile. These permissions do not give Foil Is Life access to your Gmail messages, Drive files, Calendar, or contacts.
Facebook sign-in is planned and is not currently enabled in production. The planned connection uses only email and public_profile for authentication: the Facebook account identifier, available email address, and basic public profile information such as name and profile picture. Facebook and Clerk would handle sign-in; the Foil Is Life public profile would still be managed separately. This basic sign-in connection does not request your Facebook friends list, photos, or posts and does not post to Facebook. Foil Is Life Friends connections are managed inside this service and do not import Facebook friends.
Information you enter or upload can include:
- Your public profile: display name, handle, and any location, bio, disciplines, and avatar you choose to add.
- Your private garage: brand, model, size, notes, gear photos, lifecycle details, dates, and reusable gear setups.
- Sessions: names, dates, duration, discipline, spot names, conditions, notes, personal ratings, selected gear, and any exact coordinates you enter or confirm.
- Media: photos and videos, file details, captions, and capture dates or coordinates you confirm.
- Community contributions: product submissions, product ratings and reviews, public photo comments, and reports sent for moderation.
We use this information to save and display your journal and equipment, apply your sharing choices, provide account and device access, operate search and catalog features, and handle contributions and moderation.
Apple Watch recordings and device information
When you use the Watch app and grant the relevant device permissions, a recording can contain GPS locations and timestamps, pauses, speed and distance information, heart rate, active energy, and supported water-sensor readings such as wrist depth, temperature, and pressure. Availability depends on your permissions and device capabilities. The Watch app requests HealthKit access to read heart rate and active energy and to save workouts.
Recordings also contain information needed to attribute and synchronize the ride, including account, recording, and device identifiers and recording status. Saved recording files can remain on your Watch or iPhone while awaiting upload and after upload. Signing out or a failed synchronization does not automatically delete these local recordings. Downloaded ride details and exports can also remain on your devices.
Uploaded recordings appear in your private journal. Ordinary public session pages do not expose the recorded route or health readings. A private ride link can expose selected recorded measurements only through the separate choices described below. Your recording export contains precise route and health data; take care when saving or sharing that file.
Public profiles, private garages, and published sessions
Your Foil Is Life profile is public. Visitors can read your display name, handle, optional profile details, and selected avatar. Other profile-library images remain private unless selected as the avatar.
Your garage and personal gear photos are accessible through owner-authorized application features. There is no public garage or inventory page. Retiring gear does not make it public.
New sessions are private. In Manage access, you can choose Only me, Friends, or Everyone and explicitly save that audience. Friends means a mutually accepted Foil Is Life connection. A pending or crossed request grants no access. Accepting a connection permits that person to read existing rides currently marked Friends; removing the connection ends that access. Friends can read shareable session details, broad places, ordinary notes, and the session's saved gear details. Friends access excludes original session media, exact coordinates, recorded routes, and recorded health readings. You can manage these connections and inspect sharing in More → Sharing.
Choosing Everyone publishes that session. A published session can show its session details, notes, attached media, and the gear recorded for that session. Its gear entries contain the saved brand, model, size, equipment reference, and confirmed catalog links when present. They do not expose your garage notes, personal gear photos, acquisition or disposal dates, lifecycle status, or current inventory. Renaming or retiring equipment does not replace a session's recorded gear details.
Exact session and confirmed photo coordinates are included in public data only when you enable the session's exact-location choice. A named spot is separate from exact coordinates. Reviews and comments on public session photos are community contributions visible through their public product or photo pages. Reports are handled through moderation.
Read-only ride links
You can create a link that grants read-only access to a session of any audience. Audience and link access are independent: choosing Only me or removing a friend does not revoke an active link; revoking a link does not change the audience. Anyone who holds that link can use it, including someone to whom it was forwarded. Choose access lasting 24 hours, seven days, or indefinitely until revoked.
The link includes the shareable session details, notes, rider name and handle, and that session's recorded gear. Three additional choices start off and are independent:
- Location: exact location and recorded route.
- Metrics: available recorded measurements, which can include heart rate, active energy, speed, depth, and water temperature. Metrics alone do not include coordinates. Showing heart-rate colors along a route requires both metrics and location sharing.
- Original media: the session's original photos and videos. Those files may contain embedded location, capture details, or other metadata.
Turning off the private ride link revokes future access through that link. Saving replacement link settings creates a new link and invalidates the previous one. Changing the audience alone does not rotate or revoke the link. Expired or revoked links no longer authorize session, route, metrics, or media requests. Deleting the session permanently revokes its existing link; restoring the session does not restore the old link. Revocation cannot remove information or files a recipient already saved.
Photos, videos, and embedded metadata
Photo capture dates and coordinates extracted for review are private suggestions. They become saved photo details only after you confirm them. You can edit or clear saved photo details through your editing controls.
Media is stored privately and shown only after access checks. Private storage does not mean an original file has embedded details removed. Publishing a session makes its attached session media available to visitors; selecting an avatar makes that image public. Review the original files before either action. For a ride-link recipient, original media additionally requires the separate media choice.
Infrastructure and external services
Foil Is Life uses Clerk for authentication, Neon Postgres for application records, and Vercel for application hosting and private Blob media storage. These providers process information required for their roles. Sign-in with Google also involves Google. The planned Facebook connection would involve Meta/Facebook when enabled; it remains disabled in production.
Web maps request map imagery from OpenStreetMap by default, or from the selected map-imagery provider. Such requests reveal connection information, such as the requesting IP address, and the map tiles or area being viewed to that provider. The application draws the ride route without sending your recording file to the map-imagery provider. Broad place-name suggestions use GeoNames place information without sending your coordinates to an outside naming service. Native maps use Apple MapKit.
For moderator review of ambiguous product submissions, the application may send submitted manufacturer, model, and gear category, together with an approved list of possible catalog matches, through Vercel AI Gateway to OpenAI. This feature suggests duplicates for a moderator to decide. It does not receive private garage contents, session recordings, photos, health readings, or Google account information through that workflow, and it does not autonomously merge products.
Authentication uses session-related browser storage. The website also stores display preferences in your browser. These preferences are device-specific.
Your current controls and deletion behavior
You can edit your profile and session details, change session visibility, change exact-location consent, replace or revoke a ride link, remove uploaded media through available owner controls, and review or revoke approved Watch direct-upload access. Revoking a Watch stops future direct uploads; it does not delete rides already in your journal or local device copies. Google account access can also be managed through your Google account settings. If Facebook sign-in is enabled later, its authorization can be managed through Facebook's Apps and websites settings. Unlinking a provider or removing its authorization is separate from deleting your Foil Is Life account and saved data; it can also affect how you sign in.
The journal's Delete action hides a session and makes it private while retaining its media, gear history, and recording so it can be restored. It is not permanent erasure. Restored sessions return privately and require fresh sharing choices. Removing an individual media asset uses a separate operation to remove its stored file and application record.
Permanent account deletion is available through More → Account → Delete account on web and iPhone. Sign in to the account you intend to delete, complete recent sign-in verification if requested, and type DELETE MY ACCOUNT exactly. This action cannot be undone. See the account-deletion instructions for the steps and limits.
When a request is accepted, the application removes the account's profile, sessions, stored recordings and sensor readings, friendship relationships, private garage and setups, reviews, comments, reports, submissions, saved media records, and Watch registrations. Shared rides and links stop working. Uploaded-file deletion and Clerk sign-in-account cleanup continue in the background with retry/recovery when needed. Uploaded files include catalog images you uploaded. Shared catalog products, sizes, and alternate names remain; removed catalog images are no longer shown and identifying author details are removed from product-merge history. Acceptance confirms removal of your Foil Is Life account data and access; it does not confirm that all external cleanup has finished.
The iPhone app attempts to remove saved rides and identifiable temporary files for your account and sends an account-specific cleanup message to a connected Watch. A Watch must receive the message before its local cleanup can run; offline devices and older temporary files without owner information can retain copies. Deletion through the website cannot directly erase device storage. Workouts in Apple Health, exports saved elsewhere, and copies other people saved remain under those holders' control.
After cleanup, we retain a limited record that identifies the deleted account indirectly, along with request, completion, and recovery details, to stop old app connections from recreating its data. Provider backups and any provider-retained records have separate retention arrangements. No immediate universal erasure or fixed provider-backup deletion deadline is promised by this policy.