Legal

Privacy Policy

Version 1.10 · Last updated 11 September 2026

This policy explains what Touchline Analysis collects, why, where it is kept, and what you can do about it. It is written for the thing that actually matters here: your match video, which is often video of children.

The short version

We ask for a short list when you register: your name, your club or team name, your sport, the age groups you film (you can tick more than one), and a mobile number. If you are setting a club up we also ask for a contact email and roughly how many players and coaches you have. §2.1 says why we need each one. If you are joining a club, we ask for your name and nothing else.
Your footage stays on your device unless your club shares a match. Tags and presentations sync so your team can see them. A match somebody shares is uploaded to our video storage so teammates can watch it; a match nobody shares is not uploaded anywhere, on any plan.
We store the footage your club shares, and we do not routinely inspect it. No member of our staff has a way to play your footage back in the ordinary course of running the service. There are three narrow exceptions — an abuse report, a technical or security incident, and a lawful order — and §3 names all three rather than leaving them unsaid.
If you film under-18s, your club holds the parental consents and can produce them to us within 48 hours if we ask. We never see them. §6 and Terms §6.1.
Two things measure the site and the app: a cookieless count of page views, and an error reporter that tells us when something breaks. Neither sets a cookie, and neither follows you to other sites. We set two cookies of our own: one recognises your device so your plan’s device limit works, and one is set while you watch a match video so that the video link cannot be used by anyone but you. There is no advertising and no behavioural profiling, ever. §2.3 and §9 spell out exactly what they see.
Taking footage or a file out of the app is recorded. One row, inside your own club’s records: who, what, when, and by which route. It is not a record of what you watched or for how long, and nobody — not us, not your club owner — can edit or delete a row once it is written. §2.2a says exactly what a row holds and what it does not.
We never sell, rent, or share your footage or your data with anyone for their own purposes.
You can download everything we hold, or delete it, from Settings inside the app.
One address reaches us for all of it: [email protected]. §13 lists the subject tags that route it fastest.

This summary is here so you actually read something. Where it and the detail below disagree, the detail below is what governs.

1. Who we are

Touchline Analysis is operated by Dhruv Jain, Sole Proprietor, trading as Touchline Analysis — a sole proprietorship registered in India at C-1505 Ashok Towers, Dr S S Rao Road, Parel, Mumbai 400012, Maharashtra, India. In this policy “we”, “us” and “our” mean that entity, and “you” means the person using the app.

One address reaches us for everything: [email protected]. Putting [PRIVACY] at the start of the subject line is not a requirement — a plain email is answered the same — it only sorts your message to the right place faster. The links on this page fill it in for you.

2. What we collect

2.1 What you tell us when you register

What	Why we need it
Your name	To address you in the app and to show teammates who tagged or shared a match.
Your email address	It is your login, and the address a club roster files your place under. You can sign in with a Google account, with a password, or with a one-time link sent to this address. Passwords are handled by Google Firebase Authentication and stored hashed by them — we never see or hold one.
Club or team name	To group matches and to name the shared workspace your teammates join.
Sport	To set up sensible tag panels for what you actually play.
Age groups (youth, women’s or men’s — any combination)	To know whether the footage you are about to store is of children, which changes our obligations and yours. See §6.
A mobile number	So we can reach you about your account when email does not work — a failed sign-in, a problem with your footage, or the end of your free period. We do not use it for marketing and we do not pass it to anyone.
A contact email, if you are setting up a club	The address we should write to about the club, which may not be the address you sign in with — a club administrator often sets the account up for a coach. It defaults to your sign-in address.
How many players and coaches you have, if you are setting up a club	Two approximate numbers, so we can tell you which plan fits and can size the account correctly. They are not names and not a roster; nothing in the app is limited by them.

We do not ask for your date of birth or your postal address. Data we do not hold cannot be lost, leaked, or demanded from us.

If you are joining a club that already exists, you are asked for your name only. Everything else in this table was answered by whoever set the club up.

2.2 What the app creates as you use it

