Privacy Policy
Last updated 17 November 2026
This policy explains what personal data Ishara ("we") handles, why, and what you can do about it. Ishara is operated by Hasan Abo-Shally, the party legally responsible for it. It covers two groups of people: customers, who create an account and install the widget, and reviewers, who leave notes through a customer's widget.
1. Our two roles
For customers' accounts we are the controller. For the notes reviewers leave on a customer's site, the customer is the controller and we are their processor: we handle those notes only to provide the Service to that customer, under our Data Processing Addendum (incorporated into our Terms of Service). Reviewers who want to access, correct or delete a note should contact the site's owner; if they contact us, we pass the request on.
2. What we collect from customers
- Account: name, email address, a salted hash of your password (never the password itself) or, if you sign in with Google, the identifier Google gives your account, your language, whether you confirmed your email, and your notification choice. When you choose “Continue with Google”, Google tells us your name and email address and that it has verified that address; we receive nothing else from your Google account, and never your Google password.
- Sites and settings: the sites you add, their addresses and allowed domains, and the widget settings you choose.
- Billing: your plan, its status and renewal date, the identifiers Creem gives us, and the amounts of your payments and refunds. Creem handles your payment details; we never see your card number.
- Security records: sign-in sessions (stored as hashes), API tokens (stored as hashes, with when they were last used), and short-lived rate-limit counters.
- Feedback on Ishara: while you are signed in, the dashboard shows the Ishara widget so you can leave us a note. For those notes we are the site owner and their controller; they hold what section 3 lists, and we read them to improve the Service (legitimate interests). The parts of the dashboard that show your reviewers' notes, your reviewer links and your API tokens are masked, so their text is never sent with a note.
3. What we collect from reviewers
- What they write and send: the note, a suggested wording, an optional photo, and the name they type.
- A screenshot of the page as they saw it, unless the customer turns screenshots off or the reviewer removes it before sending. It is drawn in the reviewer's browser from the page itself: typed form values, password and payment-card fields, elements marked
data-ishara-ignoreordata-ishara-mask, editable text and frames from other sites are left blank, and the widget is never in it. - Where the note was left: the page address (without its fragment), the page title and language, the chosen element's description, its CSS path and its static visible text (or the image's address when an image was chosen). The widget never reads typed values from form inputs, password fields or payment-card fields, and skips elements marked with
data-ishara-ignoreordata-ishara-mask. - Technical details: the screen size and the browser's user-agent string, kept with the note so the customer can reproduce a problem.
- The widget stores the reviewer's name, a random device token (so they can see their own notes and the replies) and, if they used a reviewer link, its key, in their browser's local storage. It sets no cookies and does not track reviewers across sites.
4. Why, and on what basis
- To provide the Service you asked for (contract): accounts, sites, notes, notifications, the dashboard, the API and the MCP server.
- To keep it secure and working (legitimate interests): rate limits, abuse prevention, error logs.
- To see how our website is used and how fast its pages load (legitimate interests), with Cloudflare Web Analytics: which pages are viewed, the referring site, the browser, operating system and device type, the country, and page-load timings. It counts visits without cookies and without identifying you.
- To bill paid plans and meet tax duties (contract and legal obligation), through Creem.
- To email you about your account and your notes. You can turn note emails off in your account settings; account and security emails cannot be turned off while you have an account.
We do not sell personal data, show advertising, or use analytics or advertising cookies. We do not use your content to train AI models.
5. Cookies
We use only the cookies the Service needs to work: to keep you signed in, to remember your language, and, for a few minutes, to complete a sign-in with Google. None is used for advertising or tracking, so we do not show a cookie banner. Our page analytics (Cloudflare Web Analytics) sets no cookies.
6. Who processes data for us
- Cloudflare hosts the Service (Workers) and stores its primary database (D1) and attached photos and screenshots (R2) in the European Union, provides optional bot protection on forms, and measures our website's page views and load times (Web Analytics).
- Creem (creem.io) is the merchant of record for paid plans: checkout, invoices, tax.
- Resend delivers our emails (stored in the United States for 30 days; customers can enable link-only notification emails in Account Settings so note text and reviewer names are never included in emails).
We may add providers as the Service grows; this list always names the ones that handle personal data.
Where data is processed outside your country, including in the United States, transfers rely on the safeguards the law requires (such as the EU Standard Contractual Clauses and the EU-U.S. Data Privacy Framework). Your own AI agents and scripts receive notes only through tokens you create; they are yours, not our processors.
7. How long we keep data
- Notes, photos and screenshots: until the customer deletes the note, the site or the account.
- Your account: until you delete it. Deleting it removes your sites, notes, photos, screenshots and tokens at once.
- Sign-in sessions and one-time links (password resets, email confirmations): only as long as they are needed, and never more than 30 days.
- Security records such as rate-limit counters (which can include an IP address): a few days at most. Records of the emails we sent: up to 30 days.
- Page analytics: Cloudflare keeps every page view for seven days, then a sample of about one in ten for longer-term charts.
- Database backups age out within 30 days, so deleted data disappears from them by then.
8. Your rights
You can see and correct your account details in your settings, download all your data as a file, and delete your account yourself. You may also ask us for access, correction, deletion, restriction or portability, or object to processing, by writing to support@useishara.com. You can complain to your data protection authority.
9. Security
Data travels over HTTPS (TLS with HSTS) and is encrypted at rest in Cloudflare's EU storage. Passwords are stored only as salted hashes, and sessions, tokens and one-time links only as hashes. Access to production data is limited to the people who run the Service. See our Security page for technical details and vulnerability reporting.
10. Children
The Service is not meant for children under 16, and we do not knowingly collect their data.
11. Changes
Ishara is in beta and this policy will change as it grows; the date at the top shows the latest version. If a change significantly affects how we use your personal data, we will tell you by email or in the dashboard before it takes effect. Questions: support@useishara.com.