Privacy Policy

Last Updated: October 9, 2026

Thank you for using Inki (hereinafter referred to as the "App"). This Privacy Policy explains how we collect, use, share, and protect information in connection with your use of the App. By accessing or using the App, you acknowledge that you have read, understood, and agreed to the contents of this Privacy Policy.

1. Account Creation (Optional)

Inki does not require you to create an account to use any feature of the App. By default, the App generates a random, anonymous device identifier that is stored locally on your device the first time you use the App, used solely to associate your own submissions and likes with your device and not linked to your real-world identity.

If you choose to, you may optionally sign in with Google, Apple (iOS only), or a phone number to save your profile and submissions across devices. If you do, we collect the email address or phone number associated with that sign-in method, along with an internal account identifier ("User ID"), and link your device's activity to that account instead of only to the anonymous device identifier. You can continue to use the App as a guest at any time without signing in.

2. Information We Collect

When you use the App, we may collect the following types of information:

• Anonymous Device Identifier: A randomly generated identifier stored on your device, used to attribute the designs you submit and the designs you like to your device, and to show you "My Submissions" within the App.
• Account Information (only if you choose to sign in): If you sign in with Google, Apple, or a phone number, we collect the email address (Google/Apple) or phone number associated with that sign-in method, plus an internal account identifier ("User ID"), so your profile and submissions can be restored across devices. We do not share your email address or phone number with third parties for advertising. Your internal User ID is provided to our marketing attribution provider as described under “Advertising Identifier and Marketing Attribution” below.
• Chat Messages (if you use the Designer Chat feature): If you choose to message the designer behind an official design, we collect the text content of the messages you send and receive, along with the identity of the sender and recipient. You may also send voice messages or photos; if you do, we collect the recorded audio content or the image you choose to send, along with the identity of the sender and recipient, and the App requests your permission to access the microphone or photo library at that time. Messages (text, voice, and photos) are retained to enable the conversation and for content moderation and safety review (see Section 4).
• Video Calls (if you use the Designer Video Call feature): From an existing chat conversation, you may start a real-time video call with the designer behind that official design. During a call, the App accesses your device's camera and microphone, only with your explicit permission, to transmit your live video and audio to the other participant. Video and audio are relayed in real time through a third-party real-time communication provider and are not recorded or stored by us. We do retain a record that a call took place (the participants, duration, and timestamp) to enable the feature and for content moderation and safety review (see Section 4). Video calls are paid with Diamonds (see "Purchases" below) and are charged per minute of call time; the call duration record is also used to calculate the Diamonds charged.
• Purchases (if you buy Diamonds): You may buy Diamonds, a virtual item used for video calls and for unlocking premium designs, through Apple In-App Purchase (iOS) or Google Play Billing (Android). Payment is processed entirely by Apple or Google; we never receive or store your credit card or other payment card details. We do collect and retain your purchase history — order number, product purchased, amount, time of purchase, and the platform's transaction identifier — together with a record of how your Diamonds were added and spent, linked to your User ID. We use this information to deliver the Diamonds you bought, verify transactions with Apple or Google, prevent fraud, and handle support and refund requests.
• Usage Analytics: We record events about how the App is used (for example, which screens are opened and which features are used) through the Sensors Data analytics SDK, and through Google Firebase Analytics. These events are associated with your device identifier and, if you are signed in, with your User ID. We use them to understand and improve the App; they are not sold. Separately from these product-analytics events, a small set of marketing attribution events is sent to AppsFlyer — see “Advertising Identifier and Marketing Attribution” below.
• Advertising Identifier and Marketing Attribution: To understand which marketing campaign or referral led to an installation of the App, we use AppsFlyer, a mobile attribution service. AppsFlyer receives your device's advertising identifier (the Google Advertising ID on Android, or the Identifier for Advertisers on iOS), basic device and installation information, and the campaign parameters associated with your installation. If you sign in, we also provide AppsFlyer with your internal User ID so that installations and events can be attributed to the same user across devices; we do not provide AppsFlyer with your email address or phone number. We send AppsFlyer a small set of events — application installed, registration completed (including which sign-in method was used), sign-in, and purchase completed (including the purchase amount and whether it was a first purchase) — so that marketing performance can be measured. This is the only purpose for which we use the advertising identifier; we do not use it to show you advertisements inside the App, and the App does not display third-party advertising. On iOS, the App asks for your permission through Apple's App Tracking Transparency prompt before the advertising identifier is used for this purpose; if you decline, the identifier is not available to the App. See Section 8 for how to limit this at the operating-system level.
• Photos and Camera Content: When you choose to submit a design to the shared design library, or use the camera-based "Try-On" preview feature, the App accesses your device's camera and/or photo library, only with your explicit permission. Photos you submit to the design library are stored on our servers and are publicly visible to all users of the App. Try-On results you capture are saved to your own device's photo library and are not uploaded to our servers unless you separately choose to submit them.
• Device and Technical Information: This includes device model, operating system version, IP address, and similar technical data, used to keep the App running reliably and to diagnose issues. When the App crashes or encounters an error, crash reports and performance diagnostics (such as the error stack trace, device model, and OS version) are collected through Firebase Crashlytics and Firebase Performance Monitoring, services provided by Google, and through the analytics providers named above. We do not collect precise location information.