Match data — the tags you log, timestamps, match names, scores, player names you type into a squad list, custom tag panels, presentations and their annotations. This is small structured text.
Match video — footage recorded in the app or loaded into it.
Device records — for each device signed in to your account, a random identifier we generate, a readable label (“iPhone · Safari”), and when it was last used. This exists so your plan’s device limit can be enforced and so you can sign a lost device out. It is visible to you in Settings ▸ Devices.
Local error diagnostics — if something goes wrong, the app records the error on your device so you can read it in Settings ▸ Diagnostics. That on-device log stays on your device: it is not transmitted to us unless you choose to copy it into a support email. Separately, a copy of the error itself — the message, the stack trace and the page it happened on — is sent to our error-reporting provider, Sentry, so faults get fixed rather than going unnoticed. §9 sets out what Sentry receives.
A record of footage and files taken out of the app — and because this one is about people rather than about the app, it is set out in full below rather than summarised in a line.

2.2a The download log — a record of who took what

This is new, and it records behaviour rather than content, so it is written out in its own section rather than buried in the list above.

When a club’s footage is opened from the cloud, or when anyone in a club saves a file out of the app, we write one row to that club’s own records. Each row holds five things and nothing else: the email address of the person, what it concerned (the match or presentation, by its identifier or its name), when, which route it took — match footage, a whole reel, a single clip, or an export such as a tags CSV, a report or a backup file — and, for cloud footage, how large the file was. It does not record what you watched, which part you watched, how long for, how many times you pressed play, your IP address, or your location.

Why we hold it. This service carries footage of matches, often including children. If a club ever needs to establish who took a copy of a game out of the app, there has to be an answer. Without a record, the honest reply to “who downloaded this” is “nobody can tell”, and for footage of children that is not an acceptable answer.

Who can see it. Your club, and only your club — the rows live inside your club’s own data alongside your matches, and every member of your club can read them. We do not build cross-club reports from them, we do not analyse them, and they are never used for advertising, profiling or ranking anybody. If you are a player, you can see that footage you appear in was taken a copy of, and by whom.

Nobody can edit or delete a row, including us and including your club owner. That is enforced by the database itself, not by a policy we promise to follow: rows can be created and after that they cannot be changed or removed by anyone signed in to the app. A log the person with most to hide can quietly correct is not worth having. The consequence is that rows outlive the thing they describe — deleting a match does not delete the record that somebody downloaded it — and the only thing that removes them is deleting the whole club, which erases them with everything else. §7 gives the retention period.

One limit, stated plainly rather than glossed. The row for cloud footage is written by our own servers at the moment access is granted, so it cannot be avoided. The rows for reels, clips and exports are written by the app on the device, which means somebody who deliberately modified the app on their own computer could avoid writing one. We will not describe those rows to you or to anybody else as tamper-proof, because they are not. They are an accurate record of ordinary use.

2.3 What we do not collect, and what we do measure

Page counts, not tracking. Our measurement is Cloudflare Web Analytics: it counts page views and load speed, sets no cookie, and gives us no cross-site identifier for you. There is no Google Analytics, no pixel, no session recorder, no heatmap tool on this site or in the app.
Two cookies, and neither is a tracking cookie. The first holds the random device identifier described in §2.2, and it exists so that this website and the app agree you are on one device rather than two — which is what makes your plan’s device limit count correctly. The second is set only when you play a match video, and its only job is to prove that the person asking for the video is the person the video link was issued to; it is what stops a copied link from working for anyone else. Both are first-party: no other site can read them, neither carries an advertising or profiling identifier, and neither is ever shared with anyone. Both are strictly necessary to provide the service you asked for, so you are not asked to consent to them and there is nothing to opt out of. If your browser blocks the first, nothing breaks — one device may simply be counted as two. If it blocks the second, cloud video will not play. That is the whole of it:

Name	What it is for	How long it lasts
`fi_did`	Holds the random device identifier so the website and the app recognise one device as one device. Nothing else reads it and nothing else is stored in it.	400 days, or until you clear your browser’s storage
`__Secure-fi_vb`	Set only when you open a match video from the cloud. It holds your signed account identifier and nothing else, is sent only to the video address on this site, and cannot be read by any script — including ours. It is what ties a video link to you, so that a link copied out of the page does not work for anyone else.	One hour, matching the video link it goes with

