SplatKing Privacy Policy

3.1 Capture Content and Session Outputs

When you use SplatKing, the app can generate and store files in the app container, including:

• photos and videos;
• optional undistorted video outputs;
• metadata sidecars (for example JSON manifests and per-capture records);
• optional LiDAR sidecars such as depth maps and point cloud binary files;
• optional person-mask sidecars if generated by device-side segmentation;
• quality summaries and quality flag files.

3.2 Metadata and Sensor-Derived Data

SplatKing may process metadata associated with captures, such as:

• timestamps and filenames;
• camera configuration and lens mode;
• motion-derived or AR-derived pose and orientation information;
• capture-quality scoring indicators;
• EXIF/TIFF/GPS fields available from system frameworks.

Location metadata is written to captures only if you enable the optional Save Location feature; see §3.7.

3.3 Device and App Diagnostics

To maintain reliability, SplatKing writes local diagnostics that may include:

• lifecycle events and non-fatal error logs;
• crash markers and stack traces for uncaught exceptions;
• app version/build;
• device model and operating system version;
• storage availability snapshots and capture pipeline counters.

3.4 Support Communications

If you contact us or use in-app feedback or debug-report features, we may process:

• your message contents and any freeform notes you include;
• attachments you provide;
• diagnostic data you choose to include, such as app and device information (app version and build, device model, iOS version), storage availability snapshots, and recent application log lines (lifecycle events, non-fatal errors, crash markers — capped in size and rotated locally);
• capture content you choose to attach, which may include photos, videos, optional undistorted outputs, LiDAR depth maps and point cloud sidecars, person-mask sidecars, metadata sidecars, and quality summaries (the categories described in §3.1), and, if you have enabled the optional Save Location feature (§3.7), location metadata embedded in those capture files;
• related correspondence records.

Debug or feedback bundles are assembled on your device and remain there until you explicitly send them through an iOS share action. You choose the destination (for example email to SplatKing support, messaging apps, AirDrop, or saving to Files / iCloud Drive); destinations other than SplatKing support are governed by those services' own terms, as described in §16.

3.5 Feedback and Reviews via App Store Channels

Users may submit ratings/reviews/feedback via App Store & TestFlight; these are collected by Apple and made available to us as developer. Where we review this to triage bugs, we remove direct identifiers (nicknames, emails, handles) before use and retain only de-identified, summarized records. Apple's handling is per Apple's policy.

3.6 Product Analytics (Optional; On or Off by Default Depending on Your Region)

To understand how SplatKing's features are used and to monitor and improve capture reliability, SplatKing includes an optional product-analytics feature. You can turn this feature on or off at any time in the app's Settings. Whether it is on or off when you first use the app depends on the privacy laws that apply where you are:

• If you are in the European Economic Area, the United Kingdom, or another region whose laws require your prior consent to store information (such as an analytics identifier) on your device, product analytics is OFF by default. No analytics data is collected, and no analytics identifier is created or stored, unless you turn analytics on.
• Everywhere else (for example, the United States), product analytics is ON by default, and you may turn it off at any time. When you first use a version of the app that includes this feature, we show you an in-app notice that analytics is on and how to turn it off.

How we determine your region. Because we have disabled IP-based location lookup for analytics (see §9.5), we do not use your IP address to determine your region. Instead, we use signals available on your device — your device's region setting and your App Store country — solely to decide whether analytics should be off by default (opt-in) or on by default (opt-out). If we cannot reliably determine your region, or if either signal indicates you are in a region that requires prior consent, we treat you as opt-in and leave analytics OFF until you choose to turn it on.

When — and only when — analytics is on (because you turned it on, or because it is on by default in your region and you have not turned it off), SplatKing sends a limited set of usage and diagnostic events to our analytics processor (see §9.5). These events fall into the following categories:

• Device identifier (anonymous): a randomly generated, app-specific identifier (an "analytics ID") stored on your device. It is not your name, email address, Apple ID, phone number, or advertising identifier, and it is not used to track you across other apps or websites. It lets us count distinct devices and reassemble a single device's sequence of events.
• Product interaction: how you use the app — for example, which capture mode you select, when a capture starts and completes, manual-control and settings adjustments, and export/share actions. We record event names and range-based ("bucketed") values, never the content of your captures.
• Performance data: operational performance signals — for example, capture durations, export/packaging throughput, and device thermal state — recorded as ranges, to help us find and fix slow or failing paths.
• Other diagnostic data: capture-reliability diagnostics — for example, whether a capture's expected output files are present, whether dual-lens streams are balanced, and aggregate per-capture quality-band counts — used to monitor and improve capture integrity. A per-capture pseudonymous reference (a "capture ID," derived by a one-way hash of a local timestamp-based folder name) links a single capture's events; it identifies one capture, not you.

Each event also carries basic context such as the app version and build, iOS version, device model identifier, whether the device has LiDAR, and device locale.

