Zenaccruage privacy policy overview
General draft — review before publishing

Privacy Policy

How Zenaccruage describes its collection, use, storage and sharing of information in connection with its analytical software and website. This is a general, editable draft.

Effective date: [Insert date] · Version: [Insert version] · This draft is not legal advice.

Document summary Draft
Applies toWebsite & platform
Controller[Insert entity name]
ContactVia contact page
Status: editable template
Next step: internal + legal review
Do not publish without review
Privacy

General privacy information

This page provides a structured starting point for describing how Zenaccruage handles information. Replace all bracketed text, confirm the details reflect your actual practices, and obtain independent legal advice before use.

Important notice

This policy is a general draft only. It does not constitute legal advice, does not imply legal review, and does not assert compliance with any specific law or jurisdiction.

  • Review and adapt all sections to your actual data flows.
  • Insert entity details, retention periods and contact routes.
  • Remove any section that does not apply to your operations.
Before publishing: confirm what you collect, why, where it is stored, who you share it with, and how long you keep it. Delete placeholder language.

Contents

Use this list to navigate the draft. Anchor links are for convenience only.

Sections 9–12 below cover children, international transfers, changes and contact details.

Approach

How this draft frames data handling

Zenaccruage provides quantitative analytical software for data analysis and decision support. This draft is structured around data minimisation, purpose limitation and transparency: collect only what is needed, explain why, and describe retention and sharing in plain language.

  • Describe only processing activities you actually perform.
  • Distinguish account and contact data from platform input data.
  • Explain user controls without overstating technical guarantees.

Do not add certifications, hosting claims, encryption standards or locations unless you have verified them. Remove any statement you cannot substantiate.

Zenaccruage data handling illustration
Policy text

Privacy Policy draft

Entity: [Insert full legal entity name, address and registration details]. Contact route: [Insert privacy contact method, e.g. via contact page]. Effective date: [Insert date].

CategorySummary — adapt to fact
Contact and account informationFor example: name, email, organisation, messages you send. [Confirm and edit].
Technical and usage informationFor example: log data, device and browser type, pages viewed. [Confirm and edit].
Platform input dataFor example: datasets, queries or files you choose to upload for analysis. [Confirm what you process and whether you store it].
Payment information[Include only if applicable. If a third-party processor is used, name it and link to its policy].

How to use this table

This summary is not exhaustive. Keep it consistent with the detailed sections below. If you do not collect a category, delete that row.

If you process sensitive, financial or third-party personal data, describe that separately and seek specific advice.

Do not list legal bases, retention periods or transfer mechanisms here unless reviewed for your situation.

1. Scope and application

1.1 This draft policy describes, in general terms, information associated with use of the Zenaccruage website and analytical platform, including pages, forms and sandbox or trial access where offered.

1.2 It does not apply to third-party websites, products or services that are linked to or integrated with our services. Review those third parties’ policies separately.

1.3 Where we act on behalf of a customer as a processor or service provider, the customer’s instructions and agreement may govern processing. [Confirm your roles and edit accordingly].

2. Information we collect

2.1 Information you provide. [Describe, for example: contact details when you enquire, account registration details, preferences, support correspondence, and any files or data you submit for analysis].

2.2 Information collected automatically. [Describe, for example: log files, IP address, device identifiers, browser type, referring pages, and interactions with the site]. State whether you use first-party analytics, and if so, what is measured.

2.3 Information from other sources. [Include only if applicable, for example: information from resellers, partners or public sources].

2.4 We aim to avoid collecting more than is needed for the purposes described below. Do not provide personal data of others unless you are entitled to do so. [Adapt].

3. How we use information

We use information for purposes such as:

  • Operating, maintaining and improving the website and platform.
  • Responding to enquiries, providing support and managing accounts.
  • Processing inputs you provide in order to generate analytical outputs.
  • Protecting security, preventing misuse, and maintaining records.
  • Communicating updates where you have requested them. [Confirm].

[Insert or delete purposes to match fact. If you use data for research, model improvement or marketing, describe that explicitly and explain consent or opt-out where relevant. Do not include purposes you do not pursue].

4. Sharing and disclosure

4.1 We share information only as described in this section. [List recipients, for example: service providers who support hosting, storage, analytics or communications; professional advisers; authorities where required by law; parties involved in a business transaction].