Everything else is your browser’s own storage, not a cookie. Your tags, your matches, your presentations and your footage are held in the storage your browser gives this site so the app works offline. That storage is never sent to us with a request, and no other site can read it.
No advertising, ever, and specifically no behavioural profiling and no targeted advertising to anyone, which is prohibited outright where children’s data is involved.
No third-party fonts. Our fonts are served from our own domain, so no font company learns that you visited. Your IP address is, however, visible to the companies your browser does contact: Cloudflare, which serves this site and counts the page view, on every page load; Web3Forms, if you submit a form on our website or register a new club in the app; and Sentry, when an error is reported. §9 lists what each one receives.

If that posture ever changes — if we ever need a cookie that is not strictly necessary — this policy changes first and you will be asked to consent before it is set.

3. Your match video — the part that matters

Video is the most sensitive thing this service touches, so it gets its own commitments.

Hosted video is open, and the commitments below are live. A match reaches us only when someone in your club chooses to share it; everything else stays in your own device’s storage and is not uploaded.

Footage never leaves your device. It is held in your browser’s storage. We could not produce a copy of it if we were asked to, because we do not have one. This is true of every match nobody has shared, on every plan, and it remains true of everything on the Basic plan.
When you share a match, we store it so that you can watch it. That is the entire purpose. We store it, deliver it to people you have authorised, and nothing else.
We do not routinely inspect your footage. There is no moderation queue, no scanning, and nobody here whose job involves watching what you upload. We never analyse it, index it, use it to train any machine-learning model, or let anyone outside your team see it.
The three occasions we would look. We reserve the right to review specific content that has been flagged to us, and only for one of these reasons: to investigate a report of abuse or a safeguarding concern raised by a user, a parent or a guardian; to investigate a technical fault or a security incident affecting the material; or to comply with a lawful order or a law-enforcement request. Where we are permitted to tell you we have done so, we will. We would rather publish the exceptions than a promise with silent ones.
Suspected material involving a child is escalated to the police without delay. That duty falls on us personally under §19 of the POCSO Act 2012 and §67B of the Information Technology Act 2000, it does not depend on our having chosen to look, and it overrides every other commitment on this page. See Report Content.
Shared footage is encrypted in transit and at rest, and served through per-request links rather than public URLs, so that a link cannot simply be forwarded and used. Each link is signed, scoped to the single match it was issued for, tied to the account it was issued to — so a copied link opened by someone else, or in another browser, is refused rather than served — and it stops working one hour after it is issued. We give you the number rather than the word “short-lived”, because a policy that names it cannot quietly drift away from it. There is no public address for any match, and the storage itself is not reachable from the internet at all — every byte is served by our own servers, after they have checked who is asking. To make scrubbing and re-watching quick, two copies of footage you have already been allowed to watch are kept for a short time: your own browser keeps the parts you have played until that link expires — at most one hour, on your device only — and our servers keep recently watched parts close to you, which they hand out only after the same check, to someone the club has allowed to see that match. So if your access to a match ends, what you had already played can still replay on your own device until its link runs out; nothing you had not already watched becomes reachable.
Access is limited to your team. Who can view a match is decided by the membership of your team workspace, enforced on our servers and not merely hidden in the interface.
We will not hand over footage without a valid legal order, and where we are lawfully permitted to tell you that we have received one, we will.

The honest caveat, because a policy that pretends otherwise is worthless: an operator with administrative access to any storage system can technically reach the files it holds. What we commit to is that doing so is not part of how the service runs, is restricted to named administrators, and would only ever happen to investigate a specific fault you have reported to us or to comply with a legal order.

4. Where your data is kept

Structured match data (tags, presentations, account details) and match video are held with the infrastructure providers listed in §9. Structured match data is stored in asia-south1 (Mumbai, India), which is a contractual region: our provider commits to keeping it there. Match video is stored with Cloudflare R2 in the Asia-Pacific region.