What product analytics does NOT collect. Product analytics never collects:

• the content of your captures (photos, videos, undistorted outputs, LiDAR depth maps or point clouds, person-mask sidecars, or any image or sensor pixel data);
• filenames or file paths of your captures;
• precise or approximate geolocation (no GPS);
• your name, email address, Apple ID, phone number, or other directly identifying information (before any future account feature, analytics is not linked to an account);
• an advertising identifier (IDFA); we do not use the data for advertising, cross-app or cross-site tracking, or any data broker;
• raw camera settings that could fingerprint a scene — values such as ISO, exposure, and white balance are converted to ranges on your device, and only the range leaves your device;
• your IP address — IP-based location lookup is disabled and the IP address is removed before events are sent.

How analytics are kept anonymous to us. We design product analytics so that events are not linked to your name, email address, Apple ID, or any account, and we do not attempt to re-identify you. A persistent app-specific identifier and pseudonymous per-capture references are used to make the data useful; under some laws (such as the EU/UK GDPR) such identifiers may still be treated as personal data, and we handle them accordingly.

Legal basis (where the GDPR / UK GDPR applies). Where your region requires your prior consent (for example, the EEA and the UK), we process product-analytics data, and store the analytics identifier on your device, on the basis of your consent (Article 6(1)(a)), which you give by turning the feature on. You may withdraw consent at any time; withdrawal does not affect the lawfulness of processing carried out before withdrawal. Where the GDPR applies but your region does not require prior consent for on-device storage, we rely on our legitimate interests (Article 6(1)(f)) in understanding feature usage and improving capture reliability, and you may object at any time by turning the feature off. For users in the United States, see §14.

Turning analytics on or off. You can turn product analytics on or off at any time in the app's Settings. Where analytics is off by default in your region, turning it on is your opt-in (and you may withdraw at any time); where analytics is on by default in your region, turning it off opts you out of all future collection. When you turn it off, SplatKing stops collecting analytics events, signals our analytics processor to opt your device out, and resets and clears the on-device analytics identifier; the analytics components stop sending or queuing events. Turning analytics off stops future collection but does not by itself delete events already collected. To request deletion of previously collected analytics data, contact us at the address in §1; because the data is not linked to your identity, we may need the analytics ID from your device to locate it.

Where the data goes. Analytics events are sent to and stored by our analytics processor, PostHog, on infrastructure located in the United States. See §9.5 (analytics provider) and §11 (international transfers).

3.7 Capture Location (Optional; Off by Default)

SplatKing includes an optional "Save Location" feature, which is off by default. If you turn it on in the app's Settings and grant the iOS location permission (while-using-the-app only), SplatKing records where your captures were taken. When the feature is on, a location fix — latitude, longitude, horizontal accuracy, altitude where available, and a timestamp — is written into your capture files on your device: into the capture's metadata manifests, into photo EXIF fields, and into video file metadata. For video and LiDAR captures, a bounded series of location samples (a movement track covering the duration of the capture) may also be recorded in the capture's metadata manifest.

All of this location data is stored only on your device, inside your own capture files. It is never transmitted to us or to our service providers, and it is never included in product analytics (§3.6) — analytics records only whether the feature is on and whether a capture had location attached, never coordinates. If you share or export capture files, any location data inside them travels with the files to the destinations you choose (see §9.1 and §16), and if you attach capture files to a support submission, the location data inside them is included (§3.4). Captures made while the feature was on keep their location data after you turn the feature off; you can delete those files at any time. You can withdraw the location permission at any time in iOS Settings; captures always work without location.

9.1 At Your Direction

We disclose data when you choose to share files through iOS share workflows. Because these transfers are initiated by you to destinations you select, the data shared in this way is not collected by us, and we do not receive it unless the destination you choose is SplatKing support.

9.2 Service Providers

If you engage support, we may use vendors that help process support tickets, communications, or operational infrastructure. Automated tools/providers used to summarize/categorize de-identified feedback receive only de-identified, summarized info — never verbatim submissions or direct identifiers.

9.3 Legal and Safety Disclosures

We may disclose information where reasonably necessary to:

• comply with law, legal process, or regulator requests;
• protect rights, safety, and security;
• investigate fraud, abuse, or violations of law/terms;
• complete corporate transactions (for example merger, financing, or asset sale), subject to applicable law.

9.4 No Sale of Personal Information

We do not sell personal information for monetary consideration. We do not use cross-context behavioral advertising identifiers in the app.

9.5 Product Analytics Provider

When product analytics is enabled (on by default or you turned it on; see §3.6), we use PostHog as a processor to collect and store analytics events on our behalf. PostHog processes this data under our instructions and a Data Processing Agreement and does not use it for its own purposes. Analytics events are stored on PostHog Cloud infrastructure in the United States. We have disabled IP-based geolocation in our analytics configuration, and IP addresses are removed before events are stored. PostHog may use sub-processors to provide the service; these are governed by our agreement with PostHog.