Skip to main content
MHBMMichael Hanna-Butros MeyeringComplex systems · human outcomes
Menu

Keystone Luma / Policy

Privacy, mapped clearly.

This policy describes the intended privacy model for an active-development prototype. Specific services and retention settings must be re-verified before any public beta release.

Prototype policyLast reviewed · August 3, 2026
01Overview and sensor dataOn-device first

What the prototype accesses

Keystone Luma is an independently developed iOS and iPadOS projection-mapping prototype. Depending on the workflow and device, it may request camera access for ARKit tracking, LiDAR access for depth sensing, optional microphone access for audio-reactive effects, and optional photo-library access for import and export.

LiDAR depth maps, live camera feeds, ARKit tracking data, and audio-frequency analysis are intended to stay on the device. Temporary ARKit and rendering buffers are released after processing. The prototype is not designed to make persistent recordings of an environment.

If a user explicitly chooses AI scene analysis, one still image selected or captured by that user may be sent to the configured AI service. Live camera feeds, point clouds, spatial maps, projector output, and project files are not part of that request.

02AI services and promptsExplicit action

Data used for AI experiments

The product concept explores Google Gemini for optional scene analysis, Imagen for texture generation, and Veo for short video generation. A request may include a text prompt, an optional still scene image, an optional seed image, generated output, and routine API metadata such as timestamp and service version.

  • Do not place personal, confidential, regulated, or sensitive information in prompts or source images.
  • Cloud providers may retain request material for security, abuse prevention, service operation, or legal compliance under their own terms.
  • The prototype does not intend to send live video, LiDAR point clouds, ARKit maps, saved surface geometry, or external-display feeds.
  • Provider selection, model versions, retention settings, and opt-out controls must be confirmed before beta access.
03Analytics and error reportingOptional

Diagnostics by consent

The project specification contemplates opt-in PostHog analytics and opt-in Sentry error reporting. If enabled in a future build, analytics may include feature usage, performance, session duration, device model, operating-system version, and app version. Error reports may include stack traces, error messages, and diagnostic breadcrumbs.

These services must not receive prompts, project contents, LiDAR or camera data, precise location, advertising identifiers, generated media, or user-created surface maps. A released build must expose an in-app control to disable optional diagnostics.

04Billing and account dataNot yet active

Planned App Store handling

Keystone Luma is currently presented as a prototype; no public subscription is offered on this website. If App Store subscriptions are introduced, Apple would process payment and manage the subscription relationship. The app would receive only the information needed to verify entitlement, such as plan, status, renewal timing, and a privacy-preserving account token.

The developer would not receive a user's payment card, billing address, or Apple account password. Final billing disclosures and cancellation instructions must be confirmed against the released App Store configuration.

05Rights, retention, and deletionUser control

Privacy requests

Users may request access, correction, deletion, portability, restriction, or information about processing where applicable under GDPR, CCPA, or other law. Keystone Luma does not sell personal information or share it for third-party advertising.

Data typeIntended handling
LiDAR, camera, ARKit, audio analysisTransient, on-device processing
Local projects and settingsUntil the user deletes them or uninstalls the app
AI prompts and selected inputsControlled by the active provider terms and configured retention
Optional analyticsProject target: no more than 12 months
Optional error reportsProject target: 90 days

Because the product remains in development, these periods are targets rather than a representation that every service is active. Release-time settings will control.

06Security, children, and international useAdditional notes

Safeguards and scope

The intended safeguards include on-device processing for spatial data, transport encryption for cloud requests, restricted service credentials, minimal logs, and user-controlled permissions. No system can guarantee absolute security, particularly during prototype testing.

Keystone Luma is not intended for children under 13. International users should understand that optional cloud requests may be processed in jurisdictions different from their own. Material policy changes will be reflected on this page before a broader release.

Privacy contact

Ask about your data.

Contact the project