Privacy Policy
Last updated: September 24, 2026
How this policy applies
This policy describes how apps published by Yash Rajesh Gandhe collect, use, share, retain, and protect information. The general sections apply to all covered apps. An app-specific disclosure supplements those general sections only for the named app and does not describe the behavior of the other apps.
App-specific disclosures
Choose an app
CHRM — AI Photo Studio
CHRM is a private portrait editor operated by Yash Rajesh Gandhe for adults aged 18 and over. This section applies to CHRM only. Its account and photos use cloud storage; the on-device practices of another app do not apply to CHRM.
Account and security information
When you sign in with Apple or Google, CHRM receives your name, email address (including an Apple relay address if chosen), provider account identifier and any profile information the provider supplies. Its backend stores authentication sessions, IP address and user agent for security, along with daily upload and monthly or daily edit counters. Your session is stored in the iOS Keychain. Editing preferences are saved on your device.
Subscriptions and purchases
Apple processes App Store payments. RevenueCat receives your CHRM account identifier, purchase history, subscription status, and app and device information to verify purchases, manage subscription access, and provide subscription history and aggregate revenue reporting. CHRM stores payment receipts for accepted edits and uses RevenueCat to verify subscriptions and grant, debit and expire edit credits. Retrying the same accepted edit does not spend a second credit. CHRM does not receive your payment card details. See RevenueCat’s Privacy Policy.
Photo sharing and your permission
Before uploading for an edit, CHRM asks you to confirm that you are 18 or older, the photo is of you, and you agree to send the original, selected references and editing instructions through Cloudflare and to OpenAI. Cloudflare hosts the backend, database, private image storage and job queue. OpenAI processes the images and instructions to generate an edit. CHRM cannot perform the edit without this processing.
Saving references requires separate consent. You may save up to five photos and choose whether to use them for each edit. CHRM uses them as image inputs; it does not train a personal model or build a face-recognition database. The app prepares selected photos locally and removes image metadata before uploading. Only images you select are accessed, and add-only Photos permission is requested when you save an edit.
Storage, retention and deletion
- Originals and edits: CHRM stores private copies that stop being available after seven days. Scheduled cleanup removes them. You can remove an original and all its edits sooner from Your edits.
- Saved references: These remain until you remove them or delete your account. Removing a reference cancels unfinished edits using it, but cannot recall a request already sent to a provider.
- Account: Settings → Delete account removes your CHRM account, sessions and usage records. Private photo erasure and provider deletion continue automatically, with retries during outages. A fresh sign-in may be required. CHRM revokes stored Apple authorization when available; older accounts without a stored token receive instructions for manually disconnecting Apple access. A minimal deletion record and encrypted Apple revocation credential remain only until erasure and revocation finish, preventing in-flight work from recreating data. CHRM also requests deletion of its RevenueCat customer record. Apple and service providers may retain transaction records for legal, accounting or security purposes. Account deletion does not cancel an Apple subscription; cancel it separately in Apple’s subscription settings.
- Device and shared copies: Deleting CHRM data does not delete photos you saved to your device or shared elsewhere.
CHRM requests that gateway prompt/output logging be disabled and bypasses the gateway cache for generation. Provider processing, security records, temporary output storage and infrastructure backups may have separate retention requirements. CHRM deletion does not promise immediate removal from every provider system. See Cloudflare’s data-use information, Cloudflare’s Privacy Policy and OpenAI’s Privacy Policy.
Your choices and privacy requests
You can decline photo processing, turn off references for an edit, remove saved images or delete your account. CHRM has no public photo feed, advertising integration or cross-app tracking SDK. The website’s traffic analytics are separate from CHRM’s app processing. Service providers may process information outside your country.
For access, correction or deletion requests, email support@yashgandhe.com and name CHRM. Include the account email and approximate request date only when relevant; never send passwords or sign-in codes. Requests for provider-side records depend on provider capabilities and applicable legal or security retention requirements.
Linify (Pregnancy Test Checker)
This section applies only to Linify and its pregnancy-test photo analysis, saved timeline, and Pro purchase features.
AI photo analysis and consent
Linify does not send a pregnancy-test photo for AI analysis until you see its disclosure and tap Allow Photo Sharing & Continue. You can choose Not Now, but Linify cannot generate an AI analysis without sending the selected photo to its AI providers.
You can stop future AI photo sharing at any time in Linify under Settings → AI & Privacy → Withdraw AI Photo Sharing. Withdrawing consent prevents future photos from being sent. It does not retroactively remove information that the providers previously processed or retained under their policies.
What is shared and why
When you request an analysis, Linify sends the pregnancy-test photo you selected, together with instructions needed to analyze it, through AIProxy to OpenAI. A photo may include the test result and anything else visible around it. OpenAI processes the photo to provide an AI-generated visual classification, confidence score, explanation, and—when appropriate—photo-quality suggestions. This feature is informational only and does not provide a medical diagnosis.
AIProxy also processes an originating IP address, an app-scoped device identifier, HTTP response status, and technical request metadata. If a request fails, its response body may be retained for troubleshooting. These technical data support request delivery, rate limits, abuse prevention, security, troubleshooting, and service analytics.
Storage and retention
- On your device: Linify saves the selected photo, AI result, and any notes in its on-device timeline until you delete the entry or remove the app's local data. Saved notes and timeline history are not sent to AIProxy or OpenAI as part of a later analysis.
- Linify's operator: Linify does not maintain a separate server copy of your selected photo or saved timeline.
- AIProxy: AIProxy routes the AI request and retains operational request records described above. AIProxy's published privacy policy does not specify one fixed retention period for those records. Its handling is governed by the AIProxy Privacy Policy.
- OpenAI: OpenAI states that API prompts, responses, images, and associated metadata may be retained in abuse-monitoring logs for up to 30 days by default. OpenAI may retain information longer where legally required or reasonably necessary to prevent harm. See OpenAI's API data controls and Privacy Policy.
Deletion requests
Delete a saved scan from Linify's timeline to remove its photo, result, and notes from the app's local storage. To ask about access to or deletion of provider-side records, email linify@yashgandhe.com with the approximate date and time of the request. Linify does not require an account, so it may not always be possible to associate a provider log with a particular person. Requests remain subject to provider capabilities and applicable legal or security retention requirements.
Purchases and subscriptions
Linify uses Apple In-App Purchase and RevenueCat to offer and validate Pro access, restore purchases, and maintain entitlement status. RevenueCat may process an anonymous app user identifier, purchase history, subscription status, device or app information, and related technical events for those purposes. Linify does not receive your payment-card details; Apple processes payment. See the RevenueCat Privacy Policy and Apple Privacy Policy.
Tracking and advertising
Linify does not sell pregnancy-test photos, AI results, or saved timeline data. It does not use them for third-party advertising or cross-app tracking.
Other Apps and Service Providers
Other apps covered by this policy may use service providers to deliver app functionality, process purchases, secure services, or understand technical performance. Their in-app disclosures and App Store privacy details describe any app-specific practices. Service providers may access only the information needed to perform their assigned tasks. Where they process personal information for us, we require them to provide the same or equivalent protection described in this policy and required by applicable platform rules and law.
Security
We use reasonable administrative and technical measures to protect information. However, no internet transmission or electronic storage method is completely secure, and absolute security cannot be guaranteed.
Children's Privacy
CHRM is restricted to adults aged 18 and over. Our other apps are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can take appropriate action.
Changes to This Privacy Policy
We may update this policy as our apps, providers, or legal requirements change. We will publish the revised policy on this page and update the date above.
Contact Us
For Linify privacy questions, contact linify@yashgandhe.com. For questions about another app covered by this policy, contact feedback@yashgandhe.com.