Privacy Policy
Shot Flow · Privacy Policy · v1.0 · Effective 21 July 2026
| Field | Value |
| Operator | CHALET AQUARIUS LTD |
| Company number | 15587263 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | Shot Flow |
| Website | https://shot-flow.com |
| Contact email | info@shot-flow.com |
| Support / complaints | info@shot-flow.com (Monday–Friday, 09:00–17:00 UK time, excluding public holidays) |
| Governing law | Laws of England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Who this policy applies to: This policy applies to visitors, purchasers, account users and people who contact Shot Flow. It explains the personal data used to operate digital-content sales, protect payments, deliver licensed files and respond to rights requests. |
1. Introduction and scope
1.1 Introduction and scope standard. CHALET AQUARIUS LTD acts as controller for the Shot Flow website, Orders, accounts, fulfilment, support and direct marketing. For introduction and scope, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
1.2 Controls for introduction and scope. A decision concerning introduction and scope may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
1.3 Requests about introduction and scope. For visitors, purchasers, account users, support contacts and privacy requesters, safeguards used for introduction and scope protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
1.4 User duties for introduction and scope. Within visitors, purchasers, account users, support contacts and privacy requesters, when introduction and scope requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
1.5 Related provisions for introduction and scope. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about introduction and scope may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
2. Data controller and contact
2.1 Controller. The controller is CHALET AQUARIUS LTD, company number 15587263, of 20 Wenlock Road, London, England, N1 7GU.
2.2 Privacy contact. Send questions and rights requests to info@shot-flow.com with “Privacy Request” in the subject line.
2.3 Verification. We may take proportionate steps to verify identity or authority before disclosing, correcting or deleting data. Verification data is used only to protect the request process.
3. Age position
3.1 Adult service. Purchasers and account holders must be at least 18. The service is not designed or directed to children.
3.2 Discovery. If data appears to have been supplied by a child without appropriate authority, we may disable access and delete it unless retention is required for fraud prevention or law.
3.3 Parent or guardian. A parent or guardian may contact info@shot-flow.com with enough information to locate and review the relevant record.
4. Categories of personal data
4.1 Categories of personal data standard. Processing covers identity, account, transaction, entitlement, technical, support and marketing-preference data. For categories of personal data, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
4.2 Related provisions for categories of personal data. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about categories of personal data may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
4.3 Controls for categories of personal data. A decision concerning categories of personal data may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
5. Sources of personal data
5.1 Sources of personal data standard. Data comes from users, devices, payment providers, delivery systems and authorised business contacts. For sources of personal data, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
5.2 Limits on sources of personal data. If sources of personal data cannot be completed as expected, the response may include correction, deletion, restriction, provider instruction, incident response or regulatory communication. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
5.3 Correction of sources of personal data. For visitors, purchasers, account users, support contacts and privacy requesters, operational delivery of sources of personal data may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
5.4 Information relevant to sources of personal data. The normal treatment of sources of personal data may be adjusted for legal retention, verified requests, privileged material and the rights of other individuals. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
5.5 Misuse safeguards for sources of personal data. In applying sources of personal data to visitors, purchasers, account users, support contacts and privacy requesters, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
6. How we use personal data
6.1 How we use personal data standard. Data is used to contract, deliver, secure, support, comply with law and improve aggregate service performance. For how we use personal data, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
6.2 Decision criteria for how we use personal data. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with how we use personal data should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
6.3 Related provisions for how we use personal data. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about how we use personal data may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
6.4 Controls for how we use personal data. A decision concerning how we use personal data may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
6.5 Correction of how we use personal data. For visitors, purchasers, account users, support contacts and privacy requesters, operational delivery of how we use personal data may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
7. Lawful bases for processing
7.1 Lawful bases for processing standard. Processing relies on contract, legal obligation, legitimate interests and consent according to the activity. For lawful bases for processing, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
7.2 Misuse safeguards for lawful bases for processing. In applying lawful bases for processing to visitors, purchasers, account users, support contacts and privacy requesters, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
7.3 Controls for lawful bases for processing. A decision concerning lawful bases for processing may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
7.4 Requests about lawful bases for processing. For visitors, purchasers, account users, support contacts and privacy requesters, safeguards used for lawful bases for processing protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
7.5 User duties for lawful bases for processing. Within visitors, purchasers, account users, support contacts and privacy requesters, when lawful bases for processing requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
8. Payments and checkout
8.1 Provider handling. Payment credentials are entered into a specialist provider’s secure systems. Shot Flow does not intentionally store full card numbers or card security codes.
8.2 Merchant data. We may receive a token, card brand, last four digits, billing country, authentication result, risk result, provider reference and payment status.
8.3 Fraud controls. Strong customer authentication, device checks, transaction velocity and manual review may be applied and may delay delivery for up to 24 hours.
8.4 Independent duties. The provider and issuer may act as independent controllers or regulated entities for fraud, legal and payment-network purposes.
9. Cookies and similar technologies
9.1 Cookies and similar technologies standard. Essential technologies support security and checkout; optional technologies follow the Cookie Policy and consent choices. For cookies and similar technologies, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
9.2 Controls for cookies and similar technologies. A decision concerning cookies and similar technologies may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
9.3 Correction of cookies and similar technologies. For visitors, purchasers, account users, support contacts and privacy requesters, operational delivery of cookies and similar technologies may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
9.4 Outcome for cookies and similar technologies. The rules on cookies and similar technologies should be read with the Cookie Policy and applicable United Kingdom data-protection law. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
10. Sharing of personal data
10.1 Sharing of personal data standard. Data may be shared with vetted payment, hosting, delivery, email, support, analytics, security and professional providers. For sharing of personal data, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
10.2 Outcome for sharing of personal data. The rules on sharing of personal data should be read with the Cookie Policy and applicable United Kingdom data-protection law. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
10.3 Decision criteria for sharing of personal data. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with sharing of personal data should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
10.4 Limits on sharing of personal data. If sharing of personal data cannot be completed as expected, the response may include correction, deletion, restriction, provider instruction, incident response or regulatory communication. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
11. International transfers
11.1 International transfers standard. Transfers outside the United Kingdom use adequacy, contractual safeguards or another lawful mechanism where required. For international transfers, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
11.2 Outcome for international transfers. The rules on international transfers should be read with the Cookie Policy and applicable United Kingdom data-protection law. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
11.3 Decision criteria for international transfers. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with international transfers should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
12. Data retention
12.1 Data retention standard. Data is retained according to contract, tax, dispute, security and consent criteria and then deleted or anonymised. For data retention, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
12.2 Information relevant to data retention. The normal treatment of data retention may be adjusted for legal retention, verified requests, privileged material and the rights of other individuals. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
12.3 Decision criteria for data retention. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with data retention should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
12.4 Related provisions for data retention. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about data retention may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
12.5 Controls for data retention. A decision concerning data retention may take account of account, order, device, consent, support and security records. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
13. Data security
13.1 Data security standard. Technical and organisational measures protect confidentiality, integrity, availability and resilience. For data security, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
13.2 Information relevant to data security. The normal treatment of data security may be adjusted for legal retention, verified requests, privileged material and the rights of other individuals. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
13.3 Decision criteria for data security. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with data security should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
13.4 Related provisions for data security. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about data security may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
14. Your privacy rights
14.1 Rights. Subject to legal conditions, an individual may request access, correction, erasure, restriction or portability, object to processing and withdraw consent.
14.2 Automated decisions. Where a solely automated decision produces a legal or similarly significant effect, the individual may seek information and human review where the right applies.
14.3 Response. We normally respond within one month. A complex or numerous request may be extended where law permits, with an explanation.
14.4 Complaint. An individual may complain to the United Kingdom Information Commissioner’s Office and may contact us first to seek resolution.
15. Marketing communications
15.1 Marketing communications standard. Marketing is sent only where permitted and every message provides an unsubscribe mechanism. For marketing communications, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
15.2 Decision criteria for marketing communications. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with marketing communications should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
15.3 Limits on marketing communications. If marketing communications cannot be completed as expected, the response may include correction, deletion, restriction, provider instruction, incident response or regulatory communication. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
15.4 Correction of marketing communications. For visitors, purchasers, account users, support contacts and privacy requesters, operational delivery of marketing communications may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
15.5 Information relevant to marketing communications. The normal treatment of marketing communications may be adjusted for legal retention, verified requests, privileged material and the rights of other individuals. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
16. Automated decision-making and profiling
16.1 Automated decision-making and profiling standard. Payment risk screening may automate a challenge or delay, with human review where applicable law requires. For automated decision-making and profiling, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
16.2 Outcome for automated decision-making and profiling. The rules on automated decision-making and profiling should be read with the Cookie Policy and applicable United Kingdom data-protection law. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
16.3 User duties for automated decision-making and profiling. Within visitors, purchasers, account users, support contacts and privacy requesters, when automated decision-making and profiling requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
17. Third-party services and links
17.1 Third-party services and links standard. Independent providers and linked sites process data under their own notices for their own purposes. For third-party services and links, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
17.2 Requests about third-party services and links. For visitors, purchasers, account users, support contacts and privacy requesters, safeguards used for third-party services and links protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
17.3 Information relevant to third-party services and links. The normal treatment of third-party services and links may be adjusted for legal retention, verified requests, privileged material and the rights of other individuals. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
17.4 Decision criteria for third-party services and links. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with third-party services and links should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
17.5 Related provisions for third-party services and links. Within visitors, purchasers, account users, support contacts and privacy requesters, a question or correction about third-party services and links may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
18. Changes to this policy
18.1 Changes to this policy standard. Material changes are published with a new version and communicated where appropriate. For changes to this policy, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
18.2 Misuse safeguards for changes to this policy. In applying changes to this policy to visitors, purchasers, account users, support contacts and privacy requesters, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
18.3 Limits on changes to this policy. If changes to this policy cannot be completed as expected, the response may include correction, deletion, restriction, provider instruction, incident response or regulatory communication. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
19. How to contact us or submit a request
19.1 How to contact us or submit a request standard. Requests are submitted by email with enough information to locate the relevant account or Order. For how to contact us or submit a request, the provision is confined to visitors, purchasers, account users, support contacts and privacy requesters and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
19.2 How how to contact us or submit a request operates. To administer how to contact us or submit a request, Shot Flow uses access controls, provider contracts, data minimisation, retention rules and rights workflows. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
19.3 Outcome for how to contact us or submit a request. The rules on how to contact us or submit a request should be read with the Cookie Policy and applicable United Kingdom data-protection law. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
19.4 Decision criteria for how to contact us or submit a request. Within visitors, purchasers, account users, support contacts and privacy requesters, a notice dealing with how to contact us or submit a request should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
Personal data categories
| Category | Examples | Source | Purpose |
| Identity and account | Name, email, organisation, account ID, authentication history | User; account systems | Create and secure accounts; communicate; verify authority |
| Transaction and payment | Order ID, amount, currency, tax, tokenised reference, status | User; payment provider | Take payment; reconcile; refund; prevent fraud; meet tax duties |
| Licence and fulfilment | Purchased Asset or Bundle, entitlement, access and download logs | Order and delivery systems | Deliver content; support re-download; evidence fulfilment |
| Technical and usage | Internet Protocol address, device, browser, session, consent and security events | Automatically from device and service | Security; diagnostics; consent management; aggregate performance |
| Support and communications | Emails, issue details, screenshots, complaints and rights requests | User; support systems | Resolve requests; evidence decisions; improve support |
| Marketing preferences | Consent, campaign interaction, opt-out and suppression status | User; email provider | Send permitted marketing and respect choices |
Lawful bases
| Processing activity | Lawful basis | Notes |
| Account, Orders, licence administration and fulfilment | Contract | Necessary to provide the requested digital content and account functions. |
| Payment reconciliation, invoices and statutory records | Contract and legal obligation | Financial records are retained for applicable accounting and tax periods. |
| Fraud prevention, security and abuse investigation | Legitimate interests; legal obligation where applicable | Balanced against user impact; significant decisions receive review where required. |
| Support, complaints and legal claims | Contract and legitimate interests | Necessary to resolve issues and establish, exercise or defend rights. |
| Non-essential analytics and marketing cookies | Consent | Withdrawable through the consent tool or browser controls. |
| Email marketing | Consent or a permitted existing-customer basis | Every marketing message includes an opt-out. |
| Court, regulator or law-enforcement response | Legal obligation or legitimate interests | Disclosure is limited to a valid and proportionate request. |
Retention schedule
| Data category | Retention period | Trigger / criterion |
| Account profile and authentication history | Active account plus 24 months | Closure or last meaningful activity, subject to claims or security holds. |
| Orders, invoices, refunds and payment references | 7 years | End of the financial year in which the transaction occurred. |
| Licence and download-entitlement records | 7 years | Order date; retained to evidence the licence and fulfilment. |
| Support tickets and complaints | 3 years | Closure of the matter unless a longer claim period applies. |
| Security, access and fraud logs | 12 months | Event date; longer where linked to an investigation or chargeback. |
| Cookie-consent record | 24 months | Last choice or replacement by a newer record. |
| Analytics data | Up to 14 months | Collection date and configured analytics setting. |
| Marketing and suppression records | Until opt-out; suppression while needed | Withdrawal, objection or hard bounce. |
Schedule 1 — Practical Retention Guide
1. Order and licence records outlast ordinary browsing data because they establish what was purchased, the amount charged and whether delivery occurred.
2. Account closure removes access but does not require immediate deletion of invoices, fraud evidence or records needed to defend a claim.
3. Users should redact unrelated personal and payment information from screenshots before sending them to support.
4. Consent evidence is retained to demonstrate the choice in force, while a limited suppression record prevents accidental re-marketing after opt-out.
5. Records linked to a chargeback, rights claim or security investigation may be isolated under a legal hold until the matter and appeal period end.
Shot Flow · Privacy Policy · v1.0 · Effective 21 July 2026 · Published on the website; subject to update; the current published version governs.