Those two sentences look alike and are not, so we would rather spell out the difference than let it read as one promise. R2 accepts a regional hint when a bucket is created and honours it on a best-effort basis. Asia-Pacific is therefore a placement preference, not a guaranteed location, and not a data-residency commitment. We deliberately do not name a country for footage, because we could not stand behind it if we did.

Footage stays on your device unless someone in your club shares a match. When they do, a copy is held in R2 under your club’s control, and your club can delete that copy at any time (§7). Your device remains the primary copy of anything you have not uploaded. The app is built to work with no network at all, which means it is normal and expected for us to hold nothing about a match you have recorded.

5. Why we are allowed to hold it

We process your data on these bases:

To perform our contract with you — running the account, storing and delivering the matches you asked us to store.
Consent — where consent is the applicable basis. For footage of children this means verifiable parental or guardian consent under §9 of the DPDP Act 2023, obtained by the club before filming and warranted to us under Terms §6.1. The club retains the signed records and undertakes to produce them to us within 48 hours if we ask. We do not hold them ourselves — §6 explains why.
Our legitimate interests — keeping the service secure, preventing abuse of accounts and device limits, keeping backups so your data survives our mistakes as well as yours, and holding the download log described in §2.2a. That last one deserves naming rather than being folded into “security”: the interest is a club’s ability to establish who took a copy of footage that may show children, which we judge to outweigh the modest privacy cost of recording an email address, an identifier and a time. It is not used for any other purpose, and never for profiling.
Legal obligation — tax and accounting records relating to payments.

6. Footage of children

Most youth sport analysis is footage of under-18s. We treat this as the highest-risk thing on the platform, and the law agrees: under §9 of the Digital Personal Data Protection Act 2023, a child’s personal data may be processed only with verifiable consent from a parent or lawful guardian, and tracking, behavioural monitoring and targeted advertising directed at children are prohibited outright. There is no legitimate-interest route around it.

The club obtains the parental consent, and warrants to us that it holds it. It is the club that knows the players, meets the parents and runs the season, so it is the club that collects consent — before filming, not afterwards. Ticking a youth age group when you register puts that confirmation in front of you and you cannot finish registering without it; we record which wording you accepted and when. The full warranty is Terms §6.1.
The club keeps the signed forms and can produce them to us within 48 hours. We never see, hold or verify the consent forms themselves — holding a national library of children’s consent records would create exactly the concentration of sensitive data this design avoids. Instead the club retains them, and undertakes to send us copies within 48 hours if we ask — which we would do if a parent contacted us, if a report were made, or if a regulator or court asked us. We offer a template you can hand to parents, beside the consent tick when you register a youth team, rather than a form that sends anything to us.
We are not only a processor here, and we do not pretend to be. See §9.3 — we choose the storage, the security, the retention and how deletion happens, so the law’s duties attach to us for those choices as well as to your club for its own.
No profiling, no behavioural tracking and no advertising is applied to any user, and specifically never to a child. There is no advertising business here to tempt us later.
Player accounts are scoped. Where a plan gives players their own logins, those logins can reach only the clips and presentations shared with them.
A parent or guardian can come to us directly. You do not have to go through the club first. If you tell us footage of your child is held without consent, or you withdraw a consent you previously gave, email [email protected] — we will act, and we will tell the club that we have. The Grievance Officer route is open to you on the same terms as to an account holder.

7. How long we keep it

