Privacy Policy
Last updated: 2026-10-23 · Version 2.0
This Privacy Policy explains what personal data I Hate Writing Reviews ("IHWR," "we," "us," or "our") collects when you use ihatewritingreviews.com and the IHWR application, why we collect it, who we share it with, how long we keep it, and the rights you have over it.
1. Who We Are (Data Controller)
The data controller for the personal data described in this policy is I Hate Writing Reviews, operated by [LEGAL ENTITY NAME AND POSTAL ADDRESS — to be completed by counsel before launch]. You can reach us about anything in this policy at privacy@ihatewritingreviews.com.
2. Information We Collect
We collect only the data needed to run the service. We do not run advertising or analytics trackers.
- Account information: your email address and a hashed password, or, if you sign in with Google or Microsoft, the name, email address and account id that provider returns to us. You may also add a profile name.
- Goals and evidence: the goals you enter and the evidence you add or import, including titles, descriptions, dates and any files you upload.
- Connected services: when you connect an external service, the credential or token you grant us (stored encrypted) and the work items we import from that service. See Section 3 for data about other people that this can include.
- Payment information: Stripe collects and processes your payment details on its own pages. We store your Stripe customer and subscription identifiers, your plan, its status and the email address used at checkout. We never see or store your full card number.
- Security and technical data: your IP address, used for rate limiting and recorded in hosting logs; an audit log of certain actions on your account (data exports and account deletion); and error reports if something goes wrong (see Section 7).
- Support correspondence: anything you send to our support, privacy or legal mailboxes.
3. Information About Other People
Work data is rarely only about you. When you connect a service, the items we import can contain personal data about colleagues, customers and other third parties, for example:
- names and email addresses of the people on an email thread, calendar event, pull request, ticket or document (authors, reviewers, assignees, reporters, attendees);
- snippets of message text from chat channels, email bodies, comments and ticket descriptions, including customer feedback on support tickets;
- meeting titles, descriptions and join details.
Why we process it and on what basis. We process this data in our legitimate interest, and yours, in identifying the work you did and the context it happened in (GDPR Article 6(1)(f)). Only the title and description of each item are shown to you and used for AI classification and review generation; the rest of the imported record is kept so the item can be re-read and so you can see where it came from. We do not use it for any other purpose, do not build profiles of third parties, and never sell or share it.
Your responsibilities. You must only connect accounts you are authorised to connect, in line with your employer's policies and the terms of the service. Our Terms of Service set this out in more detail.
Retention. Imported items stay in your account until you delete them or delete your account. Disconnecting a service stops future imports but does not delete the items already imported; delete them individually or delete your account to remove them.
If your data was imported by someone else. If you believe an IHWR user has imported data about you and you object to that processing, email privacy@ihatewritingreviews.com. We will consider your objection, and unless we have compelling legitimate grounds to continue, we will remove the data within one month.
4. How We Use Your Information and Our Legal Bases
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Providing the service: your account, goals, evidence, exports and AI-generated review drafts | Performance of a contract (6(1)(b)) |
| Importing work items from a service you connect | Your consent, given when you connect the service and withdrawn by disconnecting it (6(1)(a)); legitimate interests for data about other people (6(1)(f), Section 3) |
| Taking payment and managing your subscription | Performance of a contract (6(1)(b)); legal obligation for tax and accounting records (6(1)(c)) |
| Security: rate limiting, leaked-password checks, audit logging, abuse prevention | Legitimate interests in keeping the service and your account secure (6(1)(f)) |
| Error and performance monitoring | Legitimate interests in keeping the service working (6(1)(f)) |
| Service announcements, renewal reminders and replies to your requests | Performance of a contract (6(1)(b)); legal obligation for renewal notices (6(1)(c)) |
We do not send marketing email and we do not sell or "share" personal data for cross-context behavioural advertising.
5. AI and Automated Processing
IHWR uses Anthropic's Claude models to classify evidence, suggest which goals your accomplishments support, and draft performance reviews. For each request we send the titles and descriptions of the evidence involved, the text and categories of your goals, your review period dates, your profile name, and, when you ask us to improve a section of a review, the text of that section together with any feedback you type. Your data is not used to train AI models: under Anthropic's commercial API terms it is used solely to generate your output.
Automated decision-making. AI output in IHWR is a suggestion or draft that you review, edit and decide whether to use. We make no decisions about you by solely automated means that have legal or similarly significant effects.
6. Who We Share Data With (Subprocessors)
We share personal data only with the providers below, only for the purposes stated, and under contracts that restrict what they may do with it. We never sell your personal data.
| Provider | Purpose | Data sent | Location |
|---|---|---|---|
| Supabase | Database, authentication and file storage | Account email, hashed password or sign-in identity, goals, evidence, uploaded files, encrypted connector credentials, subscription records, audit logs | United States |
| Vercel | Application hosting and request logs | IP address, browser type, request URL and the data you send to our API | United States (Washington, D.C.) |
| Stripe | Payments, subscriptions, invoices and refunds | Email address, payment card details (entered on Stripe-hosted pages and never stored by us), billing details you provide, purchase history | United States |
| Anthropic | AI classification and review generation | Evidence titles and descriptions, goal text and categories, your review period dates, your profile name, your review drafts and any feedback you type when asking us to improve a section. Not used to train models | United States |
| Upstash (Redis) | Rate limiting, usage quotas and short-lived caches | Rate-limit counters keyed by IP address and user id (minutes), daily AI quota counters keyed by user id, AI classification results keyed by a hash of your goal and evidence text (24 hours), dashboard caches keyed by user id (up to 24 hours) | United States |
| Sentry | Error and performance telemetry | Error messages, stack traces, request URL, browser and operating-system type; 10% of requests are sampled as performance traces | United States |
| Trigger.dev | Background jobs for scheduled service syncs | Your user id and the id of each sync in job payloads and logs | United States |
| Have I Been Pwned | Leaked-password check at signup | The first five characters of the SHA-1 hash of a candidate password. The password itself is never sent | United States |
| Google and Microsoft (sign-in) | Optional sign-in with Google or Microsoft | Name, email address and provider account id returned by the provider when you choose that sign-in method | United States |
| Connected services you choose | Importing your work activity as evidence | Only what you authorise: GitHub, GitLab, Jira, Linear, Asana, Monday.com, Confluence, Notion, Figma, Zendesk, ServiceNow, Gmail, Google Calendar, Google Drive, Outlook, Outlook Calendar, Teams and Slack. We only read from these services and never write to them. Where a service lets us request read-only permissions (Google, Microsoft, Slack) we do; a personal API token you create may carry broader permissions than we use | Per service |
We may also disclose personal data where the law requires it, to protect our rights or users' safety, or as part of a merger or acquisition (in which case this policy continues to apply to your data).
7. Error and Performance Telemetry
We use Sentry to find out when something breaks. When an error occurs in your browser or on our servers, Sentry receives the error message and stack trace, the URL you were on, and your browser and operating-system type. Ten percent of requests are also sampled as performance traces (timings of page loads and API calls). We do not deliberately attach your name, email address or account id to these reports, and we do not use session replay. Sentry retains events for up to 90 days.
8. Where Your Data Is Stored
Your data is stored and processed in the United States. Our application runs in Vercel's Washington, D.C. region and our database is hosted by Supabase in the United States; the other providers in Section 6 operate from the United States.
If you use IHWR from the European Economic Area, the United Kingdom or Switzerland, your data is transferred to the United States. We and our providers rely on the EU-US Data Privacy Framework where the provider is certified and otherwise on the European Commission's Standard Contractual Clauses (and the UK Addendum) for those transfers. Contact us for details of the safeguards that apply.
9. Data Security
- Encryption: Connector credentials are encrypted with AES-256-GCM; all other data relies on our providers' encryption at rest and in transit. All connections to IHWR use TLS.
- Row-level security: every table in our database enforces PostgreSQL row-level security so that an account can only read and write its own rows.
- Authentication: passwords are hashed by Supabase Auth and never stored in plain text. When you choose a password at signup it is sent over TLS to our server and to Supabase Auth. Our server hashes it and sends only the first five characters of that hash to Have I Been Pwned to check it against known breaches (Section 6); the password itself is never sent to Have I Been Pwned.
- Read-only use of connected services: we only read from the services you connect and never write to them. Where a service lets us request read-only permissions (Google, Microsoft, Slack) we do; for services you connect with a personal API token (GitHub, Jira, Linear and others) the token may carry broader permissions than we use, so grant it the narrowest permissions the service allows.
- Private file storage: uploaded files are stored in a private bucket and served only through short-lived signed URLs.
No system is perfectly secure. If we learn of a breach that affects your personal data, we will notify you and any supervisory authority as applicable law requires.
10. How Long We Keep Data
- Account, goals, evidence, files and connections: for as long as your account exists. When you delete your account, or ask us to, we delete this data within 30 days. Copies in our database backups expire within a further 30 days. We keep a minimal deletion record (your former account ID, the time of deletion and a one-way hash of your email address) for 365 days as proof that the deletion was carried out; it contains no readable personal data.
- Audit logs: 90 days.
- Rate-limit and quota counters: from one minute up to one day.
- AI classification cache: 24 hours.
- Error and performance telemetry: up to 90 days at Sentry; background-job logs expire under Trigger.dev's retention.
- Payment and subscription records: for as long as tax and accounting law requires (typically seven years), held by Stripe and in our billing tables.
- Purchases made before creating an account: if you buy a plan and never create an account, we keep the email address used at checkout and the Stripe references so that you can claim your purchase. Email us to have them deleted.
- Support correspondence: up to two years after the matter is closed.
11. Your Rights
Wherever you live, you can exercise the following rights by using the tools in Settings or by emailing privacy@ihatewritingreviews.com:
- Access and portability: export your data from Settings at any time, or ask us for a copy of all personal data we hold about you.
- Correction: update your profile, goals and evidence in the app, or ask us to correct anything else.
- Deletion: delete individual evidence, disconnect services, or delete your whole account from Settings (see Section 10 for timing).
- Object: object to processing based on our legitimate interests, including the processing of data about you imported by another user (Section 3).
- Restrict: ask us to pause processing of your data while a dispute about it is resolved.
- Withdraw consent: disconnect a service at any time to withdraw the consent you gave when connecting it. Withdrawal does not affect processing that already happened.
- Complain: if you are in the EEA, the United Kingdom or Switzerland, you can lodge a complaint with your local data protection supervisory authority (in the UK, the Information Commissioner's Office). We would appreciate the chance to address your concern first.
California residents (CCPA/CPRA). You have the right to know what personal information we collect, use and disclose (this policy); to delete it; to correct it; to opt out of its sale or sharing (we do not sell or share personal information, and we do not use it for targeted advertising); to limit the use of sensitive personal information (we do not use it for anything other than providing the service); and not to be discriminated against for exercising these rights. You may use an authorised agent to make a request.
We will verify requests using the email address on your account and respond within one month (45 days for California requests), extendable where the law allows if a request is complex.
12. Cookies
We use only the cookies the service needs to work: session cookies that keep you signed in and protect against cross-site request forgery. We set no advertising, analytics or tracking cookies, so there is no cookie banner to dismiss.
13. Age
IHWR is a workplace tool for adults. You must be at least 18 years old to create an account. We do not knowingly collect personal data from anyone under 18; if you believe we have, email us and we will delete it.
14. Changes to This Policy
We may update this policy. The version and date at the top tell you which edition you are reading. For material changes we will post a notice on our website and email you where we hold a verified address, before the changes take effect. Continued use of the service after that date means the updated policy applies.
15. Contact Us
Questions, requests and complaints about this policy or our data practices: