Privacy Policy
1. Overview
WriteGentle is an AI-assisted communication tool that helps users draft, rewrite, and improve written messages.
This Privacy Policy explains what data we use, what we store, what we do not store, how users can manage their data, and how account and history deletion work.
2. Who this policy applies to
This Privacy Policy applies to users of the WriteGentle app and related services.
3. Data we use
We use certain data to provide the app and its core functionality.
This may include:
- account data such as email address and internal user identifier;
- app settings and preferences;
- user-created profiles and templates;
- generated response history, if the user enables history;
- limited usage and technical metadata needed to operate, secure, and improve the service;
- subscription or entitlement status where applicable.
4. Account data
We use account data to create and manage user accounts, authenticate users, protect account access, and support account-related actions.
This may include:
- email address;
- internal account or user ID;
- account creation and update timestamps;
- basic account settings.
We do not display the user’s password inside the app.
5. Settings and preferences
We may store user settings and preferences to operate the app and remember user choices.
This may include:
- interface language;
- privacy settings;
- saved form preferences;
- selected generation options.
6. User-created content
Depending on how the app is used, the service may process:
- text entered by the user;
- generated responses;
- user-created profiles;
- user-created templates.
7. History and generated content
7.1 History is off by default
Response history is disabled by default.
When history is disabled, generated responses are not saved to the user’s history.
Updated: For new accounts, the product applies these defaults on the server until the user changes them in Settings (stored server-side and reflected in the app).
7.2 Input text is not stored by default
Original user input text is not stored by default.
If the user separately enables storing input text in history, the original text may be stored together with the generated response.
7.3 If the user enables history
If the user enables history, generated responses may be stored in the user’s account history until the user deletes them or deletes the account.
8. What we do not store, or do not store by default
We do not store certain categories of data, or do not store them by default.
This includes:
- original input text by default;
- generated history entries when history is disabled;
- the full internal AI prompt;
- hidden system prompt logic exposed to the user;
- raw user input text in routine server logs;
- generated output text in routine server logs;
- full billing receipts unless retention is necessary and legally required.
9. AI-related processing
When the user requests a generated response, relevant text and selected parameters may be sent to the backend and to AI service providers as necessary to generate the requested result.
The service is designed to minimize stored content and avoid unnecessary retention.
Internal prompt construction and internal prompt protection mechanisms are not exposed to users.
10. Local device storage
The app may store limited data locally on the device for functionality and convenience.
This may include:
- interface language;
- privacy settings;
- local app preferences;
- cached or locally persisted user data associated with the signed-in account.
Where supported by the app, users may clear local data on the device without deleting their server-side account.
11. Authentication and password reset
Authentication is provided using secure account infrastructure.
If a user forgets a password, the app may initiate a password reset email flow through the authentication provider.
Password reset emails and related action links are handled through the authentication system rather than through a custom in-app mail server.
12. How we use data
We use data to:
- provide the app and its core features;
- authenticate users and protect accounts;
- save user-created settings, profiles, templates, and optional history;
- enforce subscriptions, entitlements, and usage limits;
- detect abuse, errors, and service issues;
- comply with legal obligations.
13. Data sharing
We do not sell personal data.
We may share limited data with service providers and processors that help us operate the app, such as:
- authentication providers;
- hosting and database providers;
- AI service providers used to generate responses;
- billing or purchase validation providers;
- analytics or error-monitoring providers, if used.
These providers receive only the data reasonably necessary for their role.
14. International data transfers
Depending on infrastructure and service providers, data may be processed in countries other than the user’s own country.
Where required, appropriate steps are taken to protect personal data during such transfers.
15. Data retention
We retain data only as long as needed for the purposes described in this Privacy Policy, unless a longer retention period is required by law.
Examples:
- account data is retained while the account is active;
- saved history is retained until the user deletes it or deletes the account;
- if history is disabled, history entries are not stored;
- limited billing or audit records may be retained where legally required.
16. User controls
Users may have the ability to:
- view account email and settings;
- enable or disable response history;
- enable or disable input-text storage in history;
- delete individual history items;
- delete all history;
- clear local data on the device;
- change password;
- change email where supported;
- sign out;
- delete the account from within the app.
17. Account deletion
If the user deletes the account through the app, the account and associated user data are deleted from our records, except for data we are legally required to retain.
This may include deleting:
- user profiles;
- user templates;
- saved history;
- usage records associated with the account, subject to legal and operational requirements;
- entitlement records associated with the account, where applicable.
Some limited legally required or audit-related records may be retained where necessary.
18. Children
The app is not intended for children under the age required by applicable law for independent use of such services, unless otherwise explicitly stated.
19. Security
Reasonable technical and organizational measures are used to protect personal data, including controls around authentication, transport security, access control, and data minimization.
No method of transmission or storage is completely secure, and absolute security cannot be guaranteed.
20. Changes to this Privacy Policy
We may update this Privacy Policy from time to time.
If material changes are made, we may update the in-app policy screen, the effective date, or provide other appropriate notice.
21. Contact
For privacy questions, support requests, or data-related requests, contact:
Website: www.personal.live
Email: writegentle@personal.live