The long version
Balise Privacy Policy
Last updated 29 September 2026 · Publisher and controller: Balise, Inc
Publisher / controller: Balise, Inc. Product site: usebalise.com. Privacy contact: apps@usebalise.com (subject “Balise privacy”).
Balise is not an on-device-only product. Short-lived inference copies are uploaded for cloud vision processing, and structured knowledge is stored server-side for your workspace. Balise does not keep a general archive of Apple Photos images. If you explicitly import selected Instagram photos, Balise privately stores bounded display renditions so those imports remain viewable across your devices.
1. In short
- Your original photos stay in Apple Photos (or another library you connect later). Balise is not a photo backup service.
- If you connect Instagram and explicitly select photos to import, Balise keeps private, encrypted display renditions bounded to 1,504 px in your Workspace so the imported photos remain viewable across your devices. Instagram originals remain at Instagram. This is not a backup or continuous sync.
- For photos you include in processing, Balise uploads a temporary inference render (a bounded 1,504 px HEIC derivative today, not a full-resolution archive) to private Balise infrastructure on Google Cloud so vision models can extract structured knowledge. A private Balise service may derive a WebP rendition for models that require it.
- Balise requests deletion of encrypted inference renders after processing; a one-day storage lifecycle is a cleanup backstop if immediate cleanup is interrupted.
- Balise does not keep a general photo archive. Originals remain in Apple Photos. User-chosen exceptions are selected Instagram photos you explicitly import, the photos of a Story you make and of a card or recap you publish (up to 100 photos each), a drawing you ask for (kept one day), and exact Connected AI photos you approve for one requesting connection. Connected AI access ends one hour after approval and does not include future imports (§4.4).
- If you post to X, X receives what you chose to post, and X’s own terms apply to it. Sending a picture to Instagram, Messages or another app goes through your iPhone’s share sheet; Balise itself sends nothing to that app (§4.4).
- While you are signed in, the app adds text-only entries for your photos — titles, short descriptions, keywords and dates, never images — to your iPhone’s own search index, so iPhone Search and Siri can find them. They stay on your phone and are cleared when you sign out or delete your data (§4.11).
- Balise stores structured knowledge derived from your photos (observations, facts, domains, search indexes, preferences) in your workspace — that is the durable product asset, and it is yours to correct or delete.
- We do not use your content to train models, and we do not authorize our AI providers to train on Balise inference content.
- Balise does not offer a face-identification service or persistent biometric people graph. Recurring-people grouping is opt-in and starts on your device; face templates, crops and embeddings stay there. After an import, a vision model may compare faces within the already-uploaded temporary processing copies once to reconcile obvious duplicate opaque groups. It cannot name people, split groups or create identities, and Balise stores only the resulting opaque alias links. A name you assign may accompany that reference as temporary model context when a future matched photo is processed (§4.6).
- You must be 16+ to use Balise (see §11). Parents photographing their own children for personal knowledge is an expected personal use.
- You can delete all Balise data, or delete your account including the sign-in itself, from inside the app (Your Balise → Photos & imports → “Delete all Balise data”; Your Balise → Account → “Delete account”). See §10.
- We do not sell your photos or knowledge, and we do not show ads.
- The website (usebalise.com) measures visits without analytics cookies, advertising, or cross-site tracking (see §4.8).
2. Who we are
Balise, Inc is the legal entity that publishes Balise and acts as data controller for personal data processed in connection with the Balise service and the usebalise.com website, unless a specific processing is described as performed by a third party as an independent controller (for example Apple operating system services on your device).
2093 Philadelphia Pike #3795
Claymont, DE 19703
United States
1 Chome-23-5 Higashiazabu
Minato City, Tokyo 106-0044
Japan
2-4 rue Jules Lefebvre
75009 Paris
France
Contact: apps@usebalise.com · usebalise.com
Privacy contact. One person at Balise is responsible for privacy questions, for your requests under §10, and for talking to data protection authorities — the role called a data protection officer in Europe and an encarregado in Brazil. Write to apps@usebalise.com with the subject “Balise privacy” and it reaches them. You can write in English, 日本語, français, español or português.
3. Scope
This policy covers:
- the Balise iOS app (iOS 26+), including TestFlight test builds;
- Balise backend APIs and storage used to provide the service;
- Balise’s connector for an AI service you choose: reading your memory and the photos you approve, and a small set of private writes you ask for, each under its own permission — saving a List, saving or updating a discovery, preparing a Story proposal, setting one photo’s reactions and note or correcting a few fields of one record it describes, correcting one Memory episode or one recurring person, and composing a share picture from photos you approved. The connector cannot publish or delete anything (§4.4);
- the entries the app writes to your iPhone’s search index for iPhone Search, Siri and Shortcuts (§4.11), and posting to X when you connect it (§4.4);
- the usebalise.com website, including site analytics;
- related support communications about Balise.
It does not cover third-party websites or apps that link to us, or Apple’s own processing as platform provider (Sign in with Apple, Photos, App Store, TestFlight), except to describe how Balise interacts with them.
4. Personal data we process
4.1 Account and authentication
| Category | Examples | Source |
|---|---|---|
| Identity / auth | Clerk user id, sign-in identifiers (for example Sign in with Apple), session tokens, and the email or name held by Clerk if your sign-in method provides one. Balise’s own servers store only the Clerk user id and use it as your workspace id. | You / Clerk / Apple |
| Workspace linkage | Workspace id, provisioning state, role | Generated by Balise |
| Push notifications | Device push token, if you allow notifications, so we can tell you when a round is done | You / Apple |
4.2 Photo library inputs
With your permission via Apple PhotoKit, Balise receives, for the assets you include:
- image content (to create a temporary inference render for cloud vision — not to archive your Camera Roll). The render is re-encoded on device with camera metadata (EXIF, GPS, maker notes, thumbnails) stripped from the file;
- capture / modification timestamps and the capture time-zone offset;
- location metadata when present on the asset (GPS coordinates, altitude, heading, accuracy from the photo — not live tracking of you) and a place name resolved on device from those coordinates;
- This is precise location. The coordinates are stored with the photo in your workspace and can be searched, for as long as that photo’s knowledge is kept (§9). They are how Balise places a photo on the map and answers where you were. No setting keeps location out of processing today: to keep a photo’s location from Balise, remove it in Apple Photos before importing, or leave that photo out;
- Place lookup at Google. To name the venue in a photo and to fill in geography the photo does not carry, Balise also sends the photo’s coordinates from our servers to Google Maps Platform (Places API and Geocoding API) and keeps the candidates it returns. Google receives the coordinates and nothing else — no image, no account identifier, no name. If a photo has no location, nothing is sent for it;
- an optional positive “near home” hint computed on the originating device, without copying the separately stored home-zone label, center, or radius onto the photo record;
- album membership, including album names (for inclusion / exclusion rules and as context);
- technical flags and camera settings (for example screenshot, favorite, edited, dimensions, camera model and lens, exposure, flash) and any caption you typed in Photos;
- on-device Vision results: number and position of faces and people, whether you appear (§4.6), animals, whether text is present, and quality scores — never the recognized text itself, and never face templates of other people;
- PhotoKit local identifiers and, where available, cloud identifiers, and a per-install device identifier, used for deduplication and to link facts back to the photo on your device.
These facts travel with the render as structured data (not inside the image file), are stored with the resulting knowledge, and are given to the vision model as context for describing the photo.
Instagram imports. If you connect a supported Instagram Creator account, browsing alone does not import anything. When you explicitly choose still photos to import, Balise receives their image content, stable account/post/media identifiers and your username, carousel order, posting time, and the original permalink where available. To learn how you write, Balise uses the captions of the posts you choose to import: they shape the wording of your drafts, stay in your account, are never used to train models, and are deleted when you remove that import or delete your account. Balise does not request comments. A few of them, with how long you usually write and whether you use emoji or hashtags, go with a draft request to the model that writes it; nothing from them is added to your photos, your Memory or search. You can see, clear or turn this off in Studio settings › Your voice; turning it off deletes the kept captions. If Instagram does not share a caption, none is kept. Posting time is not treated as capture time. Videos are not imported as photos. Balise keeps the Instagram authorization encrypted with a Google Cloud KMS key in its database. Disconnecting Instagram in the app deletes it; to revoke Balise at Instagram as well, use Instagram’s “Apps and websites” setting.
Defaults and limits
- You choose how many photos and which period Balise should consider; the app samples evenly across that period. With full Photos access you can also limit an import to the albums you pick; with limited access, Balise only sees the photos you picked yourself in Apple’s photo sheet.
- Hidden albums and shared albums are always excluded; this cannot be switched on.
- Limited Photos access (iOS) is supported: Balise can only see the photos you picked in Apple’s sheet.
- Photo-library permission does not mean every asset is uploaded immediately or at all.
- Keep up as you shoot (new photos picked up automatically) is off unless you turn it on. It is available on every plan, Base (the free plan) included.
4.3 Temporary inference media
Bounded inference renders uploaded for cloud vision processing. These are short-lived processing copies, not an archive of your Camera Roll. Balise requests deletion of encrypted copies after processing, including any enabled post-import People comparison; a one-day storage lifecycle is a cleanup backstop if immediate cleanup is interrupted; failed, skipped, cancelled, reset, and explicitly deleted work is cleaned sooner where possible. The storage soft-delete window is set to zero so a deleted copy is gone.
4.4 Image copies (no photo archive)
Balise does not keep a general archive of Apple Photos images. Originals stay in Apple Photos. The choices below retain only what their screens describe: selected Instagram imports, published cards and recaps, Stories, drawings you ask for, and private Connected AI renditions.
Selected Instagram imports remain private in Balise. For each still photo you explicitly import, Balise stores an encrypted display rendition bounded to 1,504 px in your Workspace. It is not publicly accessible by default and remains available across your devices even if you disconnect Instagram. We keep it until you delete that imported photo, delete all Balise data, or close your account. The original remains at Instagram; Balise does not back up the original or continuously synchronize the account. Storing this rendition does not authorize blanket access by Connected AI: the exact-photo approval and one-hour access rule below still applies.
Sharing a picture from your phone uploads nothing to Balise. Balise can turn photos and what it noticed in them into a share picture — a card, a collage, a contact sheet. Rendering it, saving it to your photo library, or sending it through your iPhone’s share sheet to Messages, Instagram, WhatsApp or another app happens on your phone. The app you send it to receives it under its own terms; Balise itself sends nothing to that app and holds no permission to post there. To suggest a style, the share sheet may send a model the text facts Balise already holds about the chosen photos (the place only when “Show place” is on) — never the pictures.
Publishing at a link is opt-in, one share at a time. Only if you choose to publish a share at a link do we store anything, and only for the photos in it. For a card: the card image your phone rendered, a preview image for when the link unfurls, and display-sized copies (up to 1,600 px on the long side) of the photo and of the other photos of that moment you keep in it. For a recap: a cover and one slide per photo you selected (about 1,350 px), which may come from several days. A share holds up to 100 photos. Your phone encrypts them before upload, and a private Balise service unpacks them into the private storage the link is served from.
Those are kept until you delete them — there is no expiry, because a dead link in something you posted is a broken promise. The address is unguessable and carries noindex, so we ask search engines not to list it, but a link is a link: treat a published share as public. Take one down in the app (Studio) or from the page itself; deletion removes the images and then the record, the address answers “gone” afterwards, and it is never reused. Deleting your data or your account removes published shares too. Payment card digits are never part of a card: they are discarded when it is made, not hidden when it is shown.
Stories are opt-in, one at a time. Balise can write a short Story — a title, a few sections of prose, and the pictures it is about — about a moment, a day, a trip, or up to 24 days you pick. Nothing is uploaded until you ask for a Story and confirm its photos. Then we store copies of up to 100 photos you chose — Balise suggests, you decide — bounded to 1,504 pixels on the long side, and the text written about them. Your phone encrypts the copies before upload. Nothing else from your library is copied.
A published story page shows a small map, and that map is an embedded frame from OpenStreetMap. It carries the story's coordinates, so anyone who opens the page contacts openstreetmap.org directly and OpenStreetMap sees their IP address and the place the story is about. That happens in the reader's browser, not on our servers, and only on a page you chose to publish.
A model looks at some of those photos in order to write. To choose and arrange the pictures and to write the text, the Story models — today OpenAI’s, and Anthropic’s Claude through Amazon Bedrock or Google Vertex AI, all via Vertesia — are shown at most twelve of the Story’s photographs as images, the key pictures, through access links that expire within fifteen minutes. The Story’s other photos, and the rest of the moment, reach them only as the text notes Balise wrote during import, together with any line you typed about how to tell it. Connected AI is a separate, user-directed connector. We do not authorize our AI providers to train on Balise content.
You read it first: a Story is a private draft until you publish it, and you can retitle it, rewrite any section, move pictures between sections, drop a section, or have one written again. Published, it sits at an unguessable address carrying noindex — but a link is a link, so treat a published Story as public. Unpublishing takes the link down and keeps the Story, photos included, as your private draft. Deleting it — in the app (Studio) or from the page itself — removes the pictures, the text and any drawn cover, then the record; the address answers “gone” afterwards and is never reused. A Story’s photos and text are kept until you delete the Story, your data or your account. Card numbers are never written into a Story at all.
Drawings are opt-in, one tap each. If you ask Balise to redraw one to four photos in an art style — for a share picture or a Story cover — your phone sends those photos to Balise (at most 1,024 px on the long side, protected in transit by TLS rather than by the per-photo encryption imports use), or Balise uses the Story’s own copies. Balise passes them through Vertesia to xAI’s Grok Imagine image model, or to Google’s Gemini image model if Grok is unavailable. Photos Balise has marked as health-related or sensitive are refused. The photos are deleted as soon as the drawing is made, with a one-day storage lifecycle as backstop. The drawing itself is kept privately for one day so you can use it, then deleted; a drawing you keep as a Story cover stays with that Story until you delete it. The app asks you once before the first drawing, nothing is drawn unless you tap, and there are at most 20 drawings a day.
Posting to X is opt-in, one post at a time. You can connect your X account from the app. Balise asks X for permission to read your profile, to post and upload media on your behalf, and to stay connected (tweet.read, tweet.write, users.read, media.write, offline.access). It keeps your X user id, your username and the access tokens in its database, the tokens encrypted with a Google Cloud KMS key. Balise posts only when you tap to post: a picture post carries the picture and the text you approved (up to 280 characters); an X Article made from a Story you published carries its title, subtitle, headings, text, captions and photos, with a link back to the Story. Balise records that an Article was posted (its X identifiers and status); it keeps no copy of a picture post. Once posted, the content is on X under X’s own terms and privacy policy. Deleting or unpublishing a Story in Balise does not delete what you posted — delete it on X. Disconnecting X in the app asks X to revoke the tokens and deletes them from Balise.
Connected AI is facts-only by default. Your assistant may request up to 24 exact photos. Balise shows every selection in the app and sends nothing unless you approve it within 10 minutes. Approval lets only that requesting connection access those exact 1,504 px display copies for one hour from approval; fetching a photo again does not extend the hour, and future imports or later selections require another approval. Expiry blocks further access through Balise; it does not erase images already received by the assistant or remove them from your conversation. At most four selected images may be returned in one authenticated response. There is no public image URL. The iPhone encrypts its HEIC rendition before upload; originals stay in Apple Photos and Balise keeps no general photo archive.
Balise does not automatically receive or store your Claude or ChatGPT conversation. It receives the arguments sent in authenticated connector calls. The connector can also make a few private changes you ask for — each only if you granted its separate permission when connecting, and some only after your assistant asks you to confirm: save a new private text List or replace one of yours (Lists permission); save a published Story or highlight to your private discoveries, or change your reactions or note on one (discoveries permission); save a private Story proposal — text and photo references only, which you review in the app, where photos are uploaded only if you go on to create the Story (Stories permission); and, with the Memory-corrections permission, set one photo’s reactions and note, correct a few fields of one record extracted from a photo (Balise keeps the original values), and correct one Memory episode (its title, favorite, place, hidden state, or one photo linked to it) or one recurring person (a name and a relationship). It can also compose a share card or collage from one to four photos you approved; that image is returned to your assistant, and Balise neither saves nor publishes it. The connector cannot publish or delete anything, cannot change a published List or Story, and cannot confirm anyone as you. Once your chosen service receives facts or images at your direction, its own terms, privacy policy, account controls, and retention choices apply. What §5.1 says about training covers Balise and its subprocessors, not an independently chosen Claude or ChatGPT account.
Public profiles are a separate, optional publishing surface. You can reserve an @handle and publish a display name, short bio, and links to cards, recaps, stories, or Lists you already published. Making the profile public does not make your indexed photo library, Apple Photos originals, or private Connected AI copies public; it exposes only the profile and links to material you had already published. Profiles are meant to be findable and may be indexed. If you ask Balise to prepare a draft, it uses only the public-safe titles and summaries of that already-published material; the draft stays private until you edit, curate, and publish it. You can unpublish it at any time. An old handle remains reserved to you so nobody else can take over an address you shared.
Saved Lists are text, not image copies. When Ask assembles things or places from your photo knowledge, nothing new is retained until you tap Save or Share. A Connected AI service may save or revise a private List only after you ask or approve the operation. Saving keeps the List text and private links back to the supporting photo records in your Workspace; it does not copy or publish those photos. Sharing publishes only the list title, summary, item names and descriptions at an unguessable noindex address. Anyone with that link can read it. It stays until you delete it in the app (Studio) or delete your Balise data; deletion removes the text and the address then answers “gone”.
4.5 Structured knowledge (durable)
- observations and extracted facts (objects, text cues, places, domain-specific fields) — including structured descriptions of photos that may depict children or other people when you included those photos;
- provenance linking facts to evidence identifiers;
- domain / interest configurations and insight definitions;
- search indexes and embeddings of structured content (not a photo backup);
- corrections and preferences you provide;
- your optional home-zone label, center and radius, stored as a private workspace setting rather than on any photo record;
- an import ledger used for deduplication and “already processed” state (photo identifiers, capture time and photo location, dimensions, status — not your original file);
- your preferred language, notification registration, and subscription entitlement state (from Apple’s StoreKit, no card details).
4.6 On-device processing, private home context, faces and the self reference
On device, Balise uses Apple frameworks (PhotoKit, ImageIO, MapKit, Vision) to select, sort and downsize photos before upload, to resolve a place name from the photo’s coordinates, and to detect faces, people, animals, text and foreground. Naming the venue itself happens on our servers, through Google Maps Platform, from the coordinates alone (§4.2). Counts, boxes, head angles, scores and optional random opaque person references may leave the phone; recognized text, face crops, landmarks and feature vectors do not.
Home area. If you choose a MapKit zone as home, Balise stores its broad label, center coordinate and small radius as a private workspace setting and mirrors it in protected storage on your signed-in device. Balise’s agents may use that selection as your explicit home context. It is not stored as a street address and is not copied onto photo records; a photo made inside it may carry only a positive home hint. You can replace or forget the zone in Profile at any time. Forgetting it deletes the server setting and the local mirror.
Self reference. A front-camera photo or Apple’s Selfies album does not identify who is pictured. Balise therefore treats every automatic candidate as untrusted. Only after you explicitly confirm a local self reference may the app compare faces on device and upload a yes/no self-presence result with confirmation provenance. The reference vector remains on your device and is never sent to Balise or a model provider. Older account vectors are deleted by the service.
Recurring people. Where supported and only if you turn the People feature on, the app uses Apple Vision face landmarks and a bundled on-device model to group recurring faces, then assigns random workspace-scoped identifiers so you can browse the same person across photos and optionally tell Balise who they are. Face crops are not stored; face-embedding templates are encrypted in the app’s local database with a device-only key and stay on the device. After a completed import, Balise may make one bounded vision-model comparison over faces already present in the private temporary processing copies, solely to merge two whole opaque groups that unmistakably depict the same person. The model cannot split a device group, name anyone, create a person id or describe sensitive traits; the server independently refuses a merge when the groups co-occur in one photo or conflict with labels you supplied. Medium- and low-confidence proposals are not applied. No cloud face crop, template or embedding is retained; the processing copies are deleted after processing, including this comparison, with a one-day cleanup backstop, and durable cloud state holds only opaque identifiers, photo membership, merge history, and labels or relationships you enter. If you give a People entry a name, Balise may include that user-authored name as temporary context when a cloud vision model processes a future photo your device matched to the same opaque identifier, so the description can use the name you supplied; the structured actor remains opaque, and a name does not establish a family, friendship or other relationship. Balise does not infer a person’s name or relationship from their face and does not run a general-purpose face-identification service.
4.7 Operational and diagnostics data
- API logs, IP address, device / app version, and crash or performance signals from Firebase Crashlytics, Firebase Performance Monitoring and Apple MetricKit;
- fixed product-interaction events (app open, import, first card, collection, search, Ask and plan actions), linked to your workspace so we can measure activation and retention; these events never contain search text, Ask prompts, photo or collection identifiers, notes, or arbitrary properties;
- if you installed Balise from an Apple Ads campaign on the App Store, the campaign, ad group, keyword and ad identifiers that Apple’s attribution service reports for that install, with its country or region, whether it followed a tap or a view, and when — linked to your workspace so we can tell which campaigns bring people who go on to use Balise. After you sign in, the app asks Apple once for an attribution token and Balise’s API exchanges it with Apple; the token is not kept, no tracking permission or advertising identifier is involved, and nothing is sent to an ad network. If the install did not come from Apple Ads, we record only that;
- Redis / Memorystore operational state (job progress, locks, manifests, short-lived tokens) — not a durable photo store;
- a control database (Cloud SQL) holding import batches, the import ledger, entitlement usage and an audit trail of account actions (for example that a data reset completed);
- security and abuse-prevention signals.
Shipping iOS builds use Firebase Crashlytics and Performance Monitoring for operational diagnostics. Google Analytics is not linked, and Balise does not use an advertising identifier or cross-app tracking. Full Apple MetricKit diagnostic payloads stay bounded on the phone; only numeric summaries go to Firebase Performance. Product interaction events go to Balise’s own authenticated API and are stored in PostgreSQL. When server forwarding is enabled, Balise may also send the same closed events to PostHog under a pseudonymous workspace identifier; no new analytics SDK is added to the app. Forwarding is disabled in development and preview environments and is enabled in production only after remote deletion is configured. Resetting the workspace or deleting the account requests queued deletion of the corresponding PostHog person and events; if that request cannot be submitted, the reset does not report success.
4.8 The website (usebalise.com)
- Pre-launch waitlist. Before launch we kept a waitlist. If you joined it, we keep that sign-up (your email, the note you left, and when you signed up) only to tell you Balise is available, and we delete it when you ask.
- Site analytics. Balise’s own browser code sends pseudonymous typed events to
/api/e; our Cloudflare Worker validates them and forwards them to PostHog’s US ingest service. We may record a random per-tab session id in session storage, a page path with shared-object ids removed, device/browser/operating-system categories, country, referrer domain only, short source andutm_source/utm_medium/utm_campaign/utm_contentcodes, page variant, and typed controls or events. We do not forward IP addresses, email, form text, photo content, full query strings,utm_term, or referral codes. There is no PostHog browser script, analytics cookie, replay, autocapture, advertising, or cross-site tracking. Do Not Track and Global Privacy Control disable collection. The per-tab id does not persist across visits, and website attribution is not automatically joined to an app workspace. - Cloudflare Web Analytics. Cloudflare may also measure aggregate traffic and site performance without cookies.
- Language cookie. If you pick a language path (for example /fr), the site sets a single functional cookie,
balise_lang, to remember it. Nothing else is stored in cookies. - Hosting. The website and its API run on Cloudflare (Workers, KV, Email Service). PostHog processes the limited pseudonymous analytics events in the United States.
4.9 Support communications
If you email us, we process your address and message content to respond.
4.10 Sensitive information in your photographs
A camera roll is not a neutral archive. Over a few years it will contain a hospital corridor, a prescription on a kitchen table, a place of worship, a demonstration, a partner, a child. Several countries treat information like that as a special category that needs more care than ordinary personal data — special category data under the GDPR, dados pessoais sensíveis under Brazil’s LGPD, 要配慮個人情報 under Japan’s APPI. Here is how Balise handles it.
Explicit photos are set aside before Balise looks closely. When a photo is flagged as explicit at the first glance, Balise stops there: the processing copy is deleted, no description is written, and nothing about the photo enters your knowledge. Balise keeps only the fact that the photo was set aside, so it is not picked up again on a later round. Your import summary shows you a count of the photos this happened to.
Health photos stay out of everything that narrates your life. When Balise notices that a photo concerns health or healthcare, it marks it, and that mark sticks. A marked photo is kept out of Stories, story highlights, the photos an editor can add, Memory prose, the material the Memory writer can see at all, episode covers and hero images, the photo strip on the map, share-card picture plans, and any description Balise writes about a person. The photo stays where it belongs in the day it happened; what it does not do is get written about or put on a cover.
Two honest limits. Photos processed before this labelling existed may not carry the mark — for Memory prose we leave out any witness that is not labelled rather than risk it, but the other surfaces rely on the mark being there. And if you deliberately send a photo to a connected assistant, Balise sends the photo you chose; the health mark does not overrule your choice.
Faces. Grouping recurring people is biometric processing in most of these laws, which is why it is off unless you turn it on, why the templates and vectors never leave your iPhone, and why the cloud holds only random identifiers, the merge history, face boxes and head angles, and the names you type yourself (§4.6).
Religion, politics, sex life, ethnicity. Balise does not set out to infer any of these and does not build audiences or profiles from them. Facts of that kind can still end up in a description if they are plainly visible in a photograph you chose to include — a wedding, a march, a shrine. You can correct or delete any of it (§10), and the controls that matter most are the ones at the start: give Balise limited access and pick the photos yourself, or keep a period out of range.
Precise location. Several US states count a photo’s exact coordinates as sensitive data in their own right. Balise keeps them with the photo and uses them to place it (§4.2) — that is providing the service, not a use beyond it.
4.11 iPhone Search, Siri and Shortcuts
What the app writes to your iPhone. While you are signed in and using the app, Balise adds one entry per photo to your iPhone’s own search index (Apple’s Core Spotlight), so iPhone Search and Siri can find your photos by what Balise learned. Each entry holds only text: a title (up to 80 characters), a short description (up to 360 characters), up to 24 keywords — collection names, place names (the venue, city, region and country), the scene, and the capture date — and the capture time. It holds no image, no coordinates, no person identifier and no Apple Photos identifier; the entries are labelled with a one-way fingerprint of your account rather than your account id.
Where it lives. The index is on your iPhone, protected by iOS data protection, and managed by iOS. The app refreshes it while it is open; an entry that is not refreshed expires after seven days. Typing in iPhone Search looks only at that local index — Balise does not receive your Spotlight searches. Opening a result opens Balise, which then asks our servers for that photo as it would in the app. The whole index is cleared when you sign out, switch accounts, delete all Balise data or delete your account, and an entry goes when you delete or hide its photo.
Siri and Shortcuts. “Search Balise” opens the app with your words in Search. “Find Balise Photos” sends your words (up to 240 characters) to our servers as an ordinary search and returns at most eight text results — title, description, place and date — with no image; your iPhone must be unlocked. What Siri or Shortcuts does with those results on your device is governed by Apple.
Your control. The app shows the index’s status in Your Balise → App → Spotlight. It has no switch of its own; to keep Balise out of iPhone Search and Siri suggestions, turn off Balise’s search and Siri suggestions in the iPhone’s Settings (under Apps → Balise, or Siri & Search, depending on your iOS version), or sign out.
5. Why we process data (purposes and legal bases)
The purposes, stated plainly. We use your personal data to: create and secure your account; process the photos you choose and build the structured knowledge, collections and Memory that Balise is for; run the cloud inference that does that processing; make the Stories, shares and drawings you ask for, and publish or post them where you choose; let an AI service you connect use your Balise at your direction; make your photos findable in iPhone Search and Siri; tell you when a round of work is finished; keep the Service reliable, debug it and prevent abuse; answer your support messages; learn which of our Apple Ads campaigns bring people who go on to use Balise; understand how the website is used; and meet our legal obligations. That is the whole list. We do not use your data for other purposes, and if we ever want to, we will tell you what the new purpose is before we start (§15). The table below adds the legal basis for each purpose for readers in the EEA and the UK.
| Purpose | Data (high level) | Legal basis |
|---|---|---|
| Create and secure your account | Auth identifiers, sessions | Contract (Art. 6(1)(b)); legitimate interests for security |
| Provide library processing and knowledge features you request | Ephemeral inference renders, structured knowledge, preferences | Contract |
| Ephemeral cloud inference | Inference renders, model input / output | Contract |
| Stories, shares and drawings you ask for; publishing at a link; posting to X | The photo copies you chose, the text written about them, model input / output, your X authorization and what you post | Contract, on your explicit request for each one |
| Connected AI you authorize | Connector grants and scopes, the arguments of each call, facts and approved photos returned, the private changes you ask for | Contract, at your direction; photo delivery only on your approval of each request |
| iPhone Search, Siri and Shortcuts | Text-only index entries on your device; the words of a “Find Balise Photos” request | Contract |
| Tell you when a round is done | Push token | Contract / consent (iOS notification permission) |
| Improve reliability, debug, prevent abuse | Logs, operational metadata, salted IP hashes | Legitimate interests; legal obligation where applicable |
| Learn which Apple Ads campaigns bring people who use Balise | Apple’s campaign, ad group, keyword and ad identifiers for your install | Legitimate interests (no tracking permission, advertising identifier or sharing with ad networks) |
| Understand how the website is used | Pseudonymous interaction events | Legitimate interests (no analytics cookies, advertising, or cross-site tracking) |
| Support | Email content | Contract / legitimate interests |
| Comply with law | Limited records, deletion audit entries | Legal obligation |
Publishing a share or a Story at a link, and posting to X, are processed on the basis of your explicit choice for each one, and last only as long as you keep them (§4.4).
5.1 No training, no selling
We do not sell personal data. We do not use your photos, inference renders, structured knowledge, or other customer content to train machine-learning models. We do not authorize our AI subprocessors (Vertesia, OpenAI, Google Vertex AI / Gemini, xAI, Anthropic, Baseten, and Amazon Web Services as used through Vertesia) to use Balise inference content to train their models. Providers process content only to deliver inference and related Service features for your workspace.
6. How processing works (pipeline)
- You authorize Photos (full or limited) and choose how many photos and which period.
- On-device rules decide which assets are eligible (hidden and shared albums always out; the sample spread evenly across the period).
- For each eligible asset, Balise creates one bounded 1,504 px HEIC processing copy, encrypts it on the iPhone, packs encrypted copies into an archive and uploads it over TLS, via a short-lived signed URL, to a private Balise inference bucket on Google Cloud Storage, together with the photo facts listed in §4.2 as structured data. A dedicated private Balise service decrypts copies for processing and derives an encrypted 1,504 px WebP version when needed.
- Vision models (orchestrated by Vertesia; currently OpenAI and Google Vertex AI / Gemini paths) analyse a temporary render and extract structured evidence. Google’s Vertex path receives a separate temporary private cloud input with expiring access, currently ten minutes. This input has cloud storage encryption rather than the phone’s per-image encryption. OpenAI-compatible paths receive short-lived access through Balise. Later text-only steps may use Gemini, OpenAI (including through Amazon Bedrock for Ask), xAI (Grok), Anthropic (Claude, including through Amazon Bedrock), or open models served by Baseten (DeepSeek, which interprets what you type in Search, and GLM, a fallback for Memory structure) through Vertesia. Stories and drawings you ask for are the two features that show a model your photos again after import (§4.4). Memory construction receives a bounded, filtered packet of extracted witness names, descriptions, domains, time and coarse place context; it does not receive photos, full Search text, exact home coordinates, healthcare content, or document bodies. Other text-only steps receive the bounded schema, account, event-story, or non-sensitive profile fields needed for that operation.
- Structured results are written to your workspace (Vertesia content objects and search index) and to the control database ledger.
- Balise requests deletion of encrypted inference objects after processing, including any enabled People comparison; a one-day lifecycle removes stragglers if immediate cleanup is interrupted.
- Balise keeps no general image archive. Explicitly selected Instagram imports keep the private bounded display rendition described in §4.4.
New photos after the first import. You can send more rounds by hand. “Keep up as you shoot” picks up new photos automatically when you turn it on, on every plan, Base included. The app UI for your build is the source of truth for whether newly added photos are being picked up.
7. Processors and subprocessors
We use service providers (“processors”) to operate Balise. They process data on our instructions. The list below reflects company-confirmed vendors and the deployed infrastructure for the Balise Google Cloud project (region us-central1 today).
| Provider | Role / purposes | Data typically involved |
|---|---|---|
| Clerk | App authentication and OAuth authorization for Connected AI | Account identifiers, auth metadata, email if provided, connector grants and scopes |
| Google Cloud / Firebase | Hosting and infrastructure: Cloud Run (API and import services), Cloud Storage (private inference media, selected Instagram display renditions, and request-approved Connected AI copies), Memorystore (Redis) (short-lived leases and disposable caches), Cloud SQL (control database, import ledger and fixed product events), Cloud KMS (encryption-key operations, including sealing the Instagram and X authorizations you connect), BigQuery (the audit log of account actions), Secret Manager, Artifact Registry, networking; Firebase Crashlytics and Performance Monitoring; Vertex AI / Gemini when Vertesia routes inference to Google’s Vertex environment | Temporary processing copies, selected Instagram display renditions, and request-approved Connected AI copies; ledger and operational data, fixed product events, crash/performance and installation diagnostics, model input / output for the Vertex path |
| Temporal Cloud | Durable import and task workflow execution, timing and retries | Opaque account and work identifiers, workflow state, timing and redacted failure metadata; no photo bytes or provider credentials |
| Vertesia | Durable workspace knowledge, search, agents / workflows, and inference orchestration using short-lived media access supplied by Balise (US region today) | Structured knowledge, workspace-scoped credentials, run metadata; temporary media access for inference |
| OpenAI | Vision / model inference via Vertesia using short-lived HTTPS media access supplied by Balise; arranging and writing Stories; Ask; text-only design and Memory steps. Some Ask steps run on OpenAI models through Amazon Bedrock | Temporary media references / model inputs and outputs; up to twelve photos of a Story you ask for, with its text notes |
| xAI | Drawing the photos you ask to have redrawn (Grok Imagine); text-only model inference via Vertesia for collection portraits, a bounded non-sensitive person description, and committed Memory prose (Grok) | The one to four photos of a drawing you asked for (at most 1,024 px) and the art style; domain schemas and templates; bounded non-sensitive aggregate counts, filtered domain examples and facets, committed accounts and event-story text |
| Anthropic | Model inference via Vertesia (Claude), through Amazon Bedrock or Google Vertex AI: writing Stories, domain design, year-level Memory prose and fallback processing | Up to twelve photos of a Story you ask for, with its text notes; bounded structured text, committed accounts, event labels and event-story text — no photos for the Memory writing steps |
| Amazon Web Services | Amazon Bedrock inference infrastructure used by Vertesia for some Anthropic Claude paths and some OpenAI Ask steps | The bounded model input and output for the applicable step, including a Story’s photos when Claude writes it there |
| Baseten | Text-only inference via Vertesia on open models it hosts: interpreting what you type in Search (DeepSeek), and a fallback for building Memory structure (GLM) | Your search text and the facet vocabulary it is matched against; for the Memory fallback, a compact table of extracted descriptions, times and coarse places — no photos |
| Google Maps Platform | Naming the venue in a photo, filling in missing geography and finding a time zone: Places API (New), the Geocoding API and the Time Zone API, called from our servers | Coordinates only — no image, no account identifier, no name |
| Meta (Instagram) | Only if you connect Instagram: reading the media you chose to import | Your Instagram authorization, account id and username, and the media, permalinks and captions of the posts you import (captions only to learn your writing voice; no comments) |
| X Corp. | Only if you connect X: a recipient of what you choose to post, not a processor. X handles it under its own terms and privacy policy | Your X authorization; the picture and text of a post, or the title, text, captions and photos of an Article, that you chose to post |
| Cloudflare | Website hosting, first-party analytics endpoint, cookie-free aggregate Web Analytics, and email (Email Service): subscription confirmations and the updates sent to people who follow a publisher | Subscriber and follower email addresses, IP data used at the edge for rate limiting, limited pseudonymous interaction events, aggregate traffic and site-performance measurements |
| PostHog (United States) | Website analytics; optional server-side closed product events and sanitized error reporting | Pseudonymous typed events and static error summaries; browser errors may include an allowlisted script filename and line number; no photo content, form text, or IP address forwarded by Balise |
Apple (platform, not a Balise AI subprocessor): OS, PhotoKit, Sign in with Apple, push notifications, App Store / TestFlight distribution and crash reports, and the on-device search index behind iPhone Search, Siri and Shortcuts (§4.11). Apple acts under its own terms for platform services.
We also hold an account with OpenRouter for evaluating models; it would stand behind Baseten for the GLM model only in a deployment where Baseten is not configured. It is not in the production route today, and we do not send customer content to a model vendor whose terms permit training on it — some vendors reachable through OpenRouter have exactly such terms, which is why they stay out of the route.
We require processors to protect data appropriately. We do not authorize processors to use Balise customer content to advertise to you or to train models on Balise inference content.
What deletion does not reach. Deleting your data removes it from Balise, our storage and our analytics. It cannot reach back into a model provider's own operational logs; those providers keep limited records under their own terms and retention periods, and we do not control them.
8. International transfers
Balise infrastructure and processors may process data in the European Union and other countries, including the United States (the Google Cloud project runs in us-central1 today; Vertesia runs in its US region today; OpenAI, Vertex, xAI, Anthropic, Baseten and Amazon Bedrock paths may also process outside the EEA; PostHog processes limited analytics events in the United States; Cloudflare runs a global network), depending on provider regions and account configuration.
Which countries, in plain terms. Today, the substance of Balise — the servers, the temporary photo copies, your structured knowledge, and the models that process them — runs in the United States. Cloudflare serves the website from wherever you are. No other country holds your data as a matter of course.
What that means for the United States. The United States has no single comprehensive federal data protection law. Protection there comes from sectoral and state laws, from the contracts we hold with each provider in §7, and from the technical limits described in §13 — not from an equivalence with your own country's law. US public authorities may in some circumstances compel a provider to hand over data.
From the EEA/UK. Where required, we use appropriate safeguards — such as Standard Contractual Clauses — for transfers to countries without an adequacy decision.
From Brazil. Personal data of people in Brazil is processed in the United States by the providers named in §7, for the purposes in §5. We give you this information so your transfer decision is an informed one, and we hold each provider to the protections described here.
From Japan. Personal data of people in Japan is processed in the United States by the providers named in §7. We are telling you the destination country, the fact that it has no comprehensive national data protection law, and the measures each recipient takes, so that you can decide with that in front of you.
9. Retention
| Data | Retention |
|---|---|
| Inference renders (temporary) | Deletion requested after processing, including any enabled People comparison; a one-day lifecycle removes stragglers if immediate cleanup is interrupted; failed/cancelled/reset work cleaned sooner where possible; zero soft-delete window |
| Connected AI request copies | Exact photos only after in-app approval; available only to the requesting connection for one hour from approval, without extension on repeated fetches; cleanup follows expiry |
| Selected Instagram display renditions | Private and Workspace-scoped until you delete the imported photo, delete all Balise data, or close your account; disconnecting Instagram alone does not remove them |
| Captions of imported Instagram posts (Your voice) | Workspace-scoped until you delete the imported photo, clear or turn off Your voice, delete all Balise data, or close your account; a caption whose photo never finishes importing is never used and is deleted the next time your voice is updated |
| Published shares (cards and recaps) | Until you delete the share, delete all Balise data, or delete your account |
| Stories (drafts and published) and their photo copies | Until you delete the Story, delete all Balise data, or delete your account; unpublishing keeps it as a private draft |
| Drawings you ask for | The photos sent to draw from are deleted once the drawing is made (one-day storage backstop); the drawing is kept one day, or with its Story if you keep it as that Story’s cover |
| X connection | Until you disconnect X, delete all Balise data, or delete your account; what you posted stays on X until you delete it there |
| iPhone search index entries | On your iPhone only; refreshed while the app is open, expire after seven days without a refresh, and cleared when you sign out, switch accounts, delete all Balise data or delete your account |
| Optional home-zone setting | Until you replace or forget it, delete all Balise data, or delete the account |
| Structured knowledge, import ledger, opaque person metadata | Until you delete it or delete all Balise data / your account |
| Private Workspace data of inactive accounts | Deleted after 24 months without sign-in, after the notices described below; published items and the account are kept |
| Auth / account records (Clerk) | For the life of the account; deleted when you delete your account in the app, or on request |
| Subscription and referral records | Your plan and purchase history (from Apple, with no card details), history-credit use, and referral attribution are financial records and are kept after a data or account deletion, as long as billing, accounting and legal obligations require |
| Redis / Memorystore operational state | Short-lived / cache-oriented; loss must not recreate a photo archive |
| Product interaction events | Until you delete all Balise data or close your account; workspace-scoped and not used for advertising or cross-app tracking |
| Apple Ads install attribution | Until you delete all Balise data or close your account; workspace-scoped and not used for advertising or cross-app tracking |
| Site analytics events | Pseudonymous; retained according to the configured PostHog project retention policy |
| Provider input copies (the Vertex path) | Access expires in ten minutes; the bytes follow the same one-day storage rule |
| Data exports you asked for | 30 days, then removed by the bucket |
| Inference run records (which model ran, when, what it cost) | 120 days, then swept |
| Searches that found nothing | 90 days, then swept |
| Import batches, domain suggestions, import archives | 30 days, then swept |
| Workflow history (Temporal Cloud) | 30 days after a workflow closes |
| Database backups and server logs | Backups 30 days, transaction logs 7 days, platform logs 30 days |
| Support emails | As long as needed to handle the request and ordinary business / legal records |
| Deletion audit entry | Minimal non-content record that deletion completed (counts, timestamp) |
Inactive accounts. If an account has not been signed in to for twenty-four (24) consecutive months, and has no active paid subscription and no unused purchased history credits, we will email the account address, and show a notice in the app, at least sixty (60) days and again fourteen (14) days before deleting its private data. Signing in before that date keeps everything. Otherwise we delete the account’s private Workspace data — what Balise learned from its photos, Memory, notes, reactions, and unpublished Stories and Lists — in the same way as “Delete all Balise data”. What you chose to publish (published shares, published Stories, shared Lists and your public profile) and the account itself are kept, so you can sign in later to see or remove them. Only time from 29 October 2026 counts towards the 24 months.
If an original photo is deleted from Apple Photos, related structured records may remain marked as evidence-unavailable until you delete them; Balise does not silently invent displayable originals.
10. Your rights and controls
10.1 In-product controls
- choose Photos access level (full or limited, picking photos in Apple’s sheet), how many photos and which period; “Keep up as you shoot” on or off;
- rely on the fixed exclusion of hidden and shared albums;
- correct or delete structured knowledge;
- Delete all Balise data (Your Balise → Photos & imports → “Delete all Balise data”): permanently deletes your searchable photos, notes, collections, import history, opaque person metadata, the local self reference, and any copies stored by Balise, across the phone, knowledge storage, both media buckets, the control database, push registration and operational state; running jobs are aborted first. Your Apple Photos and your sign-in account do not change;
- Delete account (Your Balise → Account → “Delete account”, confirmed by typing your account email): runs the same deletion, then removes your sign-in (§10.2);
- take down or delete what you published, in the app (Studio) or from the page itself; disconnect X or Instagram; disconnect a Connected AI service and approve or deny each photo request it makes;
- see the status of the iPhone search index in Your Balise → App → Spotlight, and turn Balise off in iPhone Search and Siri from the iPhone’s Settings (§4.11);
- manage sign-in methods and sign out (Your Balise → Account → Account & sign-in).
10.2 Access, export, correction, deletion
Depending on where you live (including GDPR if you are in the EEA/UK, and similar laws elsewhere), you may have rights to access, rectify, erase, restrict, port, and object to certain processing, and to withdraw consent where processing is consent-based.
The laws differ, so here is what you can ask for where you live. Write to apps@usebalise.com with the subject “Balise privacy” — from the email address on your account, or with enough detail for us to be sure the account is yours. We answer within one month — sooner where the law where you live sets a shorter deadline — and we do not charge for it. If a request is unusually repetitive or excessive we may say so and explain why, rather than charging you.
- EEA and the United Kingdom (GDPR). Access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and the right to complain to a supervisory authority (§10.3).
- Brazil (LGPD). Confirmation that we process your data at all; access; correction of incomplete, inaccurate or out-of-date data; anonymisation, blocking or deletion of data that is unnecessary, excessive or processed contrary to the law; portability; deletion of data processed with your consent; information about the public and private bodies we share data with; information about what happens if you refuse consent, and the right to refuse it; revocation of consent; and review of decisions made only by automated means (§14).
- Japan (APPI). Disclosure of the retained personal data we hold about you, including records of third-party provision; correction, addition or deletion where it is wrong; and suspension of use, erasure, or suspension of provision to third parties in the cases the Act allows.
- United States. Where your state's law provides them: to know, access, correct, delete, and obtain a portable copy; to opt out of sale, sharing for cross-context behavioural advertising, and targeted advertising — none of which we do (§10.4); to limit the use of sensitive personal information; and to appeal a refusal. We will not treat you differently for exercising a right.
- Latin America. Mexico's LFPDPPP gives you the ARCO rights — acceso, rectificación, cancelación, oposición — and Argentina, Chile, Colombia and others each have their own catalogue and their own deadlines. Write to us the same way; we follow the law where you live.
Export. You can request an export of workspace-held data such as profile properties, observations / facts / provenance, and domain configuration, by email. Exports do not include Apple Photos originals, which Balise never stored.
Account deletion. You can delete your account from inside the app: Your Balise → Account → “Delete account”, confirmed by typing your account email. It starts at once. Balise first deletes all your workspace data exactly as “Delete all Balise data” does (§10.1) — including published shares, Stories, Lists, your public profile, discoveries, your X connection and push registration — then the encrypted workspace credential, then your sign-in account at Clerk, and the app clears its iPhone search entries and signs you out. We keep only your subscription and referral records (§9) and a minimal non-content audit entry that the deletion completed. Deleting your account does not cancel an Apple subscription; cancel it in your Apple account settings. If you cannot use the app, email apps@usebalise.com with subject “Balise delete my account” from your account email (or include enough detail to identify the Sign in with Apple account), and we will do the same for you.
10.3 Complaints
You may contact us first so we can help. You may also lodge a complaint with the data protection authority where you live. In the EEA, that is your national authority; our European office is in France, where it is the CNIL (cnil.fr). In the UK, the ICO (ico.org.uk). In Japan, the Personal Information Protection Commission (ppc.go.jp). In Brazil, the ANPD (gov.br/anpd). In the United States, your state attorney general.
10.4 California / other US state laws
We do not sell personal information for money, and we do not share it for cross-context behavioral advertising.
11. Children and age eligibility
You must be at least 16 years old to create a Balise account (or the higher age of digital consent where you live). Where local law allows a lower age with verifiable parental consent (for example 13+), we may permit that only after implementing an appropriate parental-consent flow; until then, 16+ is the default. Balise is not directed at children under these thresholds. If you are between 16 and the age of majority where you live (18 in Brazil and Japan, among others), the law there may require a parent or guardian to agree to a paid subscription for it to hold; get their agreement before you buy. We do not knowingly create accounts for children or solicit personal data from them. If you believe a child has used Balise in a way that provided us personal data, contact apps@usebalise.com and we will take appropriate steps, including deletion.
12. People who appear in your photos (including children)
Your library may contain images of other people (including children). When the account holder includes such photos, Balise may process those images for inference and may store structured knowledge about them (descriptions, events, places, and related facts) in the workspace. Ordinary image renditions are scheduled for deletion after processing, with a one-day cleanup backstop. Exact photos approved for a connected assistant may also include other people and follow the same one-hour access rule. You remain responsible for having the right to share them.
Expected personal use. Parents photographing their own children for personal knowledge (for example watching a child grow up) is an expected personal use of Balise. The way to “see the pictures” is Apple Photos on your device — not Balise becoming a photo archive.
We do not have a direct relationship with third parties who appear in your photos and do not run a general-purpose face-identification network or retain cloud biometric templates. If People is enabled, the bounded post-import duplicate-group comparison described in §4.6 may process their faces inside temporary photo copies. You (the account holder) remain responsible for having the right to process photos that include other people. Use limited Photos access, the period and count controls, and deletion if photos should not be processed. Shared albums are always excluded, and face templates, crops and embeddings remain on your device (§4.6).
13. Security
The iPhone encrypts each processing copy before upload with a fresh AES-256-GCM key, wrapped using RSA-OAEP-SHA256. Private image copies are encrypted in storage. The master private key remains in Google Cloud KMS; decryption permission is restricted to the dedicated private media service. Staff are not granted access to open private photos. Authorized automated processing decrypts copies for preparation, AI processing and approved delivery. This is not device-only end-to-end encryption: the processing service and relevant AI providers can analyse the inputs they need, and searchable knowledge is stored separately on our servers. Production access controls enforce staff restrictions; encryption alone is not a guarantee against every possible system compromise.
AI providers receive time-limited access to decrypted inputs. Vertex processing can use a temporary private cloud input outside the phone’s per-image encryption, protected by cloud storage encryption and an expiring provider access permission. The current input access window is ten minutes. Expiry closes access independently of physical deletion; scheduled cleanup follows expiry and a one-day storage lifecycle backs up interrupted cleanup. Other image providers fetch through short-lived access links. The one to four photos you send to be drawn (§4.4) are the exception to the phone’s per-image encryption: they travel to Balise protected by TLS and are held only until the drawing is made. These controls do not promise that a provider retains no inputs or traces.
We also use private storage, encrypted connections (TLS), access checks for each account, and logged decryption attempts. Read the plain-language photo protection explanation. Report suspected vulnerabilities to apps@usebalise.com.
14. Automated decision-making
Balise uses machine learning to extract and organize information from photos. These outputs are assistive knowledge tools for your account. They are not intended to produce legal effects or similarly significantly affect you as solely automated decisions under GDPR Art. 22. You can correct or delete extracted knowledge.
Automated processing is nonetheless how Balise works, so wherever you live: you can ask a person at Balise to look at anything it decided about you, and you can correct or delete it yourself in the app. In Brazil, the LGPD gives you that review right expressly, on a lower threshold than the GDPR, and we honour it on request without asking whether the threshold is met.
15. Changes
We may update this policy by publishing a new version at this URL with a revised date. We will tell you about material changes at least thirty (30) days before they take effect, in-app or by email, and say what changed — including any new purpose we want to use your data for. For significant changes that require consent under applicable law (including any future optional image-retention feature), we will request consent / opt-in before proceeding.
16. Contact
Balise, Inc
2093 Philadelphia Pike #3795
Claymont, DE 19703
United States
1 Chome-23-5 Higashiazabu
Minato City, Tokyo 106-0044
Japan
2-4 rue Jules Lefebvre
75009 Paris
France
apps@usebalise.com (subject “Balise privacy”)
usebalise.com
Contact and requests
Delete everything we learned: in the app, Your Balise → Photos & imports → Delete all Balise data. It runs right away. Your Apple Photos and your sign-in stay as they are.
Close the account itself: in the app, Your Balise → Account → Delete account. It deletes everything above and your sign-in.
Export your data, or anything else: email apps@usebalise.com from your account email. Subjects that help us route it: “Balise delete my account”, “Balise export”, “Balise security”, “Balise privacy”. A person answers.