Data	Kept for
Matches and presentations you delete	10 days in the app’s recycle bin, on every plan, so a mistake is recoverable. Then permanently erased. You can empty the bin yourself at any time to erase them immediately.
Match video you delete	Video you have not shared is held on your own device, so deleting it removes it there, recoverable from the recycle bin for the same 10 days. The cloud copy of a shared match is different, and we would rather say so plainly: when your club deletes it, it is erased from our video storage straight away and cannot be recovered. There is no 10-day window for it, no copy in a backup, and nothing that ages out on a timer — the object is gone. A multi-gigabyte file is not something we keep after you have asked us not to, and the app asks for a heavier confirmation because of it. One limit, because it is true: somebody already watching that match when it is deleted can finish the part their player had already loaded, and no new viewing of it can be started by anyone, including them.
The download log (§2.2a)	For as long as the club exists. Rows are deliberately permanent and uneditable — nobody, including us and including your club owner, can alter or remove one, which is the only thing that makes the record worth anything in a dispute. They therefore outlive the match they describe: deleting a match, or emptying the recycle bin, does not delete the record that somebody downloaded it. Deleting the club erases them along with everything else it holds.
Backups	Up to 7 days. Deleted data can survive in a backup for this window before ageing out. This is how a restore is possible at all.
Enquiry and sign-up details	24 months from the last time we were in contact with you, then the record is deleted. This covers what you typed into the contact form on our website and the registration details that reach us when a club signs up (§2.1). If you ask us to delete it sooner we will — email [email protected] and it goes within 30 days. The clock restarts on contact, not on the first message, so an ongoing conversation is never cut off mid-way.
Your account, if you close it	Erased within 30 days, excluding records we must keep by law (below).
Billing and tax records	As long as tax law requires — typically 6 years from the end of the financial year they relate to. These contain invoice and payment details, not footage.
What happens if you stop paying	Your plan runs to the end of the period you paid for. Then 10 days in which you can sign in and download everything held in the cloud, but not upload. After that, everything we hold in the cloud — footage, matches, tags, presentations — is permanently deleted and cannot be recovered. Anything on your own device is untouched. Full detail in the Refunds & Cancellation Policy §4.

8. Your rights, and how to use them

Two of these are buttons in the app, not requests you have to make to us:

Download my data (Settings) — exports every panel, presentation, match record and tag we hold on your device as a single file. Video is not included, because it is too large to bundle; download footage from each match card instead.
Delete my data (Settings) — erases everything the app holds on that device, including stored video.

Depending on where you live, you also have the right to access, correct, or erase your data, to object to or restrict processing, to data portability, to withdraw consent, and to complain to your data-protection authority. Email [email protected] and we will respond within 30 days. We do not charge for this.

9. Who else touches your data

Every company that can touch data belonging to you or your club, what each one does, and where it holds it. This is the list a school’s data protection officer asks for, so it is published here and kept current rather than sent on request. They process data on our instructions only, and none of them may use it for their own purposes.

On the Basic plan most of this does not apply to you — footage never leaves your device, so no provider below holds it, and neither do we.

Provider	What for	What it sees
Cloudflare	Serving the website and the app	Standard request data (IP address, page requested) needed to deliver a web page
Cloudflare Web Analytics	Counting page views and load speed	The page requested, the page that referred you, and coarse device and country information. No cookie, and no identifier that could follow you across sites.
Sentry	Collecting JavaScript errors so faults get fixed	The error message, the stack trace, and the page URL the error happened on. Personal-data collection is switched off (`sendDefaultPii: false`), so your IP address, request headers and cookies are not attached. The honest residual: an error message can quote text that was on screen, and in this app that can include a match title, a club name or a player name.
Web3Forms	Delivering the contact form on our website to our inbox, and telling us when a new club signs up in the app	For the contact form: the name, email, message and other fields you typed into it. For a new sign-up: the registration details listed in §2.1 — your name, club, sport, age groups, mobile number, contact email and the two headcounts — and the plan you chose. In both cases, the IP address that submitted it. No match data, no tags and no video is ever sent to them.
Google (Firebase)	Sign-in and the sync of tags, presentations and account details	Your email address, account details, and match tag data — not video
Google (Gmail and Sheets)	Receiving mail sent to us, and keeping one row per enquiry so we can answer it and know who asked	The same contact-form and sign-up details Web3Forms delivers, kept as a record rather than only as an email. Retention is in §7. No match data, no tags and no video.
Cloudflare R2	Storing and delivering uploaded match footage	The video files for matches your club has chosen to share, encrypted at rest. They are delivered only through signed, per-request links scoped to a single match, tied to the account they were issued to, and valid for one hour — never a public URL. Footage nobody has shared is never sent here.
Cashfree Payments	Taking payment	Your billing details — your name, your email address and the amount. We never see or store your card number: it is entered on Cashfree’s own page and held by them, as RBI rules require.
YouTube (only if you choose it)	Playing back a match you have hosted on YouTube yourself	Only what YouTube already sees. We embed the privacy-enhanced player, so nothing is set unless you press play.

