Data Export & Portability

This page describes how BuildWise Technologies Kft. (“TaskShot”, “we”, “us”) handles requests to export or retrieve organisation content held in the TaskShot product (the web app at https://app.taskshot.app and related mobile clients). It is provided as a practical policy for customers and should be reviewed by your legal counsel; it does not replace the Privacy Policy or Terms of Service.

1. Who can request an export

Export and portability requests must come from an authorised representative of the organisation that holds the TaskShot subscription (typically an organisation owner or administrator), using the contact channel we recognise for that organisation (e.g. the billing or primary admin email). We may ask for reasonable identity verification before releasing data.

2. What “organisation content” includes

For export purposes, organisation content typically includes:

• Cases (metadata such as title, description, status, type, hierarchy, template-related fields, timestamps, and creator identifiers as stored in the product).
• Media files attached to cases (photos, videos, documents) stored in our object storage, under keys scoped by organisation and case.
• Derived product data where applicable (e.g. thumbnails, OCR or extraction results stored with media), subject to technical feasibility.

Some data may be held in separate product areas (e.g. tasks, drafts, user avatars). If your request should include those, state this explicitly when you contact us; scope and feasibility will be confirmed in writing.

3. How exports are delivered today

TaskShot does not guarantee a self-service “one-click” full account export in all tiers. Unless we publish a different feature, exports are handled through support: you describe the scope (see below), we confirm feasibility and timeline, then we provide data using a secure method (for example time-limited download links, or another agreed technical channel).

4. Scope you can ask for

• Date range: you may ask to limit export to cases created (or updated—specify which) within a date range. The narrowest clearly stated range helps us deliver faster.
• Folder layout: where technically practical, we can arrange delivered files in a logical structure (for example by year and month of case creation, then by case). Exact layout may depend on volume and tooling.
• Human-readable summary per case: we can include a small text or machine-readable file with key case metadata (e.g. description, creator id, timestamps) alongside media files, where feasible.

5. Cold storage and large exports

Closed cases may store original media in archival (cold) storage. Export of those objects may require a restore window before files can be copied or downloaded. That can extend delivery time and may incur additional infrastructure cost; we will confirm before proceeding where relevant.

Very large exports (high object count or total size) may require staged delivery, longer preparation time, or a paid export arrangement to cover compute, storage during packaging, and data transfer. Fair-use limits may apply for standard subscriptions; we will quote any fee before work begins.

6. Retention and access after subscription ends

Access to the live product may end when a subscription is cancelled or suspended, in line with the Terms of Service. Export requests after cancellation are still considered where we have a legal obligation or a reasonable residual duty to assist, subject to our retention rules and technical availability.

7. Personal data (GDPR) requests

Requests that relate primarily to personal data about an individual (access, erasure, rectification, portability under GDPR) should be sent to the same contact address. We will respond under applicable law. Organisation-wide content exports and individual GDPR requests may follow different timelines and verification steps.

8. How to contact us

Email info@taskshot.com with the subject line Data export request and include: organisation name, approximate scope (date range, all cases or selected identifiers), preferred delivery method if you have one, and the name of the authorised requester.

9. Updates

We may update this page when we introduce self-service export tools or change delivery practices. The revision date below reflects the last update.

Last updated: April 29, 2026