Writerify
Privacy Policy
This Privacy Policy explains how Writerify collects, uses, and protects information when you use our Windows desktop application and website. Writerify is operated by Isloo Marketing, and the data controller for personal data described here is reachable at support@writerify.org. We take privacy seriously: Writerify is a local-first tool, which means most of your data never leaves your computer.
1. Quick summary
- We collect only what's necessary to operate the license system and process payments.
- Your generated articles, AI API keys, WordPress credentials, prompts, and image cache all stay on your local computer. They never travel to our servers.
- For payments and refunds we use Paddle, a Merchant of Record that handles billing data on our behalf.
- License activation uses your computer's hardware fingerprint (a one-way SHA-256 hash of OS-level machine identifiers). This is not personally identifying on its own.
- We do not sell, rent, or share your personal information with third parties for marketing.
2. Data we collect
Account & license data
- Email address — provided at checkout, used to deliver your license key and respond to support inquiries.
- License key — generated when you purchase, bound to your machine fingerprint.
- Machine fingerprint — a SHA-256 hash of your computer's stable identifiers (Windows MachineGuid + CPU model + RAM bucket + hostname + MAC). It is one-way; we cannot reverse it into the original IDs.
- Hostname — the friendly name of your computer (e.g., "John-PC"), used to display "License bound to: John-PC" in the app.
- Activation logs — timestamp + IP address + user-agent for each license activate / validate / deactivate call. Used to detect license abuse (e.g., one key activating from 50 different IPs in a week).
Payment data
All payment processing is handled by Paddle.com Inc., acting as Merchant of Record. Paddle receives your card or bank details — we do not. Paddle's privacy policy is at paddle.com/legal/privacy. We only receive a transaction ID, the email address you used at checkout, and the plan name.
3. Data stored on your computer only (never sent to our servers)
Everything below stays on your hard drive. Uninstall Writerify and it's gone (the output folder remains until you delete it manually).
- Your generated articles (.md files in your chosen output folder)
- API keys you paste for Claude / OpenAI / Gemini / OpenRouter / Pexels / Pixabay / YouTube
- WordPress + Next.js site credentials
- Custom prompt templates and your edits
- Image cache (WebP-compressed CC photos)
- Job queue history + activity log
- Settings, theme preference, and any custom prompts you've authored
These are stored in standard Windows app-data folders and protected by your operating system's user-account permissions. We do not sync them to the cloud unless you explicitly configure a publishing target (WordPress / Next.js) — and even then, articles go directly from your computer to that target, not via us.
4. How we use data
- To operate your license — activate, validate, and deactivate license seats; enforce the one-PC-per-key rule.
- To process payments and refunds — through Paddle.
- To provide support — when you email us, we read your messages and reply.
- To detect abuse — aggregate IP and fingerprint patterns help us identify license key sharing.
- To send transactional emails — your license key, refund confirmations, payment receipts. We do not send marketing emails without explicit opt-in.
5. Third parties
We use a small number of third-party services strictly to operate the product:
- Paddle — payment processing & tax compliance (Merchant of Record).
- Vercel — hosting for this marketing website.
- VPS provider (Hetzner / DigitalOcean) — hosts the license server that handles activate / validate / deactivate requests.
We have data-processing agreements in place with each. We do not share data with advertisers, marketing networks, or data brokers.
6. Google user data (Search Console & Google Analytics)
Writerify's AI Analyzer feature lets you optionally connect your Google account so the app can show your own websites' search and traffic performance inside your Writerify dashboard.
What we access
Only after you explicitly grant consent through Google's sign-in screen, and only with read-only scopes:
- Google Search Console (
webmasters.readonly) — the list of properties you have verified, and search performance data for the properties you choose (clicks, impressions, click-through rate, average position, top queries and top pages). - Google Analytics 4 (
analytics.readonly) — the list of GA4 properties you can access, and aggregate traffic metrics for the property you choose (sessions, users, pageviews, engagement time). - Basic profile (
openid email) — your email address, shown in the app so you can see which Google account is connected.
We never request write access. Writerify cannot change anything in your Search Console or Analytics accounts.
How we use it
- The data is fetched from Google's APIs and displayed to you, in your own dashboard, only — charts, score cards and tables for the sites you selected.
- We do not use Google user data for advertising, do not sell or rent it, do not share it with any third party, and do not use it to train AI or machine-learning models.
- No human at Writerify reads your Google data, except with your explicit permission for a support request, or where necessary for security investigations or to comply with applicable law.
How we store it
- The OAuth tokens Google issues are stored encrypted at rest in your Writerify account record and are used solely to fetch the metrics above when you open the AI Analyzer.
- Fetched metrics are held transiently (short-lived cache) to render your dashboard; we do not build long-term copies of your Search Console or Analytics data.
Revoking access
- In Writerify: AI Analyzer → Disconnect — this deletes the stored tokens immediately.
- In Google: myaccount.google.com/permissions → remove Writerify.
Limited Use disclosure: Writerify's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
7. Cookies & analytics
Your theme preference (dark/light) is stored in your browser's local-storage and never sent anywhere. This website uses Google Analytics 4 to understand aggregate visitor traffic (pages viewed, referral sources); GA4 sets its own cookies and processes data per Google's privacy policy. We do not run Facebook Pixel, ad-retargeting pixels, or any data-broker scripts, and we never tie analytics data to your Writerify account.
8. Data retention
- License records (email + key + fingerprint + activation log) are retained as long as your license is active, plus 24 months after expiry for tax + audit purposes.
- Payment records are retained as long as required by law (typically 7 years for tax).
- Support emails are kept for 24 months after the last reply, then deleted.
9. Your rights (GDPR / CCPA)
If you're in the EU, EEA, UK, or California, you have the right to:
- Access — request a copy of all personal data we hold about you;
- Rectify — correct inaccurate data;
- Erase — request deletion ("right to be forgotten") subject to legal retention requirements;
- Port — receive your data in a machine-readable format;
- Object / restrict — limit how we process your data;
- Withdraw consent — at any time, for any processing based on consent.
To exercise any of these rights, email support@writerify.org. We respond within 30 days.
10. Security
We protect your data with industry-standard practices: HTTPS everywhere, encrypted local-storage for license cache (XOR-encrypted electron-store), bcrypt-hashed admin credentials on the license server, and least-privilege server access. No internet-connected system is 100% secure, but we make a real effort.
11. Contact
All questions — privacy, GDPR / CCPA, security, general support — go to one inbox: support@writerify.org. Use a clear subject line (e.g. "Privacy request", "GDPR data access", "Security disclosure") for the fastest routing.
© 2026 Writerify. All rights reserved.