9.1 The legal entities, and where each one holds it

The same list again, named the way a procurement form needs it.

Entity	Role	Where it holds it
Cloudflare, Inc.	Serves the website and the app; DNS and TLS; cookieless visit counts; stores and delivers uploaded match video (R2); routes mail addressed to hello@ onward to our inbox	Global edge network; video in the Asia-Pacific region — a placement preference rather than a residency guarantee, see §4
Google LLC (Firebase, Gmail, Sheets)	Sign-in links, the accounts database, and team sync of matches, tags and presentations; also our own mailbox, and the sheet that records enquiries	Firebase in asia-south1 (Mumbai, India). The mailbox and the enquiry record sit on Google's general infrastructure and are not region-pinned — §10 covers what that means.
Functional Software, Inc. (Sentry)	Error reporting	United States
Web3Forms	Delivers the website contact form and the new-sign-up notification from the app	United States
Cashfree Payments India Private Limited	Takes payments and issues receipts	India

Both locations above are fixed when the project or the storage bucket is created and cannot be moved afterwards, so each is a decision rather than a default. They are not the same kind of statement: asia-south1 is a contractual region, while the Asia-Pacific placement of the video storage is a best-effort preference. §4 explains why we do not flatten the two.

9.2 Where your footage actually lives

Worth separating out, because it is the question that matters most and the answer changes with your plan:

Basic plan — footage is stored by the browser on the device that filmed it. It is not uploaded anywhere. No provider above holds it, and neither do we.
Paid plans — a match somebody in your club chooses to share is uploaded to our video storage (Cloudflare R2) so your teammates can watch it. A match nobody shares stays on the device that filmed it. Sharing is always a deliberate act: nothing is uploaded in the background.
Either way, there is no public link to a match. Playback requires a signed-in member of the team it belongs to.

9.3 Who is responsible for what

The Digital Personal Data Protection Act 2023 calls these roles Data Fiduciary (the one who decides) and Data Processor (the one who acts on instructions). It would be convenient for us to claim we are only ever the second. We are not, and saying so would not survive contact with the facts:

Your club is a Data Fiduciary for footage of its players. It decides what is filmed, who may see it, and when it comes down, and it holds the parental consents.
We are also a Data Fiduciary in our own right. We choose the storage provider, the security controls, the retention windows and how deletion is actually carried out. Those are our decisions, not instructions we receive, so the Act’s duties — safeguards under §8(5), breach notification under §8(6), erasure under §8(7) — attach to us directly. We do not disclaim them.
We act as your Processor for what we genuinely do on your instruction: storing the matches you upload, delivering them to people you have authorised, and deleting what you tell us to delete.
For your own account details — your email, name and the club you entered — we are the Data Fiduciary outright.

What this means in practice, and it is the reason the distinction is worth the paragraph: a parent, a player or a coach can bring a request to us and we will act on it ourselves. We will not send you back to your club and call that an answer.

The companies in the table above are our sub-processors — they act on our instructions, on the same terms, and may not use anything they hold for their own purposes.

9.4 Changes to this list

We keep this list current: a provider added to the product is added here in the same release. For a new provider that can access footage or personal data, we publish the change at least 30 days before it takes effect, so a club with a procurement process has time to object. If you object and we can’t resolve it, you can cancel before the change takes effect, and your plan runs on to the end of the period you have paid for — the new provider is never introduced into a period you bought without it. To be told about changes, email [email protected] and ask to be added to the notice list. It is used for nothing else.

10. International transfers

Some of what we hold is processed outside India, so this section names which parts and what protects them. It is short because the honest answer is short.

