Drytally1. Who is responsible and what this notice covers
Huiru Gao is responsible for Drytally’s own processing described in this notice. Contact erchen735@gmail.com for privacy questions, requests or complaints. This notice covers the Drytally iPhone app, this product website and support correspondence. It does not replace Apple’s or another provider’s notice for services they control independently.
Our starting point is simple: your drinking diary is kept on your device. That does not mean every interaction with the app or website is invisible to all service providers. Purchases, web delivery and emails have separate data flows, explained below.
2. Diary and settings kept on your device
The app stores dates, drink counts and types, notes, selected diary photos, price/currency settings and calculated summaries in its local storage. It also stores profile name, signature and selected avatar, optional onboarding answers, appearance preferences, reminder settings, purchase-access cache and the version/date of legal acceptance.
Local database and preference storage are used to show your diary and preserve choices between launches. A shared App Group container lets the widget read a local snapshot. We do not receive this diary or profile in an operator-hosted database, and the current build has no diary-upload endpoint or cross-device sync service.
3. Photos and the system picker
You choose whether to select a profile photo or attach photos to a day. The app imports the items you select, makes a resized/compressed local copy and uses it in the relevant diary or profile view. It does not upload those images to us or scan your entire library as part of this workflow.
Removing an imported photo or resetting local app data affects the app’s copy. It does not delete the original image in Apple Photos, an export you saved elsewhere or an independent Apple device backup. Photos can contain sensitive information; choose carefully before exporting or sharing them.
4. Optional Apple Health writing
If you choose to enable Apple Health and iOS grants permission, Drytally can write the number of alcoholic beverages you log to Health. The integration is write-only: the app does not read your Health history for this feature. Health records may include technical metadata needed to associate a written sample with a local day.
You can revoke access or manage the written records in Apple’s Health controls. A Health copy is separate from the local diary and may remain after uninstalling Drytally. Apple’s own settings and policies govern any Health syncing or backup. We do not use Health information for advertising or send it to RevenueCat.
5. Reminders and widgets
Reminders are scheduled as local iOS notifications using the days and times you choose. They are not a marketing-email subscription or a remote push-messaging account. You can turn them off in the app or iOS settings.
Widgets use a snapshot in the app’s shared on-device container. A home or lock screen may be visible to other people with access to your phone. Choose widgets and notification display settings appropriate for the privacy you want.
6. Purchases, Apple and RevenueCat
Apple handles payments, account billing and store transaction records. Drytally uses transaction and entitlement information to recognise Pro access and support restoration. We do not receive your payment-card number or Apple Account password.
The current app is configured to use RevenueCat for purchase validation and restoration. It processes a generated anonymous purchase/customer identifier, product and transaction details, entitlement status, app/platform/version information and network information needed to deliver its service. Its subscription dashboard provides purchase analytics. The app does not set your diary, notes, photos, profile name or health records as RevenueCat customer attributes. It does not use an advertising identifier or link this anonymous purchase identity to a diary account.
Purchase processing supports access checks, restoration and fraud prevention. Purchase data may be retained by Apple or RevenueCat under their policies and legal obligations independently of local deletion. If RevenueCat configuration or other purchase data flows materially change, this notice and the store disclosure must be reviewed before distribution.
Our Cloudflare-hosted purchase service verifies Apple-signed transaction information and checks the current purchase status with RevenueCat. Authenticated provider events associate a hashed original transaction identifier with the anonymous RevenueCat customer identifier and event time. The service does not accept a client claim of Pro access as proof, and does not receive diary entries, notes or photos. Sandbox and production checks are separated. A test webhook or a local purchase fixture is not a real App Store purchase.
7. Website visits and support email
Cloudflare delivers this website and hosts the purchase-verification service and may process connection data such as IP address, requested URL, browser information, time and security-related events to serve and protect those requests. We do not add advertising pixels, behavioural analytics, fingerprinting, marketing forms or third-party font requests to the site. We do not set advertising cookies. The hosting provider may use necessary security mechanisms under its published policies.
If you email us, we receive the address, message, attachments and technical details you choose to send. Email providers also process that correspondence. Share only what is needed for the issue; do not send passwords, verification codes, payment-card data or full diary exports unless a specific support need has been explained and you choose to do so.
8. Why information is processed
Local records and settings make the features you request work. Purchase information enables paid access and restoration. Limited connection data serves and protects the website and purchase service. Support correspondence lets us answer requests, troubleshoot problems and comply with legal duties.
Where EEA or UK data-protection law applies to our processing, the relevant basis may be performing the agreement you request, complying with a legal obligation, or our legitimate interests in secure delivery, preventing fraud and answering enquiries, balanced against your rights. Optional device permissions remain your choice. If a separate consent is legally required for a particular processing activity, it must be requested separately and can be withdrawn; accepting the Terms is not a substitute.
9. Sensitive information and what we do not do
A drinking diary, notes or selected images may reveal health or other sensitive information. They remain local in the current product unless you deliberately share or export them, use Apple Health or include them in a support message. We do not operate an advertising profile, sell diary data, use it to decide insurance or employment eligibility, or use it to train an AI model.
The current app has no social account, friend directory, AI analysis service, remote diary backup or operator-run cloud sync. An existing service for a different product is not part of Drytally merely because it belongs to the same operator. A material future service would require its own disclosure and any required choices before use.
10. Recipients and international processing
Information goes to the recipients necessary for the activity: Apple for platform purchases and optional system services; RevenueCat for purchase services only when configured; Cloudflare for website delivery/security; and the providers used to exchange support email. We may also disclose information we actually hold when legally required, to protect rights or security, or in a lawful business transfer with appropriate notice and safeguards.
Providers may operate in countries outside your own, including outside the EEA or UK. Applicable protections depend on the service and transfer. We do not treat publication of this notice as consent to an otherwise unlawful transfer. Before enabling a new data flow, we must assess its legal basis and any required safeguards. Contact us for information about the protections applicable to a specific interaction; supplier policies are linked below.
11. Retention, deletion and backups
Local diary data is kept until you change or delete it, reset app data or uninstall the app, subject to iOS behaviour and backups you control. Legal acceptance and settings are local preferences. Existing Health records, original library photos and separately saved exports are not erased just by uninstalling Drytally.
Support correspondence is retained only as reasonably necessary to answer the issue, maintain a proportionate support record, protect legal rights or meet an applicable legal obligation. Provider transaction records and security logs follow the provider’s applicable retention arrangements; we do not promise an arbitrary deletion deadline for systems we do not control. You can ask about retention for information we hold about you.
The purchase service keeps hashed event identifiers for duplicate detection for up to 30 days, with expired entries removed when subsequent events are processed. The anonymous purchase binding is kept while needed to verify and support access to the purchased service; it is not a diary backup. We do not retain the complete signed purchase proof or full provider event payload in the application database. Contact us about access or deletion of service records we hold; deleting local diary data does not itself remove Apple or RevenueCat transaction records.
12. Your choices and privacy rights
You can edit local entries, remove photos, change permissions and use the app’s reset control. CSV/PDF export features are available under the current Pro feature rules. Your legal rights are not made conditional on buying Pro: contact us to exercise a right concerning information we actually hold. We cannot remotely retrieve or identify an on-device diary we have never received.
Depending on your location and the applicable law, rights may include access, correction, deletion, restriction, portability, objection and withdrawal of consent. Email erchen735@gmail.com with “Privacy request” and describe the information or interaction involved. We may verify identity proportionately and explain any lawful limit. We will respond within the timeframe required by the law that applies.
13. United States and California information
For applicable US state privacy laws, the relevant categories may include online/network identifiers and interaction data for web delivery; commercial purchase information when purchase services are enabled; and contact information or attachments you voluntarily send to support. Local diary information is described separately above because it is not uploaded to an operator database.
We do not sell personal information or share it for cross-context behavioural advertising. We do not use advertising tracking technologies, so a Global Privacy Control signal is consistent with our existing no-sale/no-advertising-sharing practice. Where a state law applies, you may exercise the relevant access, correction, deletion, portability, opt-out or appeal rights through the privacy email, including through an authorised agent where allowed. We do not discriminate for exercising a protected right. This section does not assert that every state statute applies to every interaction.
14. EEA/UK rights and complaints
Where the GDPR or UK GDPR applies, you may object to processing based on legitimate interests, withdraw an applicable consent and complain to the supervisory authority in the country where you live or work or where you believe a violation occurred. In the UK, the authority is the Information Commissioner’s Office. Exercising those rights does not remove other available remedies.
Our privacy contact is Huiru Gao at erchen735@gmail.com. This notice does not claim that a data-protection officer, EEA representative or UK representative has been appointed. Any representative or additional public contact required for the actual service and markets must be assessed and provided where legally required; it is not satisfied merely by listing a target region in a release plan.
15. Children, security and automated decisions
Drytally is not directed to children under 17. Local platform age restrictions and the eligibility terms also apply. We do not knowingly solicit children’s personal information through the website or support channel. If you believe a child has sent information to us, contact us so we can investigate and take appropriate steps.
We use the app sandbox, platform permissions and reasonable operational measures appropriate to the information processed. No software, device or transmission can be guaranteed completely secure. Protect your passcode and backups. The app’s charts are descriptive calculations from your entries, not automated decisions producing legal or similarly significant effects.
16. Changes, supplier notices and contact
This notice is version 2026-10-23.2, effective 23 October 2026. We will update it when actual data practices change and bring material changes to your attention where required. The app and website use the same document version; optional permissions and any separately required consent remain separate from this notice.
For questions, a privacy request or a complaint, contact Huiru Gao at erchen735@gmail.com. Relevant supplier information is available at apple.com/legal/privacy, revenuecat.com/privacy and cloudflare.com/privacypolicy. Following an external link takes you to that provider’s own service and policies.