PRIVACY POLICY
Version 1.6 — Last Updated: 20 October 2026 | Effective Date: 20 October 2026
SUMMARY: HAFYCH DOES NOT CURRENTLY OFFER A HAFYCH USER ACCOUNT OR CONTENT-STORAGE SERVICE FOR ORDINARY USER CONTENT. OPTIONAL CLOUD FEATURES SEND DATA DIRECTLY TO THE USER'S SELECTED PROVIDER. WRITER STUDIO CAN CONTINUE SYNCHRONIZING AFTER THE USER ENABLES SYNC; COLLABORATION SHARES PROJECT DATA WITH INVITED PARTICIPANTS. REVENUECAT AND APP STORES PROCESS PURCHASE AND ENTITLEMENT DATA. HAFYCH MAY PROCESS SUPPORT EMAILS AND LIMITED PURCHASE INFORMATION AVAILABLE THROUGH PROVIDER DASHBOARDS.
1. Controller and Contact
For personal data processed by HAFYCH for its own purposes, the controller is Nazarii Hafych, acting under the HAFYCH brand. HAFYCH is not a separate legal entity.
Controller: Nazarii Hafych
Public contact address: Kharkiv Oblast, Kharkiv District, village of Borshchova, Bazivska Street 10, Ukraine
Telephone: +48 571 088 639
Privacy email: nazariihafych@gmail.com
Website: https://hafych.com/
No data protection officer has been appointed. Privacy requests are handled directly by Nazarii Hafych through the email above. This statement does not prevent appointment of a data protection officer or representative if later required by law.
2. Scope and Privacy Roles
This Privacy Policy applies to the Apps and Website. Actual processing varies by App, operating system, permissions, purchase status, provider configuration, and feature selection. Part III states the current shared architecture known to HAFYCH. A store disclosure or permission prompt may provide additional App-specific detail.
2.1 HAFYCH as Controller
HAFYCH acts as controller for data it decides to process for support, legal notices, security, entitlement administration, enforcement, product management, and its own compliance. HAFYCH may receive limited purchase and subscription information through Google Play or RevenueCat dashboards even though it does not process the underlying payment card.
2.2 Organizations and Business Users
An organization using an App for its own purposes normally determines why and how its personnel or other persons’ content is handled and is responsible for its own notices, legal bases, permissions, employment rules, security, and data-subject requests. HAFYCH acts as processor only to the extent it processes personal data on documented instructions for a Business User and the separately published Business-to-Business Data Processing Addendum applies.
2.3 Independent Third Parties
Google, Apple, RevenueCat, Google Drive, Dropbox, a user-selected AI provider, Cloudflare, GitHub, operating-system file providers, device manufacturers, and other providers may act as processors, service providers, or independent controllers depending on the service and legal context. Their own privacy notices govern processing they independently determine.
3. Current Data Architecture
No HAFYCH account system. Users do not create a HAFYCH username or password.
No HAFYCH content backend. HAFYCH does not operate a server that stores ordinary User Content.
Local or user-selected storage. Content may remain on the device, be sent directly to Google Drive or Dropbox through a user-enabled cloud feature, or be stored in a folder or file provider that the user selects through the operating system. AllPDF confirms each result-file transfer. Writer Studio's enabled backup and collaboration features can perform subsequent synchronization automatically, including after edits, without a separate confirmation for each transfer.
Optional AI transfer. AllPDF can send a bounded amount of extracted document text—not the PDF file itself—to the AI provider selected and configured by the user, but only after the user invokes an AI action and confirms the document-specific transfer.
Subscription infrastructure. RevenueCat and the relevant app store may process purchase history, App User IDs, receipts or purchase tokens, entitlement status, and technical metadata.
Direct support. HAFYCH may receive email, attachments, screenshots, or diagnostic information only when a person contacts support or sends a legal or privacy request.
Static Website. The primary Website is hosted through Cloudflare Pages; legacy pages remain on GitHub Pages. Cloudflare and GitHub may process request and security data under their own terms.
The absence of a HAFYCH backend does not mean that no data leaves a device. App stores, RevenueCat, selected cloud providers, operating systems, and network providers may process data needed for their functions.
4. Data HAFYCH and Providers May Process
4.1 Local User Content
Depending on the App, local User Content may include files, notes, text, settings, metadata, documents, images, audio, exports, backups, or other material selected by the user. HAFYCH does not receive ordinary local content merely because the App stores or displays it. Local content remains under the control of the device, operating system, user, and any selected storage provider.
4.2 Google Drive, Dropbox, and User-Selected File Providers
When a user enables Google Drive or Dropbox, or chooses a folder or file provider through the operating system, the App and provider may process selected file contents, names, identifiers, folder references, metadata, timestamps, synchronization status, authorization scopes, tokens, and error information necessary for the requested action. Google Drive uses the narrow drive.file scope. AllPDF never treats connection as upload authorization: a result file is read and uploaded only after the user selects the provider and confirms the transfer. A folder exposed by an Apple operating system can be backed by iCloud Drive, but the current Apps have no separate HAFYCH CloudKit content backend. Transfers occur directly between the device and selected provider; HAFYCH has no content server that receives the file.
4.2.1 Writer Studio for Android and Google user data
Writer Studio for Android, package com.writerstudio, is a local-first writing app. A HAFYCH account is not required. Google Sign-In and Google Drive are optional. When you connect Google, the app can process the connected account's email address, account identifier, display name, and profile image URL when provided by Google. These identify the connected account and associate the requested cloud operations with it; they are not added to RevenueCat customer attributes.
The only Drive permission requested is https://www.googleapis.com/auth/drive.file. It allows the app to create and manage project files created with the app or otherwise explicitly made available to it within that authorization. Writer Studio does not request unrestricted access to all files in your Drive, Gmail, contacts, or calendar. The app can upload, list, download, restore, and update its project backups and related project files. These files can contain manuscript text, project structure, notes, attachments and other material included in the project, together with file names, identifiers, revisions, modification times, and synchronization information.
Connecting and enabling Google Drive can enable automatic safety copies on save. Once enabled, synchronization may continue when you edit or save a project; each subsequent transfer does not require another consent prompt. You can control the feature in the app's cloud synchronization settings or disconnect Google Drive. New shared-writing sessions in the current Android interface use Dropbox; Google Drive provides the owner's project safety copies.
Google API data is used to provide the user-facing account, backup, restore, and synchronization functions described here. It is not sold, used for advertising or data brokerage, or used to develop or train generalized AI or machine-learning models. It is not sent to RevenueCat. Writer Studio uses Google API data in accordance with the Google API Services User Data Policy, including its Limited Use requirements. HAFYCH does not routinely view your Google Drive files; if you voluntarily send a file to support, that separate support communication is handled as described in Section 4.5.
4.2.2 Writer Studio for Android and Dropbox collaboration
Dropbox connects only after you choose Connect Dropbox and authorize the app in Dropbox. The app processes your Dropbox account identifier, email address, display name, profile image URL when available, and storage quota information to show the connection, associate operations with the right account, attribute changes, and handle storage limits. Collaboration can also process invited participants' email addresses, account identifiers, display names, access roles, membership status, authorship, and activity times.
Writer Studio uses Dropbox shared folders for project snapshots and collaboration files. Depending on the activity, transferred data can include manuscript edits, node and project identifiers, notes, comments, presence and activity records, project titles, file names, revisions, timestamps, and other project content. Inviting a participant makes the relevant project data available to that participant under the assigned Dropbox permissions. Owners can invite participants, change editor or reader roles, and revoke access. An enabled shared project can synchronize subsequent changes automatically.
The requested scopes are account_info.read for account identity, quota and contributor attribution; files.metadata.read for file metadata, revisions and change enumeration; files.content.read and files.content.write for project transfers and cleanup; and sharing.read and sharing.write for shared-folder identity, membership, invitations, role changes and access removal. No team, contacts, file-request or permanent-delete scopes are requested.
The Dropbox application uses Full Dropbox access because the shared-folder APIs used for collaboration do not support App Folder access. This permission technically permits access across the connected Dropbox account. The app's implemented project operations address its created or joined project resources; this is an application behavior, not a Dropbox-enforced restriction to a single project folder. Optional recovery also uses /.writer-studio/key-escrow-<deviceId>.json in your Dropbox. If you use key recovery, these files contain passphrase-encrypted recovery envelopes for project-vault keys, together with recovery format and device-related metadata. Recovery files are separate from shared-project folders.
Project snapshots use the app's project encryption where applicable. That does not make every collaboration file end-to-end encrypted: JSON sidecar files can contain readable manuscript edits and comments, and names, identifiers, membership and activity metadata remain available to the provider and people with the relevant file access. Do not rely on snapshot encryption to conceal all collaboration data from Dropbox or authorized participants.
4.2.3 Storage, disconnection and deletion for Writer Studio
Project data and cloud references can be retained locally on your device and in your selected provider account. Account identifiers and synchronization preferences are stored locally. Dropbox access tokens are held in memory; the refresh token needed to reconnect is persisted using the app's protected device storage. Google authentication and authorization credentials are handled through the Google Sign-In SDK and platform facilities. Neither provider's OAuth credentials are sent to a HAFYCH content server. Ordinary project data moves directly between the app and the selected provider, rather than through HAFYCH.
To stop future transfers, disable the relevant synchronization feature or disconnect the provider in the app. Dropbox disconnection clears the app's saved connection and attempts to revoke its token; you can independently revoke authorization in your Dropbox connected-app settings. You can revoke Google authorization in your Google Account connections. Signing out, revoking authorization, or uninstalling the app does not automatically delete cloud backups, recovery envelopes, exports, or copies already downloaded by collaborators.
Delete local projects and exports through the app or device controls, and delete provider files, shared folders and recovery files through the relevant provider. Dropbox and Google can retain revisions, deleted items or other records under their own policies. Removing a collaborator prevents future access under the updated permissions; it cannot erase copies they already obtained. HAFYCH cannot remotely delete files it does not possess or control. For support or other personal data held by HAFYCH, use the deletion-request procedure in Section 9.1.
4.3 RevenueCat Subscription and Entitlement Data
RevenueCat may process an App User ID assigned by its SDK or provided by the App, purchase history, product identifiers, store, subscription status, entitlement status, trial status, renewal, cancellation, expiration, refund and transaction events, receipt or purchase-token information, currency, locale, country or region, App version, platform version, SDK version, and timestamps. HAFYCH may access customer and transaction views in the RevenueCat dashboard for entitlement support, purchase analytics, fraud prevention, and product operation.
HAFYCH does not operate its own user-account system and does not require a name, email address, or telephone number to create a HAFYCH account. The inspected AllPDF and Writer Studio release configurations use automatically generated anonymous RevenueCat App User IDs, do not set RevenueCat Customer Attributes or advertising identifiers, and have no third-party analytics or attribution integration. There is no application webhook because there is no HAFYCH subscription backend; Google Play real-time developer notifications are connected directly to RevenueCat for subscription-state updates. Store declarations must be updated if this configuration changes.
4.4 Google Play and Future Apple Purchases
The relevant app store may process account information, payment information, device and technical data, purchase history, receipts, order identifiers, country or region, tax information, refund status, and fraud or security signals. HAFYCH generally receives only limited product, transaction, entitlement, refund, and status information necessary to supply or support the purchase. HAFYCH does not receive a complete payment-card number or CVV from the app store.
4.5 Support, Privacy, Security, and Legal Communications
If you contact HAFYCH, HAFYCH may process your email address, name if provided, organization if provided, message, attachments, screenshots, device or App information, purchase information, RevenueCat App User ID, diagnostic details, and HAFYCH’s response and internal notes. Do not provide information that is not necessary for the request.
4.6 Website hosting: Cloudflare and legacy GitHub Pages
The primary Website is hosted at https://hafych.com/ using Cloudflare Pages and Cloudflare delivery and security services. Legacy pages remain available at https://hafych.github.io/ using GitHub Pages. Cloudflare, GitHub, and network providers may process IP address, browser and device information, request time, requested page, referrer, security events, cookies or similar data, and logs under their own terms. HAFYCH does not intentionally place advertising cookies or run its own advertising network on the static Website.
4.7 Device and App Technical Data
An App, operating system, app store, or embedded provider may process App version, package or bundle identifier, device type, operating-system version, locale, region, timestamps, installation or App-instance identifiers, network information, and error or performance information necessary to operate the App, enforce purchases, or provide a selected feature. HAFYCH does not state that every listed data type is collected by every App.
An App may keep limited diagnostic or UX events locally for the current App session and may print them to debug logs in a debug build. The current releases do not send those events to a HAFYCH analytics backend. RevenueCat separately processes subscription and purchase analytics as described above.
4.8 AI Prompts and User-Selected Providers
Writer Studio editor AI actions create copy-ready prompts and place them on the device’s system clipboard. They do not automatically send manuscript text to HAFYCH, OpenAI, or another AI provider. Clipboard content is controlled by the operating system and user; it leaves the device only if the user pastes or otherwise sends it to an external service.
AllPDF lets the user configure OpenAI, Anthropic, or an OpenAI-compatible endpoint. Selecting a PDF remains local and does not start a network request. On the first AI action for each selected document, AllPDF identifies the provider and host, states the exact character count, and requests confirmation. If confirmed, AllPDF sends only the bounded extracted text needed for that action; the PDF file itself is not sent through the AI flow. The selected provider independently controls its processing, retention, model-improvement, security, and international transfers under the user’s relationship with that provider. API credentials entered by the user are stored through the device’s secure-storage facility where supported and are not sent to HAFYCH.
4.9 Permissions
An App may request a device permission only when required for a user-selected function. The operating system presents the applicable permission description and allows the user to grant, deny, or revoke access. Denial may prevent the relevant feature from working. No permission should be treated as authorization for an unrelated purpose. Exact permissions must remain consistent with the released App and store listing.
5. Data HAFYCH Does Not Intentionally Collect
Based on the current stated configuration, HAFYCH does not intentionally:
operate a HAFYCH user-account database or require a HAFYCH username and password;
operate a backend that stores ordinary User Content;
receive complete payment-card numbers, CVV values, or online-banking passwords;
sell User Content or personal data;
use an HAFYCH advertising network or intentionally track users across unrelated apps or websites for targeted advertising;
ask for a date of birth or independently verify age;
employ personnel or contractors who routinely access User Content; or
collect sensitive content merely because a user stores it locally or in a user-selected cloud account.
This Section is limited to HAFYCH’s intentional practices. Operating systems, app stores, RevenueCat, cloud providers, Cloudflare, GitHub, and networks may process data independently. A released build or provider configuration that introduces another data flow must be disclosed before or when it becomes active.
6. Purposes and Legal Bases
Where the GDPR, UK GDPR, or another law requires a legal basis, HAFYCH may process personal data for the following purposes and bases:
| Purpose | Typical data | Typical legal basis |
|---|---|---|
| Provide and restore purchases and entitlements | Purchase history, App User ID, product and entitlement status | Performance of contract; legitimate interests in reliable licensing and fraud prevention |
| Respond to support, privacy, security, and legal requests | Email, message, attachments, identifiers, diagnostic details | Performance of contract or pre-contract steps; legitimate interests; legal obligation |
| Protect Apps, users, rights, and provider accounts | Security, entitlement, transaction, abuse, and communication records | Legitimate interests; legal obligations; establishment, exercise, or defense of legal claims |
| Comply with law, sanctions, tax, accounting, platform, and court requirements | Transaction, identity, correspondence, and legal records | Legal obligation; legitimate interests in compliance and defense |
| Improve product and subscription operation | Aggregated or pseudonymous purchase and entitlement information | Legitimate interests; consent where legally required for optional processing |
| Enable user-selected cloud or file-provider features | Selected content, file metadata, and authorization data handled on device or by provider | Performance of the user’s request; consent or provider authorization where required |
HAFYCH will rely on consent where mandatory law requires it for a permission or optional processing. Consent may be withdrawn prospectively through the relevant setting or by contacting HAFYCH, but withdrawal does not invalidate earlier lawful processing.
7. Sharing and Recipients
HAFYCH may disclose limited personal data only where necessary and lawful to:
RevenueCat for subscription, purchase validation, entitlement, analytics, and fraud-prevention functions;
Google Play or Apple for distribution, purchase, subscription, refund, tax, platform, security, and compliance functions;
Google, Apple, Google Drive, Dropbox, or another user-selected operating-system file provider to perform a feature the user requests;
OpenAI, Anthropic, or a user-configured OpenAI-compatible provider when the AllPDF user explicitly confirms an AI text request;
Google or an email provider to receive and respond to support, privacy, security, or legal email;
Cloudflare for primary Website hosting, delivery, security and related request processing, and GitHub for legacy Website hosting;
professional advisers, courts, arbitral tribunals, regulators, law enforcement, platforms, insurers, or other authorities where reasonably necessary to establish, exercise, defend, enforce, or comply with legal rights and obligations; or
a lawful successor or transferee in connection with a sale, assignment, succession, restructuring, financing, or transfer of an App or related rights, subject to applicable privacy law.
HAFYCH does not sell personal data. A user-directed transfer to Google Drive or a provider folder selected through the operating system is controlled by the user and the provider’s own terms.
8. International Transfers
RevenueCat, Google, Apple, Cloudflare, GitHub, cloud providers, and other Third-Party Services may process data in countries outside your residence, including outside the European Economic Area or United Kingdom. Where HAFYCH is legally responsible for a transfer, HAFYCH may rely on an adequacy decision, provider data-processing terms, standard contractual clauses, another approved transfer mechanism, or a specific lawful derogation. User-directed transfers to a selected provider are also subject to that provider’s terms and transfer safeguards.
9. Retention and Deletion
| Category | Typical retention / control |
|---|---|
| Local User Content | Until the user deletes it, clears App data, resets the device, or uninstalls the App; exported and backup copies may remain elsewhere. |
| Google Drive, Dropbox, or user-selected provider folder | Controlled by the user and provider. Deleting from the App may not delete the provider copy; deletion must also be performed through the provider. |
| AI request text | Controlled primarily by the user-selected provider under its terms and the user’s configuration. AllPDF does not store the transmitted text on a HAFYCH backend. |
| RevenueCat purchase and entitlement data | Retained under RevenueCat and app-store policies and as needed for entitlement, refund, fraud, tax, legal, and support purposes. HAFYCH may request deletion of a RevenueCat customer record where legally appropriate and technically identifiable. |
| Support and ordinary correspondence | Ordinarily up to three years after the request is closed; longer where needed for a legal hold, repeated abuse, or an unresolved dispute. |
| Legal notices and dispute records | Up to six years after final resolution, or longer where a mandatory limitation, enforcement, tax, or records rule requires it. |
| Tax, accounting, purchase, refund, and compliance records | For the period required by applicable law, platform rules, or legitimate defense and audit needs, which may be up to ten years in some contexts. |
| Website request data | Determined primarily by Cloudflare, GitHub, and network providers under their policies; HAFYCH does not operate a separate web-log backend. |
9.1 Deletion Requests
You may request deletion of personal data controlled by HAFYCH by emailing nazariihafych@gmail.com with the subject “PRIVACY REQUEST.” HAFYCH may ask for information reasonably necessary to identify the relevant support record, transaction, or RevenueCat App User ID. HAFYCH cannot delete data it does not possess or control, including local files, user-controlled backups, Google Drive or Dropbox files, AI-provider records, copies in a user-selected provider folder, app-store records, or provider data retained under the provider’s own legal obligations.
Because there is no HAFYCH user account, there is currently no HAFYCH account to delete. Users delete local data through App or device controls and delete cloud data through the selected provider. Purchase records may remain with Google, Apple, RevenueCat, tax authorities, or other providers where legally required.
10. Privacy Rights
Depending on applicable law, you may have the right to request access, correction, deletion, restriction, portability, or objection; withdraw consent; and lodge a complaint with a competent supervisory authority. These rights may be limited where HAFYCH does not control the data, cannot identify the record, must retain it, or has overriding legal grounds.
To exercise a right, email nazariihafych@gmail.com with the subject “PRIVACY REQUEST.” HAFYCH may verify identity or authority in a proportionate manner. Do not send a passport or other high-risk identity document unless HAFYCH specifically explains why a less intrusive method is insufficient.
A person in the European Union may complain to the supervisory authority in the Member State of habitual residence, place of work, or alleged infringement. A person in another jurisdiction may contact the local authority available under applicable law.
11. Children and Age
The Apps are intended only for persons aged 18 or older and are not directed to children. HAFYCH does not ask for a date of birth or operate an account system that independently verifies age. A person under 18 must not use the Apps. If HAFYCH learns that it directly controls personal data submitted by a person under 18 in violation of this Policy, HAFYCH will take reasonable steps to delete or restrict it, subject to legal requirements.
12. Sensitive Data
A user may choose to place sensitive or regulated information in local files or a user-selected cloud account. HAFYCH does not receive that content merely because the App handles it. Do not send sensitive data to HAFYCH support unless necessary and lawful. The Apps are not represented as certified for regulated medical records, payment cards, classified information, critical infrastructure, or child data unless an App-specific notice expressly states otherwise.
13. Security
HAFYCH applies measures reasonably appropriate to the limited data and systems it controls, including limiting direct access to provider accounts and avoiding a HAFYCH User Content backend in the current architecture. Third-Party Services maintain their own security. No security measure is absolute, and HAFYCH does not guarantee that an App, provider, device, network, or storage location is invulnerable.
Users are responsible for device security, operating-system updates, passwords, cloud-account security, file permissions, backups, recovery material, and safe exports. Security concerns may be reported to nazariihafych@gmail.com. Do not publicly disclose a vulnerability before allowing a reasonable opportunity to investigate and remediate, unless applicable law protects a different disclosure process.
14. Advertising, Tracking, and Automated Decisions
HAFYCH does not intentionally sell personal data or operate cross-app behavioral advertising. RevenueCat processes purchase history for App functionality and subscription analytics and may process additional identifiers or attributes if configured. App stores and operating systems may independently process data for their own security, measurement, advertising, or platform purposes under their policies.
HAFYCH does not currently make a decision that produces legal or similarly significant effects solely by automated processing of a user’s personal data. Entitlement validation may automatically enable or disable paid features based on platform purchase status.
15. Cookies and Website Technologies
The static Website may use cookies, local storage, security mechanisms, or request logs supplied by Cloudflare, legacy GitHub Pages, the browser, or network providers. HAFYCH does not intentionally place advertising cookies on the Website. Browser controls may be used to block or delete cookies, although provider functionality may be affected.
16. Changes to this Privacy Policy
HAFYCH may update this Policy to reflect an App, provider, law, store requirement, or data-flow change. The revised version will identify its effective date and be made available through the Website, App, or store. Where law requires notice or consent for a material new use, HAFYCH will provide it before or when the new processing begins.
17. Contact
Privacy controller: Nazarii Hafych / HAFYCH
Email: nazariihafych@gmail.com
Telephone: +48 571 088 639
Public contact address: Kharkiv Oblast, Kharkiv District, village of Borshchova, Bazivska Street 10, Ukraine
Website: https://hafych.com/
PART III
CURRENT TECHNICAL AND PRIVACY SCHEDULE
Version 1.6 — Updated 20 October 2026 for the primary domain and Website hosting migration. Writer Studio Android cloud data disclosures are unchanged; other provider statements retain their stated scope and dates.
This Schedule is a factual supplement to the Privacy Policy. It does not claim that every HAFYCH App uses every optional feature. A released App’s store declaration and permission prompts must be narrower and exact for that package and version.
1. Provider and Distribution
Provider: Nazarii Hafych / HAFYCH
Current confirmed store distribution: Google Play
Apple App Store distribution: Not currently used as of 29 July 2026
Website: https://hafych.com/
User accounts: No HAFYCH account, login, or registration system
HAFYCH backend: None for ordinary User Content
Employees or contractors with content access: None; the Provider acts alone
Minimum age: 18 years
Own advertising system: None declared
Own analytics platform: None declared; RevenueCat provides subscription and purchase analytics
2. Current Data-Flow Matrix
| Data flow | Data involved | Destination / access | Purpose | Control / deletion |
|---|---|---|---|---|
| Local App use | User-selected content, settings, local metadata, files depending on App | Device and operating-system storage; HAFYCH does not receive ordinary content | Provide the selected App function | User deletes through App/device; uninstall may not delete exports or backups |
| Google Drive | Connected account email, identifier and profile when supplied; project content, names, file identifiers, revisions, timestamps, authorization and sync information | Directly between app/device and Google Drive within drive.file; no HAFYCH content server |
Writer Studio backup, restore and enabled automatic project safety copies; AllPDF user-confirmed result transfers | User disables sync or disconnects, revokes Google authorization and deletes local/provider copies; see Privacy Policy 4.2.1 and 4.2.3 |
| Dropbox for AllPDF | A result file selected for upload, its name and transfer metadata, authorization and error information | Directly to Dropbox after the user selects Dropbox and confirms the transfer; no HAFYCH content server | Save a completed AllPDF result at the user's request | User disconnects the provider and deletes the file through Dropbox |
| Dropbox for Writer Studio Android | Account/profile and quota information; collaborator emails, identifiers and roles; project snapshots, manuscript edits, comments, presence/activity and file metadata; optional encrypted recovery envelopes | Directly between app/device, Dropbox and authorized participants; Full Dropbox permission with application-selected project/recovery paths; no HAFYCH content server | Shared writing, invitations, role management, ongoing sync and optional key recovery | User disables sync/disconnects, revokes Dropbox authorization, manages membership and deletes files; downloaded copies and provider history can remain; see Privacy Policy 4.2.2 and 4.2.3 |
| User-selected folder / operating-system file provider | Selected file contents, names, identifiers, metadata and sync information where the operating system exposes the folder | Directly through the device and selected provider; an Apple-selected folder may be backed by iCloud Drive; no HAFYCH content server | Open, save, import, export, or sync as selected by the user | User manages the folder and provider through operating-system/provider controls |
| AllPDF AI request | A bounded amount of extracted text, provider/host, request parameters and technical error information; the PDF itself is not sent by this flow | OpenAI, Anthropic, or the OpenAI-compatible host selected by the user, only after document-specific confirmation | Perform the specific AI action requested by the user | User controls the provider account and provider-side deletion/retention; HAFYCH has no copy on an HAFYCH backend |
| RevenueCat | App User ID; purchase history; product, transaction, subscription, trial, entitlement, refund and status information; app/platform/locale metadata | RevenueCat systems; HAFYCH may view dashboard data | Purchase validation, entitlements, fraud prevention, subscription analytics, support | Request through HAFYCH where record can be identified; provider and store retention may continue |
| Google Play | Google account and payment data held by Google; product, order, receipt/purchase token, subscription and refund status available to App/providers | Google systems; limited transaction/status data to HAFYCH or RevenueCat | Distribution, payment, tax, subscription, refund, security, entitlement | Managed through Google account and Google Play; mandatory records may remain |
| Support email | Email address, message, attachments, screenshots, App/device/purchase details voluntarily supplied | Google email infrastructure and Nazarii Hafych | Support, privacy, legal, security, billing, and dispute handling | Ordinarily retained up to three years; legal records longer as stated in Policy |
| Website | IP address, browser/device and request data, timestamps, security logs, cookies or similar provider data | Cloudflare Pages and Cloudflare; GitHub Pages for legacy pages; network providers; HAFYCH does not run a separate web backend | Host and secure the Website | Provider-controlled under Cloudflare or GitHub policies |
| AI prompt / system clipboard | Selected manuscript text and generated prompt | Device system clipboard; no automatic AI-provider transmission | Let the user copy a prompt for optional use in an external service | User replaces or clears clipboard content and controls any later paste or transmission |
3. RevenueCat Configuration Statement
The inspected AllPDF and Writer Studio release code configures RevenueCat without a custom App User ID, so RevenueCat assigns an anonymous App User ID. The code does not call logIn, setEmail, setPhoneNumber, setDisplayName, setAttributes, or collect advertising identifiers. The current projects have no third-party analytics or attribution integration and no application webhook; Google Play RTDN is connected directly to RevenueCat. Each project uses the pro entitlement and is intended to expose monthly and annual packages through its current offering.
For the current configuration, the Google Play Data safety declaration must include purchase history collected for App functionality and analytics. Personal information and advertising/device identifiers are not introduced by the inspected RevenueCat integration. This conclusion must be rechecked whenever the SDK, release code, RevenueCat project, or provider integrations change.
4. Accounts and Deletion
No HAFYCH account is created, so a HAFYCH account-deletion flow is not applicable. A user may:
delete local data through App or device controls;
delete cloud data and revoke provider access through Google Drive, Dropbox, or the selected operating-system file provider;
manage or cancel subscriptions through Google Play; and
request deletion of data controlled by HAFYCH or a RevenueCat customer record by emailing nazariihafych@gmail.com and supplying information reasonably necessary to identify the record.
5. Device Permissions
The inspected Writer Studio Android manifest declares microphone access for its user-invoked dictation feature. AllPDF declares camera access for user-invoked capture and scan features; it does not request microphone, advertising-ID, or broad all-files access. Network access is supplied through the platform and provider libraries used for user-invoked Google Drive, Dropbox, AI, RevenueCat, and Google Play functions. Each permission must remain limited to the feature the user requests, be explained by the operating system and store documentation, and be rechecked in the final merged release manifest before every publication.
6. Security and Responsibility
HAFYCH’s current risk-reduction measure is architectural: ordinary User Content is not stored on a HAFYCH backend. This does not eliminate risk on the device, in cloud storage, in the app store, or at RevenueCat. Users remain responsible for device security, provider accounts, permissions, backups, and recovery material. HAFYCH makes no certification or guarantee of regulatory suitability.