Privacy Policy

The Short Version

BRYKK is designed to use family data for family safety features, not to sell, advertise to, or profile your family. Family sharing is invite-based: your family's information is shared with the members your family approves, and with anyone you send a temporary share link to while that link is active. Authorized BRYKK operators can also access family data to run, secure, and support the service. BRYKK has no ads, no ad-tracking SDKs, and does not sell personal data. We use the information needed to operate BRYKK on iPhone, Android, and the web, support users, manage purchases where offered, diagnose problems, and deliver family, safety, messaging, and live-drive updates.

What We May Receive

• Aggregate download, installation, app-version, device, and operating-system information from Apple and Google Play
• Country or region-level distribution and aggregate purchase or subscription reporting from the applicable app store
• Crash, performance, and delivery diagnostics supplied by Apple, Google Play, or your device
• A short crash or freeze summary that the BRYKK app sends automatically the next time it opens after a crash or freeze. It carries your device identifier and a scrambled, one-way code made from your family code (not the code itself), plus technical details (app and operating-system version, device model, and where in the app's code the crash or freeze happened). It contains no locations, messages, or contacts.
• Problem reports. When you tap "Send report", the app sends BRYKK support a report: app and phone details and the app's technical log from about the last day (times, what the app did, and why). The app can also send a report on its own when it notices a problem, such as a drive that didn't record, but only if you turn on automatic problem reports; it is off unless you choose it. Before any report leaves your phone, the app strips it: locations are rounded to about 1 km, Wi-Fi network names are replaced with codes, family members' names and your place names are replaced with labels such as “member 1” or “home”, and your family code and device identifier are replaced with one-way codes. Reports never include messages, photos, or contacts.
• Information you choose to send us directly, such as emails to support or legal contacts

We do not run an advertising analytics stack. We do use the following measurements to operate and improve BRYKK:

• Website visits: brykk.app uses Vercel Web Analytics, which does not use cookies, to count page visits. Before a visit is counted, family codes, share-link identifiers, tokens, and query strings are removed from the page address, and the web dashboard is not counted.
• Service usage measurements: BRYKK's service records operational measurements, such as how many families were active and how quickly updates were delivered. These are keyed by hashed (not plain) family and member identifiers, can include the approximate country and, for location updates, the reported speed, and are kept for about 3 months.
• Driving-sensor diagnostics, only if you agree: BRYKK support can ask your iPhone for a diagnostic to tune crash detection. Your phone shows the request and records nothing unless you tap Send; if you don't answer, nothing is sent. After Send, for up to 7 days (or until you turn it off in Settings), the app sends motion-sensor statistics recorded while you drive (acceleration peaks and percentiles, sample rate, gaps when the app was paused, and for each jolt its size, duration, direction, air-pressure change and your speed just before and after), plus the device model, operating-system version, app state, and a hashed member identifier. It does not include your location, places, messages, or contacts.

What the App Processes for Your Family

Depending on how you use BRYKK, the app may process information such as:

• Location and movement status for family members who are part of the same family
• Family membership, family names, join requests, and member roles
• Family chat and voice message content shared inside the family
• Saved places and per-person settings for those places
• Trip history, route-related context, ETA, and movement summaries
• Avatar photos, battery status, weather context, and alert records
• Optional event or calendar context used for departure alerts
• Optional medical details you choose to share with your family (allergies, medications, and emergency notes), only while you turn sharing on

How Family Data Syncs

BRYKK uses BRYKK-operated services, including Cloudflare and Vercel infrastructure, as the authoritative store for family membership, locations, saved places, messages, trips, alerts, and dashboard data across iPhone, Android, and the web.

Family data is encrypted in transit between your devices and BRYKK's services, and our hosting providers encrypt the stored data at rest. Family data is not end-to-end encrypted: BRYKK's service can read it, including locations, in order to provide features such as arrival and departure alerts.

Medical card details are stored on your device. Blood type, date of birth, and sex read from Apple Health are never shared with your family. Your family sees your allergies, medications, and emergency notes only if you turn on Share with my family (off by default), for everyone or for members you pick; BRYKK then stores those fields on its family service. Turning sharing off deletes them from BRYKK's service, and your family's apps show that you haven't shared medical info after their next refresh. If BRYKK detects a possible crash while the app is in the background, your medical card details and the crash location are sent through BRYKK's notification service and Apple Push Notification service to your own device so they can be shown on your Lock Screen; BRYKK's notification service does not store them.

Apple Push Notification service and Firebase Cloud Messaging deliver wake-up hints and notifications so devices can refresh family information. BRYKK does not put precise coordinates, family codes, or private message text in Firebase notification payloads. Map and nearby-safety features may use Apple Maps, OpenStreetMap, Leaflet, Overpass, WeatherKit, or other platform services. iPhone features may also use Apple frameworks such as HealthKit, StoreKit, Translation, and ActivityKit when you enable them. Those providers process limited request, device, or network information under their own privacy policies.

Weather and Road Maps

• Weather alerts: to check for severe-weather alerts (and for a forecast when Apple Weather is unavailable), your phone asks the US National Weather Service (part of NOAA, a US government agency) about the areas around your saved places and your family members' locations. The app sends only an approximate location, rounded to about 1 km, never an exact position, and no names or identifiers. As with any website, the Weather Service sees your phone's IP address. BRYKK does not store these requests.
• Weather radar: the radar map loads its images from NOAA for the part of the map you are looking at.
• Forecasts: Apple Weather (WeatherKit) provides forecasts under Apple's privacy policy.
• Road maps for drives: to show road names and speed limits during a drive, the app downloads road-map pieces built from OpenStreetMap data. Each piece covers an area of roughly 50 km, chosen from your family's saved places and from where a family member is driving. The download comes from BRYKK's storage, hosted by Cloudflare, which sees which area was asked for and your phone's IP address. No names, family codes, or identifiers are sent with it.

What Stays on Your Device

BRYKK also stores certain information locally on your device as needed to make the app work well, such as profile settings, notification preferences, local copies of trips or saved places, medical card details you choose to keep in the app, and local credentials or settings used for family administration.

Family Places and Personal Places

• Family Places are visible to the family members who are meant to share them.
• Personal Places are intended to stay private to your own devices and not appear to other family members.
• Per-person settings for shared places can differ by family member.

Children and Supervised Members

BRYKK is built for family use, including children participating with parental or guardian involvement. Parents and guardians are responsible for configuring and supervising a child's use of the app, including supervised member status and device-level settings that are appropriate for the child.

Identifiers We Use

• A platform or app-generated per-device identifier used to tell family members' devices apart inside a family group
• An app-generated family code and member identifier that link family records to the right person
• An optional phone number you may choose to add to your profile
• Purchase or subscription status from Apple's App Store or Google Play, where offered, used to unlock BRYKK Life features for your family

These identifiers are used to run the app for family coordination, security, and subscription gating, and, in hashed form, for the service usage measurements and diagnostics described above. They are never used for advertising, cross-app tracking, or data brokerage.

Who Can Access Family Data

• Approved members of your family, through their approved devices and any web dashboard they pair.
• Anyone who has a temporary share link you created, until that link expires or is stopped.
• Authorized BRYKK operators, who can access family data to run, secure, and support the service.
• Our service providers (such as Cloudflare, Vercel, Apple, and Google), as needed to host the service and deliver notifications.

Website and Web Dashboard

If you pair a browser with the BRYKK web dashboard, we set one secure, httpOnly cookie that keeps that browser signed in for up to 30 days, and keep a matching session record on our servers (your family code, member identifier, and the name and platform of the device that approved it) for the same period. The dashboard also keeps a small progress marker in your browser's session storage. Signing out ends the session. The dashboard's sample family uses a separate cookie that lasts up to 8 hours.

Permissions We Request

• Location: Used for family location sharing, saved-place alerts, drives, SOS and crash alerts, and weather alerts for your area.
• Motion & Fitness: Used to tell when you're driving, walking, or still, to notice a possible crash, and to save battery.
• Notifications: Used for family alerts, chat, arrival updates, and safety-related notifications.
• Calendar: Used for optional departure-time and schedule-related features.
• Health: Read only, for the medical card: blood type, date of birth, and sex, if you allow them. BRYKK never writes to Apple Health.
• Microphone and Speech Recognition: Used for Translate and for voice messages you choose to send. Speech is turned into text on your phone.
• Bluetooth: Used to find family members' phones when you're near each other, so voice messages and chat can go straight between them.
• Local Network: Used to find family members' phones on the same network, so voice messages and chat arrive faster. Only random codes are shared on the network, not your name or your phone's name.
• Wi-Fi network name: With your location permission, the app can read the name of the Wi-Fi network you're on to recognize your saved places (so it can save battery). The network name stays on your phone; it is not sent to BRYKK, and problem reports replace it with a code.
• Photos: Optional, used only if you choose to set an avatar photo or similar media.

What We Do Not Do

• No ad networks or advertising identifiers
• No sale of personal data
• No contact scraping or address-book harvesting
• No behavior profiling for advertising
• No payment card storage by BRYKK

Payments

If you subscribe to BRYKK Life through an app store, billing and payment processing are handled by Apple or Google. We do not receive or store your full payment card details.

Data Retention

Data retention varies by feature. Today:

• Each member's latest location is kept for 7 days, and detailed location points and drive breadcrumbs for 14 days, then deleted automatically.
• Trips, messages, voice messages, saved places, calendar context, alert records, family membership, profile photos, and app settings do not expire automatically; they are kept until deleted as described below.
• Temporary share links are deleted 7 days after they expire. Closed join requests and push tokens that have stopped working are deleted after 30 days. Removed devices are revoked rather than erased.
• Problem reports and crash or freeze summaries are deleted automatically 90 days after we receive them, or sooner if you delete your account.
• Service usage measurements keyed by hashed identifiers expire after about 3 months.
• Web dashboard sessions last up to 30 days.

Deleting Your Data

• Delete your account in the app: on iPhone, Settings → Privacy → Your data → Delete BRYKK Account & Data; on Android, Settings → Privacy & security → Delete my BRYKK account & data. This erases, from BRYKK's service: your name, photo, and phone number; your live location, location history, and drive breadcrumbs; your trips and route files; messages and voice messages you sent; saved places you created and your place settings; safety alerts and your replies to others' alerts; check-ins; shared medical info; calendar context; temporary share links; device names and permission details; and push tokens. Your devices are signed out and their open connections closed. It also erases what our website holds for you: push registrations, Android sign-ins, web dashboard sessions, temporary share links, and problem reports and crash summaries sent from your devices. The app then erases its own copy on your phone.
• What remains: to stop old devices from signing back in, BRYKK keeps an anonymous record that a member existed in the family (an internal identifier labeled “Deleted member”, with its role and dates) and the revoked device records (identifier, platform, and a one-way hash of the device's secret). The family's change history keeps the type and time of past changes, with their contents removed. Messages other members sent to you stay with the people who sent them. Service measurements keyed by hashed identifiers are not linked back to you and expire on their own (about 3 months).
• Timing: deletion from BRYKK's family service happens immediately when you confirm. Copies on our website and older versions of stored files are deleted within minutes; if a part of the service is unavailable, BRYKK retries for up to 7 days.
• Last member: if you are the last member of your family, leaving or deleting your account deletes the whole family and everything in it. If you own the family and others remain, deleting your account makes the longest-standing admin (or member) the owner.
• Leaving without deleting: when you leave, BRYKK deletes your live location, location history, phone number, shared medical info, calendar context, push tokens, and device details. Trips, messages, and places you shared stay with the family unless you delete your account instead.
• Removed by an admin: when an admin removes you, your data is erased the same way as account deletion, and your own request to delete your account afterwards also succeeds.
• You can remove saved places and your profile photo from the app. Individual messages and trips cannot currently be deleted one at a time from BRYKK's service.
• Deleting the app stops that device from sharing but does not by itself delete family data already synchronized to other family members or BRYKK services. Use account deletion first.
• You can email legal@brykk.app to request deletion of data associated with your use of BRYKK. We may need to verify the family or device before completing a request.

Where BRYKK Is Available

BRYKK is offered in the United States, and BRYKK's services store and process family data in the United States. If you started using BRYKK somewhere else before it became US-only, this policy still applies to your data, and you can still delete your account in the app or by emailing us.

Data Sales

We do not sell personal data. BRYKK uses data to run family safety features, support users, process app-store purchases, and keep the service working.

Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected here with an updated date.

October 23, 2026 (BRYKK 1.1): We added how weather alerts and road maps work: weather alerts ask the US National Weather Service using approximate locations (about 1 km), and road maps download by area from our storage at Cloudflare. We described problem reports: what they contain, what the app strips before sending, that automatic reports are sent only if you turn them on, and that reports and crash summaries are now deleted after 90 days. Crash summaries now carry a one-way code instead of your family code. We added the Local Network and Wi-Fi network name permissions, corrected the iPhone path to delete your account, and stated that BRYKK is offered in the United States.

October 17, 2026: We described our practices more precisely. Family data is encrypted in transit and at rest but is not end-to-end encrypted. We added the website and service measurements we use, and how hashed identifiers are used for them. We stated how long each kind of data is kept today, what leaving a family deletes, and who can access family data, including operators and temporary share links. We added the web dashboard cookie, and that your medical card is sent with a crash alert to your own Lock Screen. Later the same day we changed how three things work and updated this policy to match: medical sharing with your family is now off by default and really controls whether your allergies, medications, and notes leave your phone; deleting your account now erases your data from BRYKK's service, our website, and your phone (what remains and why is listed above); and driving-sensor diagnostics are now recorded only after you agree on your phone.

Contact

Questions about privacy? Email legal@brykk.app.