Poseline Privacy Policy
This Privacy Policy describes how Miller Carter AŞ. (“Miller Carter,” “we,” “us,” or “our”) collects, uses, and discloses information in connection with the Poseline mobile application (the “App”). By using the App, you agree to the practices described in this policy. If you do not agree, do not use the App.
Face and depth sensing are performed on your device. The “Get Your Pose Line” feature analyzes your face using your device’s on-device camera and depth technology, and our live pose line guidance reads on-device depth to gauge distances in the scene, such as how far you are from a wall or the position of the floor. The camera feed, your facial geometry, and all depth data’s smaller copies are processed with OpenAI ChatGPT and Fal AI Flux Schnell and in real time. They are not uploaded to our servers, stored by us, used to identify you, or shared with third parties.
Table of Contents
1. About Us
The App is published by Miller Carter AŞ. This policy applies to information processed through the App and our related services. It does not apply to third-party services that have their own privacy policies, which are referenced below.
2. Information We Collect
2.1 Information You Provide
- Account details: When you create an account, you sign in with Sign in with Apple, Google, META or an email address and password. We collect your email address and, only if you choose to share it through Sign in with Apple, your name. Authentication is handled by Google Firebase Authentication.
- Face & Photo Data: If you expressly allow user agreement and use Poseline, we receive smaller copies of the photos you select, limited technical ranking metadata, and a pseudonymous authenticated request identifier. Photos may show faces, expressions, and other visible details. We use these details only to assess the photographic moment and do not use them to identify a person or create a biometric profile.
- Feedback: If you respond to an in-app feedback prompt, we collect your rating and any message you choose to provide.
2.2 Information Collected Automatically
- Usage Analytics: Through Google Firebase Analytics we record in-app events, such as completing onboarding, finishing a scan, viewing or favoriting a pose, using an overlay, taking a capture, viewing the subscription screen, and completing a purchase. RevenueCat also sends subscription lifecycle events, such as trial starts, renewals, cancellations, billing issues, and expirations, to Google Analytics on our behalf.
- Device and Diagnostic Data: When you submit feedback, we attach basic technical context such as app version and build, device model, operating system version, and your device locale to help us reproduce and resolve issues.
- Subscription and Purchase Information. RevenueCat processes your pseudonymous App User ID, Firebase app-instance identifier, product and offering identifiers, purchase and transaction information, price and currency, subscription status, and related lifecycle events so we can provide premium access, test subscription offers, measure paywall performance, and understand subscription changes.
2.3 Information We Do Not Collect
We do not collect your location, contacts, health data, or advertising identifiers (IDFA). We do not use third-party advertising networks and do not track you across other companies’ apps or websites.
3. Information That Stays on Your Device
A substantial part of the App runs entirely on your device. The following are stored locally and are not transmitted to us:
- Face-scan Processing: The live camera feed and the facial geometry used by “Analyzing” are analyzed on your device using Apple’s Vision and TrueDepth technologies. We do not receive the camera feed or any face or depth data.
- Depth-Based Line Guidance: The App’s live coaching features use on-device depth from your device’s camera to measure distances in the scene, such as how far you are from a wall behind you or where the floor sits in the frame, so the App can suggest framing and place a posing guide. This depth reflects the surrounding scene rather than identifying you, is processed live in device memory, and is not recorded, stored, or transmitted.
- Captured photos: Photos and thumbnails you capture in the App are stored within the App on your device. They are not uploaded to AI.
- Capture history, pose favorites, and preferences Are stored locally on your device.
Your angle profile (the scores and recommendations) is the only scan-related information that syncs to your account, and it does not include images.
4. Camera and Photos
The App requests access to your camera and photo library solely to provide its features:
- Camera Access: Camera to provide live posing and framing guidance. The camera feed is processed in real time on your device and is not recorded or transmitted by us.
- Photo library Access: Photo library(read) so you can review and improve existing shots, if you choose to use an existing photo. Saving to your library (add-only) means the App requests add-only access in order to save a captured photo to your library only when you choose to save it. This permission does not allow the App to read or browse your existing photos.
5. How We Use Information
We use the limited information we collect to:
- Create and secure your account and authenticate sign-in,
- Sync your angle profile across your devices,
- Provide, maintain, and improve the App and its features
- Understand which features are used so we can prioritize improvements,
- Respond to your feedback and provide support,
- Manage your subscription and entitlements,
- Detect, prevent, and address technical issues, fraud, or abuse, and comply with legal obligations.
Where the EU or UK General Data Protection Regulation applies, our legal bases for processing are performance of a contract (providing the App and your account), your consent (camera, photos, and optional feedback), and our legitimate interests (securing and improving the App).
6. Analytics and Tracking
We use Google Firebase Analytics to understand how the App is used. Firebase Analytics collects and processes app events and identifiers, including a pseudonymous app-instance identifier. We associate that identifier with subscription and purchase events processed by RevenueCat so that RevenueCat can send server-side subscription lifecycle events to Google Analytics even when the App is not open. This allows us to measure subscription performance, including offer and paywall experiments, renewals, cancellations, billing issues, and expirations.
This is first-party analytics: the data is used by us to operate and improve the App. We use it for advertising, we do combine it with third-party data to target advertising. We do not share it with data brokers. Accordingly, the App engages in “tracking” as defined by Apple’s App Tracking Transparency framework, and requests tracking permission. You can learn more about how Google collects and processes data from apps that use its services at Google’s Business Data Responsibility page.
| Providers | Purposes | Data Involved |
|---|---|---|
| Google Firebase (Authentication, Firestore, Analytics, Crashlytics, Cloud Messaging) | Account authentication, account and content database, product analytics, crash and stability reporting, push notifications | Email address, profile information, user-submitted content and feedback, Firebase app-instance identifier, usage and screen-view events, crash logs and diagnostic data, device and OS attributes, IP address, push token |
| Google AdMob | Serving in-app advertising and measuring ad performance | Advertising identifier (IDFA / GAID, where consent is given), IP address, coarse location derived from IP, device and OS attributes, ad impression and interaction events |
| Apple | Sign in with Apple, App Store purchases and subscriptions, app ratings, and responding to subscription or app-usage inquiries | Authentication token, purchase records, and limited subscription, app-version, diagnostic, or usage details when reasonably necessary to address an inquiry |
| Google Sign-In | Optional sign-in | OAuth authentication token, and the email address and basic profile fields you authorize |
| RevenueCat | Subscriptions, entitlements, subscription-offer experiments, and subscription lifecycle analytics | Pseudonymous App User ID, Firebase app-instance identifier, product and offering identifiers, purchase and transaction information, price and currency, subscription status and lifecycle events |
| AppsFlyer | Install and campaign attribution, marketing measurement, deep linking, remarketing audience creation, and ad-fraud prevention | AppsFlyer ID, device and advertising identifiers (IDFA / IDFV / GAID, where consent is given), IP address, coarse location derived from IP, device and OS attributes, app version, install, session and in-app events (including purchase events), referrer and attribution data, SKAdNetwork / AdAttributionKit postbacks |
| Mixpanel | Product analytics — funnel, retention, cohort and feature-usage analysis, and A/B test measurement | Pseudonymous distinct ID, in-app events and screen views, session and engagement data, subscription state, device and OS attributes, app version, language and IP-derived country or region, IP address |
| Meta (Facebook Audience Network, Meta SDK & Analytics) | Advertising delivery and monetization, user-acquisition campaigns, conversion measurement and attribution, and audience building for remarketing | Advertising identifier (IDFA / GAID, where consent is given), Meta app-instance identifier, IP address, device and OS attributes, app events such as installs, registrations, trial starts, subscriptions and purchases, ad impression and interaction data |
| Google Ads | User-acquisition campaigns, conversion tracking, attribution, and remarketing | Advertising identifier (IDFA / GAID, where consent is given), Firebase app-instance identifier, conversion and in-app events, purchase value and currency, IP address, device and OS attributes, SKAdNetwork / AdAttributionKit postbacks |
| TikTok Ads | User-acquisition campaigns, conversion tracking, attribution, and remarketing | Advertising identifier (IDFA / GAID, where consent is given), TikTok app event identifiers, install and in-app conversion events, purchase value and currency, IP address, device and OS attributes, SKAdNetwork / AdAttributionKit postbacks |
| OpenAI | Powering AI-assisted in-app features — generating pose suggestions, guidance text, and related outputs from your inputs | The prompt or input you submit (including any photo or image content you choose to process), the feature context needed to generate a response, and basic request metadata. No account identifiers are sent unless required for the feature. Data sent through the OpenAI API is not used by default to train OpenAI’s models, and inputs and outputs may be retained for up to 30 days for abuse monitoring before deletion, unless longer retention is legally required |
| fal.ai | Running generative image and media models that power AI-assisted in-app features — processing your submitted photo or prompt and returning a generated result | The image you submit and any accompanying text prompt, model and parameter settings, generated output media, and basic request metadata. No account identifiers are sent unless required for the feature. Inputs and outputs are processed on servers located in the United States |
7.1 Apple Subscription and App-usage Inquiries
If Apple contacts us about a subscription, purchase, refund, suspected fraud, App Review matter, or technical or App-usage inquiry, or if you ask us to work with Apple on such an inquiry, we may provide Apple with only the limited information reasonably necessary to investigate and respond. This may include subscription status, product and transaction identifiers, App version, and relevant diagnostic or usage events.
We do not provide Apple with your photos, camera feed, face or depth data, angle profile, email address, or unrelated App activity for this purpose, unless you specifically ask us to, consent to it, or disclosure is required by law. We do not share this information with Apple for advertising.
We may also disclose information where required by law, to enforce our Terms of Use, or to protect the rights, safety, and property of our users or the public.
8. Retention and Account Deletion
We retain your account information for as long as your account is active. Information stored locally remains on your device until you delete it or remove the App. Poseline erases its photo uploaded-image buffers when the analysis request finishes; a photo-free ranking result may be cached for up to 15 minutes for request completion and duplicate-charge protection. Fal AI may temporarily retain photo inputs and its linked Flux Schnell data-governance documentation.
You may delete your account at any time from within the App, which removes your account and associated profile data from our systems. You may also request deletion by emailing hello@millercartersoftware.com. We will action verified requests within a reasonable time, subject to any legal obligation to retain certain records.
9. Your Privacy Rights
Depending on where you reside, you may have the right to access, correct, export, restrict, or delete your personal information, and to object to or withdraw consent for certain processing.
9.1 EEA and UK (GDPR)
You have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to lodge a complaint with your local data protection authority.
9.2 California (CCPA/CPRA)
You have the right to know what personal information we collect, to request its deletion, and to correct it. We do not sell or share your personal information as those terms are defined under California law, and we do not offer financial incentives in exchange for it.
To exercise any of these rights, contact us at hello@millercartersoftware.com. We will not discriminate against you for exercising your rights.
10. Children’s Privacy
The App is not directed to children under 13 (or the minimum age of digital consent in your country, where higher), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us and we will delete it.
11. Security
We use industry-standard safeguards, including the security infrastructure provided by Google Firebase, to protect information in transit and at rest, and we restrict account data so that it is accessible only to you. Information stored on your device is protected by iOS application sandboxing. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
12. International Data Transfers
The account, analytics, and photos data we collect is processed on Google’s cloud infrastructure, which may be located in the United States and other countries. By using the App, you understand that your information may be transferred to and processed in countries whose data protection laws may differ from those of your country. Where required, we rely on appropriate safeguards for such transfers.
13. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above and, for material changes, provide a more prominent notice. Your continued use of the App after an update constitutes acceptance of the revised policy.
14. Contact us
If you have questions or requests regarding this policy or your information, contact us at:
Miller Carter AŞ.
hello@millercartersoftware.com