3. Face Data and the Try-On Feature

The App's "Try-On" feature lets you take or select a photo and manually drag, scale, and rotate a tattoo design or sticker on top of it. The App does not perform facial recognition, biometric analysis, or extract any facial geometry, facial landmarks, or biometric identifiers from your photos. No automated face detection or face-matching technology is used by the App or its backend at any point.

A photo you use for Try-On (which may or may not contain a face) is processed entirely on your device to render the overlay. It is never transmitted to our servers unless you explicitly tap "Save"/"Submit" to keep or share the result. If you do submit a Try-On result, only the resulting composited image file is uploaded and stored on our servers (using the same infrastructure described in Section 6, Sharing and Disclosure of Information); we do not separately extract, analyze, or store any facial data points from it. If you additionally choose to make the result public, it becomes visible in the shared design library as described in Section 5.

We do not share Try-On photos or any face-containing images with third parties for advertising, analytics, or any purpose other than the infrastructure providers necessary to host and serve the App (Section 6). Submitted Try-On images are retained until you request deletion (see our Data Deletion page) or until we remove them for content-policy reasons; Try-On photos that are never submitted stay only on your device and are never retained by us.

4. Use of Information

We use the information above for the following purposes:

• Operating the Service: To let you browse the design library, filter by category, submit your own designs, like designs, and use the Try-On camera preview.
• Attributing Your Content: To show which designs and likes belong to your device under the "My" tab, without requiring a login.
• Processing Purchases: To deliver the Diamonds you buy, charge Diamonds for video calls and premium designs, keep an accurate transaction record, and handle refund and support requests.
• Analytics and Improvement: To understand how features are used, and to find and fix crashes and performance problems.
• Content Moderation and Safety: To review reported content and remove submissions or messages that violate our content standards.
• Security and System Maintenance: To detect abuse and keep the App and backend infrastructure stable and secure.

5. Publicly Visible Content

Any design image, caption, or category you submit through the App becomes part of the shared design library and can be viewed by any other user of the App. Please do not submit photos that reveal information you do not want to make public. Try-On results saved only to your own device's photo library are private and are never made public unless you separately submit them.

6. Sharing and Disclosure of Information

We do not sell your information. We may share information in the following limited circumstances:

• Service Providers: We use third-party providers to operate the App, including cloud hosting and storage providers; Apple and Google (to process in-app purchases); Google Firebase (for crash reporting, performance monitoring, analytics, and push notifications); RongCloud (to deliver chat messages); Agora (to relay real-time video and audio calls); Sensors Data (for product analytics); and AppsFlyer (for marketing attribution, as described in Section 2). These providers only access data to the extent necessary to provide their services.
• Legal Requirements: We may disclose information if required by applicable law, court order, or government request, or to protect the rights, safety, or property of our users or the public.

7. Data Storage and Security

We use reasonable technical and organizational measures to protect data from unauthorized access, disclosure, alteration, or destruction. However, no method of transmission or storage over the Internet is completely secure, and we cannot guarantee absolute security.

8. Your Choices

If you use the App as a guest, you can find your anonymous device identifier under the "My" tab in the App (tap to copy it), and use it when contacting us to request removal of specific submissions or data associated with your device. If you signed in with Google, Apple, or a phone number, you can sign out at any time from the "My" tab, and contact us using the email address or phone number tied to your account to request removal of your account and its associated data — see our Data Deletion page for details.

You can limit the use of your device's advertising identifier at the operating-system level. On Android, open Settings → Privacy → Ads, where you can delete or reset the advertising ID. On iOS, you may decline the App Tracking Transparency prompt, or turn off “Allow Apps to Request to Track” under Settings → Privacy & Security → Tracking.

Uninstalling the App will remove the locally stored device identifier from that device (and sign you out of any linked account on that device); a new anonymous identifier will be generated if you reinstall.

9. Children's Privacy

The App is not directed at children, and we do not knowingly collect information from children. If we become aware that content submitted through the App was provided by a child in violation of this policy, we will remove it as soon as reasonably practicable.

10. Privacy Policy Updates

We may update this Privacy Policy from time to time. When we do, we will post the revised version on this page and update the "Last Updated" date above.

11. Contact Us

If you have any questions about this Privacy Policy, please contact us at Email: sherkhanvideos9@icloud.com