Website data management is not only backups or CSV export. It defines who owns visitor data, how long it is kept, who may access it, and how you separate analytics aggregates from information that identifies a person (such as lead details from a form).
For site owners in Israel, these questions tie to privacy regulation, relationships with developers and marketing agencies, and customer trust. This guide explains how to manage measurement data in an orderly way when using a dashboard such as Insytix alongside other tools — without inventing policies that do not exist in practice.
The Insytix dashboard shows data for sites linked to your account. Access is controlled by user login and cloud-side permissions — not everyone with a link to the public site can see leads or recordings unless you invited them to the account. Understanding that boundary is the basis of sound data management.
A developer who only embeds the tag does not need full lead history — grant the minimum role needed to install and verify events.
Types of data a measurement system holds
Most setups separate three layers: statistical aggregates (visitor counts, viewed pages, traffic sources), business events (form_submit, phone_click, store order), and identifying information stored separately (form fields, order details, session recordings if enabled). Each layer needs different retention and sharing rules.
Aggregate stats are usually less sensitive than a raw lead with name and phone. A screen recording showing what a visitor typed is far more sensitive, so it requires clear on-site consent before enablement.
Retention and holding periods
Retention should match business use and law, not “forever because we can.” Old stat events help year-on-year comparison; old leads may matter for CRM or tax records. Session recordings usually have shorter lifecycles because they are heavy and sensitive.
In Insytix, events and leads live in remote storage so you can open history in the dashboard. This is not a substitute for legal advice on how long to keep customer records — but a good operational rule is internal documentation: what is deleted after X months, who approves deletion, and how to export before deletion.
When switching agencies, export leads and a sensible event list before access is removed — not to “take data away” but so nothing is lost for the client when the account is cleaned up.
Dashboard ownership and permissions
The account owner who registered the site in Insytix is usually the primary data gatekeeper. Developers and agencies often ask for access for setup or campaigns — inviting a user with the right role beats sharing one password. When the project ends, revoke access instead of leaving the account open “just in case.”
Separating sites in one account (multi-site) takes discipline: each site with its own tracking ID, no mixing clients. An internal register of who can see leads per site prevents leaks between businesses managed by the same agency.
Sharing data with third parties
Sharing can be manual export, dashboard access, or integration (such as a webhook or external analytics connection when enabled). Before sending leads to a CRM or media buyer, confirm your agreement with the end client (if you are an agency) allows it, and that transfer uses encryption in transit.
⚠️ A session recording view link — when the product supports it — is your responsibility: anyone with the link may see the content. Do not forward recordings via WhatsApp or email without checking who is in the thread.
Privacy and transparency for visitors
A site running tracking needs a privacy policy that briefly states what is collected, why, and how to request deletion or correction. Israel expects transparency; the EU and some cases also require explicit consent for cookies or behavioral tracking. A label saying “we use Google Analytics” without mentioning other active tags is a gap that can attract complaints.
Enabling session recordings or detailed click tracking especially requires explanation in the privacy page and a consent mechanism when applicable law requires it. Insytix provides collection; publishing policy and consent on your site remains your responsibility as site owner.
Security and backup
Strong passwords and two-factor authentication on the dashboard account reduce risk of lead breaches. On a shared computer — log out. Periodic export of important leads (CSV or via in-product export when available) keeps a copy not tied only to the UI.
Rotating API keys or webhooks when someone leaves is basic hygiene many agencies skip. Document which integrations are live per site and who holds keys.
Managing multiple measurement tools
When GA4 and Insytix run together, two vendors with different retention policies apply. Checklist: are both tags named in the privacy policy, does the cookie banner handle both per your setup, and are leads stored in one place defined as the action source.
Define a source of truth for action: Insytix for lead response, GA4 for monthly agency reports. That reduces number arguments and centralizes access control where it belongs.
Deletion and visitor requests
A visitor asking to delete details they submitted in a form — handle the lead row in the dashboard or CRM first, not only an analytics log. Aggregate anonymous stats usually cannot identify one person, so you cannot “delete a session” from a chart like a spreadsheet row.
💡 A simple internal process: privacy contact email, named owner, defined response time, and a log of requests. Even a small site benefits from a one-page doc, whether or not it is legally mandatory in every case.
Internal documentation and a minimal standard
A short internal doc — even a sheet or Notion page — pays off: active tools (Insytix, GA4, Meta pixel), who has access, last privacy policy update, and privacy contact. When a new hire or agency arrives, you skip WhatsApp archaeology.
Quarterly check: inactive dashboard users, stale webhooks still firing, WordPress plugin on a current version. Not a legal audit — maintenance that prevents surprises.
Keep a screenshot or export of the access list after each meaningful change — easier to show who saw what in a disputed period.
Summary
Orderly website data management rests on separating data types, clear dashboard permissions, visitor transparency, and focused sharing with partners. Insytix centralizes what happens on your site — you decide who sees it, what is kept, and how it fits other tools.
Spend an hour on policy and an access list. That prevents costlier mistakes than polishing a stat chart.
Frequently Asked Questions
Who owns the data in Insytix?
Data belongs to the business operating the site and account. The vendor hosts and displays it as a service; access and sharing decisions stay with the account and site owner.
Must we export data regularly?
Not always mandatory, but periodic export of important leads is good practice for business backup and CRM or vendor changes.
What should the privacy policy say about tracking?
Briefly: what types of data are collected (stats, forms, recordings if any), why, which third parties receive it, and how to contact for requests. Match tools actually installed on the site.