Privacy Policy — dripwriter
Last updated: November 9, 2026
Contact: cmolatef@gmail.com
This policy describes how information is processed when you use dripwriter.
Local writing
Local writing and Apple purchases do not require a Google account. Drafts, imported DOCX/RTF/TXT files, formatting and local history are processed and stored on your device. Device backups may include app data according to your backup settings.
Google Docs and cloud writing
When you choose Connect Google, we request permission to identify your Google account and access Drive files created or explicitly authorized for this app. We use a protected representation of Google’s stable account identifier to keep your cloud workspace separate from other users. We do not request your Google password, email or name.
Starting a cloud session sends the title, text, supported formatting and schedule to our Cloudflare-hosted server, which writes to Google Docs. When appending, existing document text is processed and stored to check edits safely. Cloud sessions and history remain associated with your account until account deletion. Confirmed cloud-edit snapshots can be reconstructed from the saved draft and operation history. Google Docs independently controls how its own versions are grouped.
Google access tokens are encrypted on the server. App connection credentials use iOS Keychain. Temporary encrypted connection flows expire after ten minutes; temporary deletion confirmation expires after five minutes. Security controls process short-lived IP-derived identifiers and connection metadata to limit abuse.
Existing accounts
Accounts created in earlier versions may retain protected Apple identifiers and encrypted Apple grants until deletion. Linking Google preserves an existing workspace only after secure account verification. Accounts are not merged using email. Google-confirmed Drive identifiers may be compared to recover a uniquely matching older workspace.
Apple subscriptions
Apple processes payments. The app uses StoreKit to verify signed subscription transactions and access. When you connect a cloud workspace, our server verifies Apple-signed purchase information and checks current subscription status directly with Apple. We process product and transaction identifiers, subscription status, expiration or revocation information, and a random app-account identifier to associate paid cloud access with your workspace. Original transaction lookup information is encrypted at rest, and transaction identifiers used for matching are protected with keyed hashes. We may receive signed Apple subscription notifications when available and periodically recheck status during use. We do not collect payment card details. Deleting the app, signing out or deleting your cloud account does not cancel an Apple subscription. Manage or cancel it in your Apple Account subscription settings.
Notifications
Notifications are optional. When cloud alerts are configured and enabled, a device notification token and random installation identifier are associated with your account. Notifications use generic status messages and session identifiers, not draft text or document titles.
Providers, purpose and security
We use Cloudflare to host and store cloud sessions, Google for authorized document functionality and identity confirmation, and Apple for purchases and optional notifications. Providers process information under their own policies and may process it outside your country. We use the data to provide writing features, authenticate workspaces, verify purchases, deliver optional alerts and secure the service. No system can guarantee absolute security.
We do not sell personal information or use advertising or analytics SDKs to track you across other companies’ apps or websites.
Deletion and your choices
To delete your cloud account, open Connect → Delete cloud account, type DELETE, confirm the same Google account, return to the app and confirm permanent deletion. This stops cloud jobs and removes owned sessions, history, credentials and notification registrations. It clears that account’s local drafts on the device completing deletion. Other offline devices can retain cached local files.
Google Docs remain in your Drive. Temporary encrypted provider-revocation tasks can remain for up to seven days; a protected deletion receipt remains for ten minutes to recover a lost response. Legacy Apple authorization codes, if any, expire within five minutes. The app tells you when a previous Apple connection needs manual unlinking.
You can review or revoke Google access in your Google Account’s connected-app settings. If you previously used Apple sign-in, you can review that connection in your Apple Account settings.
Depending on applicable law, you may request access, correction or deletion of personal information by contacting cmolatef@gmail.com.
Changes and contact
We may update this policy as the service changes and will publish a revised date.
Contact: cmolatef@gmail.com