Your match video does not leave the Asia-Pacific region, and your matches, tags and presentations are held in asia-south1 (Mumbai). Those are the two things most people are asking about, and neither crosses a border in the ordinary course. §4 sets out the difference between the two guarantees.
What is processed abroad. Error reports go to Sentry in the United States. Our own mailbox and the sheet that records enquiries sit on Google’s general infrastructure, which is not region-pinned, so a message you send us may be held outside India. Web3Forms, which delivers our forms, processes it in the United States. §9.1 says all of this in the table rather than only here.
What permits it. Under §16 of the Digital Personal Data Protection Act 2023, transfer out of India is permitted to any country the Central Government has not restricted, and it has not restricted any. We are not relying on a loophole and we are not relying on the EU’s Standard Contractual Clauses, which are a different law’s mechanism and would be the wrong thing to cite.
What protects it. Our contract with each provider — their data processing terms, which we have accepted rather than negotiated — requires them to process only on our instructions, to secure what they hold, and never to use it for their own purposes. The same obligations follow the data wherever the provider keeps it. If you need a copy of those terms for a procurement review, ask and we will point you at them.

11. Security

Said plainly enough that a school’s IT contact can check it. Every control here exists today — we would rather leave a line out than describe one we are still building.

11.1 Accounts and sign-in

Three ways to sign in. A Google account, an email address with a password, or a one-time link sent to your email. Passwords are handled entirely by Google Firebase Authentication, which stores them hashed — a password never reaches our own systems, and nobody here can read it.
Your inbox can reach your account. Both the one-time link and a password reset arrive by email, so that inbox is a way in whichever method you chose. Protect it with two-factor authentication.
Confirming a device. Opening a one-time link confirms the device that opened it: a link opened on one phone doesn’t authorise another, and forwarding one doesn’t quietly hand over your account. Signing in with a password or with Google admits that device directly, as those methods do everywhere — which is why the device list below matters.
Devices are visible and revocable in Settings ▸ Devices. Signing a device out stops it syncing immediately. Plans cap how many can be signed in at once, which also puts a ceiling on how far a shared login can spread.

11.2 Your data

Encrypted in transit (TLS — the site and app are HTTPS only, with no unencrypted route to fall back to) and at rest by the providers in §9.
Access control is enforced on our servers, not merely in the interface. A signed-in user cannot read another club’s matches by asking for them directly; what the app hides is convenience, what the rules refuse is security.
Video is never public. There is no shareable public link to a match, by design.
We hold very little about you (§2.1), and backups mean a fault on our side or a mistake on yours is recoverable (§7).

11.3 How the app is built

Offline-first. Recording and tagging never leave the device, which removes an entire class of exposure from the part of the product used most.
No third-party code on the critical path. Fonts and libraries are self-hosted rather than pulled from a CDN, so a compromised CDN cannot reach your session.
No advertising or tracking SDKs, and hardened response headers — HSTS, nosniff, a referrer policy, framing restricted to our own origin, and a content security policy.

11.4 Reporting a vulnerability

Email [email protected] with [SECURITY] in the subject. Our machine-readable contact is at /.well-known/security.txt. Please include what you found, the steps to reproduce it, and what an attacker could achieve; a working proof of concept is welcome, a screenshot of a scanner’s output usually isn’t enough to act on.

What we commit to: an acknowledgement within 3 working days, an honest assessment of what we think it is and what we intend to do, credit here if you’d like it once the fix is out, and we will not pursue legal action against you for research that follows the rules below. We deliberately do not publish a fix deadline: we are one person, the right timeline depends on what you found, and we would rather agree a real date with you than miss a printed one.

What we ask: use your own account and your own test data — don’t access, modify or keep anyone else’s footage, because this platform holds video of children and that line is not negotiable. No denial of service, no spam, no social engineering. Give us reasonable time to fix it before publishing, and stop as soon as you’ve proved the issue: reading one record to confirm access is a proof, downloading a database is not.

We don’t run a paid bug bounty. We’re honest about that up front rather than leaving it to be discovered after the work is done.

11.5 If something does go wrong

We’ll tell you. Where a breach affects your personal data we notify affected users and the Data Protection Board of India as the law requires, and we tell you what was affected and what to do about it. Our understanding of an incident may be incomplete, but it won’t be shaded.