4.2 [If you use sub-processors or vendors, list categories and, if appropriate, names and locations. Link to relevant vendor policies only if verified].

4.3 We do not sell personal information as commonly understood. [Delete or revise if this statement does not reflect your practices].

5. Retention and deletion

5.1 We retain information for as long as needed for the purposes described, unless a longer period is required or permitted. [Insert specific retention periods or criteria, e.g. account data retained while account is active plus [X months/years]; logs retained for [period]; support messages retained for [period]].

5.2 [Describe deletion, de-identification or archival practices in general terms. Avoid technical guarantees unless verified].

6. Security measures

6.1 We apply organisational and technical measures intended to protect information against unauthorised access, loss or misuse. [Describe in general terms only what you actually do, e.g. access controls, encryption in transit, role-based access].

6.2 No system is completely secure. Do not state absolute security, specific standards or certifications unless verified and maintained. [Delete unverified claims].

6.3 [Describe user responsibilities, e.g. safeguarding credentials and notifying you of suspected unauthorised use].

7. Choices and rights

Depending on your location and circumstances, you may have rights to request access, correction, deletion, restriction, portability or objection. [Insert applicable process: how to make a request, what verification is needed, and expected response time. Do not name specific laws unless you have confirmed they apply].

You may be able to control cookies through browser settings, unsubscribe from marketing communications via the link provided, and manage account settings where available. [Confirm and edit].

We will consider requests in accordance with applicable requirements and explain our decision. [Adapt after advice].

8. Cookies and similar technologies

8.1 [Describe whether you use strictly necessary cookies, preferences, analytics or other trackers. List categories, purposes and durations].

8.2 [Explain how users can manage cookies, e.g. browser controls and any consent tool you provide. If you do not use non-essential cookies, state that].

8.3 Third-party tools, if any, are subject to their own policies. [List only tools actually used].

9. Children

Our services are not directed to children. [Insert age threshold relevant to your audience, e.g. under 16/18, after advice]. We do not knowingly collect information from children. If you believe a child has provided information, contact us via [insert route] so we can review. [Adapt].

10. International transfers and storage

[Describe where information is stored and whether it is transferred between locations. Include only verified locations. If transfers occur, describe safeguards in general terms and seek advice on appropriate wording. If no cross-border transfer occurs, state that].

11. Changes to this policy

We may update this policy to reflect changes in our practices. We will post the revised version with a new effective date. [Describe whether and how material changes will be notified, e.g. by notice on the site]. Continued use after the effective date is subject to the updated version. [Confirm].

12. Contact

For privacy questions or requests, use: [Insert privacy contact details or link to contact page]. Include what information to provide to help us respond, and expected handling process. [Do not insert unverified addresses, names or phone numbers].

Regulatory note: Zenaccruage supplies quantitative analytical software for data analysis and decision support. This policy covers information handling only and does not provide financial or legal advice.

Common questions about this draft

These answers explain the template itself, not your legal position.

Is this policy ready to publish?
No. It is a general starting draft. You should align every section with your actual data flows, complete all bracketed fields, remove inapplicable text, and obtain independent legal advice before publishing.
What should we check first?
Confirm what personal information you collect, where it is stored, which vendors have access, how long you keep it, and how users can contact you. Ensure the summary table, detailed sections and any cookie notice are consistent.
Should we list specific privacy laws?
Only after advice. Avoid naming regulations, legal bases or specific rights unless you have confirmed they apply to your entity, audience and processing activities. Generic language with placeholders is safer until reviewed.
How do we handle platform input data?
Be explicit. State what happens to files, datasets and queries submitted for analysis — whether they are processed transiently, stored, logged, used for improvement, or shared — and how users can request deletion. Delete any option you do not offer.
Next step

Review and finalise this draft

Complete the placeholders, verify hosting, vendors and retention periods, and have the result reviewed. For questions about Zenaccruage data handling, use the contact page.

Do not rely on this template as compliance or legal assurance. Seek independent advice for your circumstances.

Pre-publish checklist

  • Entity name, contact route and effective date inserted.
  • Collection, purposes, sharing and retention verified.
  • Cookie description matches actual tools used.
  • Unverified claims, dates and addresses removed.

This checklist is administrative only and does not confer legal review.