Privacy policy
Last updated 9 October 2026
1. Two kinds of data, two roles
Account data (about you and your team, for running your account): Edureify Inc. is the controller.
Visitor and customer data (collected by the Kratly script on your websites and from your payment and ad accounts): you are the controller and we are your processor, acting only on your instructions under our data processing agreement. If you are a visitor to one of our customers’ websites, please contact that website about your data; we will help them respond.
2. Account data we collect
Name, email address and a password hash; team membership and roles; billing status and the Stripe customer reference (we never see or store card numbers); security logs of sign-ins and sensitive changes, with IP addresses stored only as one-way hashes; questions you ask the AI assistant and its answers; and support messages.
If you add Kratly to Slack or Microsoft Teams: the workspace’s name and ID, Kratly’s bot token (encrypted), the channel you choose, and the messages that mention Kratly or are sent to it directly, with its answers. Kratly does not read other messages or files. The asker’s email address is looked up to check their access in Kratly. Slack and Teams data is not used to train AI models. See Kratly for Slack.
If you use a free tool on our website (the free video, the growth plan, the AI search audit or the app audit): the website or app address you enter, the result, and a one-way hash of your IP address (to limit how often each tool can be used). If you ask us to email you the result, we keep the email address you give with that website’s address, use it to send the link and may contact you about your result and Kratly. The free video’s link is only sent to an address at the website’s own domain. We remove these email addresses after 12 months, or sooner if you ask. These pages may use Cloudflare Turnstile to check that a person, not a bot, is starting the tool: Cloudflare receives your IP address and information about your browser for that check, under its own privacy policy. Legal basis: our legitimate interest in offering the tools and preventing their abuse.
We use this to provide and secure the Service, bill you, send service emails (verification, invitations, billing notices) and improve the product. Legal bases: performing our contract with you, and our legitimate interest in security and product improvement. We don’t send marketing email without your consent.
3. What the tracking script collects for our customers
Page address and title, referrer, campaign parameters (such as utm_source and ad click identifiers), screen size, browser, operating system and device type, the browser’s time zone (used only to correct the approximate country when a VPN or proxy makes the IP address look foreign), the email address and name a visitor enters in a form on the customer’s site (when the customer has not turned this off; password, payment and other sensitive fields are never read), events the customer’s site already sends to Google or Meta (for example “checkout started” or “purchase”, with their value), approximate location (country, region, city), clicks on links and buttons with their visible label, form submissions (of the values typed, only an email address and name are read, and only to identify the visitor; everything else is never read), scroll depth, time on page, page-speed measurements and JavaScript error messages, plus any custom events and email addresses the website owner chooses to send.
IP addresses are used only in memory to look up approximate location from a local database and to compute a hash that rotates daily. The raw IP address is never stored and, in production, never sent to a third party.
Payment information comes from the website owner’s Stripe or LemonSqueezy account through signed webhooks: amounts, currency, refunds, subscription status and the paying customer’s email. Card numbers are never received.
4. Cookies and browser storage set by the tracking script
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
| _av_id | Cookie (first-party) | Recognise a returning browser so visits can be counted once | 1 year |
| _av_sid | Cookie (first-party) | Group page views into a visit | 30 minutes, renewed on activity |
| _tg_buf | Local storage | Hold events briefly if the network fails, then resend | Until sent (max 200 events) |
| _tg_optout | Local storage | Remember that this browser opted out | Until cleared |
| _tg_vid, _tg_sid | Session storage | Cookieless mode only: identifiers for the current tab session | Until the tab closes |
Website owners can run the script in consent mode (nothing is sent until the visitor agrees) or cookieless mode (no cookies at all), and can make it respect Do Not Track and Global Privacy Control signals. The Kratly dashboard itself uses local storage only for your sign-in token and display preferences, and no advertising cookies.
5. Who we share data with
Only the service providers needed to run Kratly, listed with their purpose in our subprocessor list: hosting ([Hosting provider and region]), AI answers (Anthropic), our own billing (Stripe), and email delivery ([email protected]). Ad platforms and CRMs receive requests only when you connect your own accounts. We may disclose data if the law requires it, and will tell you unless prohibited. We do not sell personal data.
6. International transfers
Where providers process data outside your country, we rely on safeguards such as the European Commission’s Standard Contractual Clauses or the UK addendum. [Confirm the hosting region and each provider’s transfer mechanism.]
7. How long we keep data
| Data | Retention |
|---|---|
| Account data | While the account is open, then deleted within 30 days of closure |
| Visitor events and sessions | [25 months] by default, or as configured by the customer |
| Slack and Teams connections and conversations | Until you disconnect in Kratly or remove the app; then deleted. An unclaimed Slack install is deleted after 1 hour |
| Email addresses given to the free tools on our website | 12 months, then removed (the tool’s result stays, without the address) |
| Security logs | [12 months] |
| Invoices and billing records | As required by tax law, typically [7 years] |
| Backups | Rotated within [35 days] |
8. Security
Encryption in transit (TLS) everywhere; connector and payment-provider credentials encrypted at rest with AES-256-GCM; passwords hashed with bcrypt; tokens for email verification, password reset and invitations stored only as hashes; role-based access for team members; an audit log of sensitive actions; and least-privilege database access. We will notify affected customers without undue delay if a personal data breach occurs.
9. Your rights
Depending on where you live, you can ask to access, correct, delete, restrict or export your personal data, or object to processing. Email [email protected]. For visitor data, contact the website you visited; we support our customers in responding. You can also complain to your data protection authority.
10. Contact and changes
Edureify Inc., 447 Boradway Road New York USA. [email protected]. [Add EU/UK representative and DPO details if required.] We will post changes here and notify customers of material changes by email.