If you need documentation for a procurement or safeguarding review — an information security policy, a data processing agreement, or this list in a signable form — ask at [email protected].

12. Changes to this policy

If we change this policy in a way that materially affects you, we will say so in the app before the change takes effect. The version number and date at the top always tell you which version you are reading.

13. Contact

There is one address, and it is read by the people who build this: [email protected]. A subject tag helps it reach the right place faster, and every link on our pages fills one in for you — but an untagged email is never turned away.

Subject tag	Use it for	First response
`[SAFEGUARDING]`	A child’s safety, or footage that should not exist. See Report Content.	Ahead of everything else. Acknowledged within 24 hours
`[GRIEVANCE]`	A formal complaint (Grievance Officer, §13.1)	72 hours — or 24 hours where it concerns a child — resolved in 15 days
`[REPORT]`	Other content that shouldn’t be on the platform	3 working days
`[PRIVACY]`	Access, correction or erasure of your data	3 working days, resolved within 30 days
`[SECURITY]`	A vulnerability (§11.4)	3 working days
`[BILLING]`	Payments, invoices, plans, cancelling	3 working days
`[SUPPORT]`	Everything else	3 working days

13.1 Grievance Officer

If something about this service has gone wrong for you — your data, your account, your money, or how we have behaved — this route gets you a named person and a written answer within a stated time.

Name: Dhruv Jain
Designation: Grievance Officer & Data Protection contact
Email: [email protected] — subject [GRIEVANCE]
Phone: +91 80800 90005 — Mon–Fri, 10:00–18:00 IST
Post: The registered address below, marked for the Grievance Officer

What this route is for: your personal data (a copy, a correction, or erasure — tag those [PRIVACY]); content about you that should not be on the platform; an account you have lost access to; a charge you do not recognise; or a decision you think we got wrong. If it involves a child’s safety, use Report Content instead — that route is separated from ordinary mail and dealt with ahead of it.

What to include, so the first reply is the useful one: the email address on the account (that is how we find you), your club or team name if the complaint concerns team data, what happened and when, and what you would like us to do. Please do not attach footage. Tell us where it is in the app and we will find it — sending it makes an extra copy of exactly the material you may be asking us to delete.

Within 72 hours — acknowledged. Within 24 hours if it concerns a child. In writing, with a reference and the name of the person handling it. Weekends included. Three days is what one person can honestly hold for a billing dispute or a data request. It is not what a complaint about a child’s footage deserves, so that one keeps the 24-hour window and is acknowledged ahead of everything else — tag it [SAFEGUARDING], or use Report Content, which needs no account and asks the questions we actually need in order to act.
We investigate We may come back with questions. Where we need to look at account records to answer you, we look at the minimum that answers it, and we log that we did.
Within 15 days — resolved A written decision: what we found, what we have done, and what we have not done and why. If something genuinely cannot be finished in 15 days, you get the reason and a date before the 15 days are up, not after.

Most data requests do not need us at all. Settings ▸ Download my data exports everything the app holds, and Settings ▸ Delete my account erases it. This route is for what those two buttons cannot do.

You do not need to go through your club, and we will not send you there instead of answering. For footage of players your club is a Data Fiduciary and so are we (§9.3), which means a request that reaches us is ours to act on. In practice: we act on it, we tell the club we have, and where the decision is genuinely the club’s to make — whether a match stays up at all — we say so, give you our own answer alongside theirs, and tell you what to do if you disagree with it. A parent or guardian who has no account here has the same route as anyone else. See §6.

If we do not fix it, our answer is not the end of the road and we will not pretend otherwise: the Data Protection Board of India for personal data under the DPDP Act 2023; the National Consumer Helpline (1915) or your District Consumer Disputes Redressal Commission for a service or billing complaint; cybercrime.gov.in or your local police for anything criminal — please also tell us, so we can preserve what is relevant.

Touchline Analysis (sole proprietor: Dhruv Jain), C-1505 Ashok Towers, Dr S S Rao Road, Parel, Mumbai 400012, Maharashtra, India. +91 80800 90005