DailyScore Security and Vulnerability Disclosure Policy
Version: 2026-10-10.1
Effective date: 10 October 2026
Public page: https://thedailyscore.app/security
Security contact: info@thedailyscore.app with the subject Security report
About this document
DailyScore values good-faith security research. This policy explains which systems may be tested, the limits needed to protect people and data, how to report a vulnerability, how DailyScore will respond and when research is treated as authorized.
DailyScore is operated by Yash Purandare, an individual in India.
Postal address: 75/76 Sector A, Indore, Madhya Pradesh 452018, India.
In this policy, Yash Purandare is called “DailyScore”, “we”, “us” or “our”.
1. The short version
- Test only the exact DailyScore assets listed as in scope in the published policy, using accounts and data you own or are expressly permitted to use.
- Never access, copy, change, delete or disclose another person's information.
- Stop immediately if you encounter personal data, credentials, private group content, a minor's information or evidence of active exploitation.
- Use the minimum testing needed to confirm the issue. Do not persist, move laterally, cause disruption, bypass payments for benefit or test safety and parent controls on real users.
- Report privately and promptly, provide reproducible evidence and allow reasonable time for investigation and remediation before public disclosure.
- When you make a good-faith effort to follow this published policy, DailyScore treats the covered research as authorized and will not initiate or support legal action over that research.
- This is a vulnerability-disclosure programme, not a paid bug bounty. No reward is promised unless a separate written offer says otherwise.
2. Scope
Only the assets in this table are in scope.
| Asset | Permitted testing |
|---|---|
The official DailyScore iOS and Android apps (com.dailyscore.quest), current store version | Static analysis and low-impact dynamic testing on a device, installation and test account you control |
https://thedailyscore.app (this domain only, not its subdomains) | Low-impact testing of the public pages |
| The DailyScore API used by the official apps | Low-impact testing through your own test account and data only |
A listed domain does not automatically include every subdomain, IP address, cloud tenant, provider console, development system or third-party integration. If an asset is not clearly listed, ask before testing it.
3. Systems and activities outside scope
Unless DailyScore gives specific written permission, do not test:
- Supabase, Google, Firebase, Apple, RevenueCat, Resend, KWS/Epic, IPinfo, GitHub, app stores, telecommunications networks or any other third-party system, account or infrastructure;
- employee, contractor, parent, guardian or user accounts other than your own approved test accounts;
- production administrator, support, moderation, recovery or provider consoles;
- real groups, friend codes, contacts, messages, habits, photos, backups, notification tokens, subscription records, age/eligibility records or parent- verification records;
- physical offices, equipment or people through social engineering, phishing, pretexting, bribery, threats or impersonation;
- denial of service, distributed denial of service, resource exhaustion, traffic flooding, destructive load testing or interference with availability;
- malware, ransomware, destructive payloads, persistence, command-and-control, cryptomining or supply-chain compromise;
- credential stuffing, password spraying, broad brute force, mass account creation or testing leaked credentials;
- broad automated scanning or high-volume requests without prior written approval and an agreed rate;
- interception of traffic you are not authorized to observe; or
- public disclosure, sale or transfer of an unremediated vulnerability or data obtained through testing.
Do not test whether age gates, Teen Mode, friend-only controls, parent consent, payments, account deletion, reporting or moderation can be bypassed using a real child, parent, unrelated person or live purchase. Ask for a disposable staging flow.
4. Good-faith research rules
Research under this policy means activity in which you:
- comply with this policy and applicable law;
- use only listed assets, your own approved accounts and synthetic data;
- avoid privacy violations, user harm, service degradation and destruction or manipulation of data;
- use an exploit only as far as needed to demonstrate the vulnerability;
- do not establish persistence, obtain a command shell, exfiltrate data, access secrets unnecessarily or pivot to another system;
- stop testing once the issue is demonstrated or sensitive data is encountered;
- promptly report the issue and keep vulnerability details confidential during coordinated remediation;
- securely delete any accidentally obtained DailyScore information as soon as we confirm preservation is no longer needed, unless law requires otherwise;
- respond reasonably to questions needed to reproduce and fix the issue; and
- do not demand payment, threaten disclosure, or condition deletion of data on compensation.
Proof should use the least harmful evidence. Prefer request/response excerpts with tokens and personal data redacted, a minimal screen recording using synthetic data, or a precise sequence of steps. Do not download an entire table or open additional records merely to show that access is possible.
5. If you encounter sensitive information
Stop immediately if you encounter another person's personal data, credentials, authentication token, private message, habit information, contact list, precise location, payment information, a minor's information, parent data, backup archive, secret key or other confidential information.
Do not copy, retain, photograph, download, alter, delete, share or use it. Note only the minimum necessary to identify the affected system and access path, disconnect from the data, and report the issue immediately. Do not contact the affected person yourself. DailyScore will assess containment, notification and legal obligations through its incident-response process.
Never download, reproduce or send suspected child sexual abuse material. Stop, preserve only non-content technical facts, report through the urgent safety route and follow applicable reporting law.
6. What to report
We welcome reproducible vulnerabilities that could materially affect confidentiality, integrity, availability or safety, including:
- authentication or authorization bypass;
- access to another account, private group, file or database row;
- account takeover, session/token failure or insecure sensitive action;
- server-side code execution, injection or request forgery;
- exploitable cross-site scripting or cross-site request forgery;
- exposure of production secrets or private storage;
- privilege escalation or administrator-function access;
- a practical row-level-security, object-ownership or account-isolation failure;
- a practical bypass of age, parent, privacy, reporting or friend-only safety controls;
- subscription-entitlement forgery that affects access or financial records;
- an exploitable cryptographic, backup, notification or deletion failure; or
- a vulnerable dependency with a demonstrated effect on an in-scope build.
The following are normally not actionable without a demonstrated security impact:
- a scanner report with no reproduction or product-specific analysis;
- a version string, banner, stack fingerprint or public information;
- a missing header or best-practice setting with no practical exploit;
- clickjacking on a page with no sensitive action;
- self-XSS requiring a user to paste code into their own console;
- logout CSRF with no additional impact;
- email spoofing observations without a DailyScore-controlled domain or exploitable configuration in scope;
- rate-limit suggestions without a meaningful abuse scenario;
- a dependency advisory that does not affect the deployed code path;
- a hypothetical mobile issue that requires a rooted, jailbroken or already compromised device without showing additional DailyScore risk;
- an issue already reported and being addressed; or
- spam, support, eligibility, billing or account-recovery problems without a security vulnerability.
We may still use a non-qualifying report to improve the product, but it may be closed without security treatment or recognition.
7. How to report
Send reports to info@thedailyscore.app with the subject Security report. Do not include another person's personal data, passwords or secrets in the report. If a finding is too sensitive for ordinary email, say so in a first message without the details, and we will arrange a safer way to share it.
Include:
- the affected asset, app version/build and environment;
- vulnerability type and expected security impact;
- clear reproduction steps, including your test-account identifier if needed;
- the minimum proof needed to validate the result;
- relevant request identifiers, timestamps and redacted logs;
- whether you encountered data, credentials or evidence of active abuse;
- actions you already took and whether any test data remains;
- suggested mitigation, if known;
- whether you plan to disclose the issue and your proposed timeline; and
- your preferred contact and whether you want public credit.
Do not send live access tokens, passwords, service-role keys, private user data or dangerous working exploit code through ordinary email. Describe what you have and wait for secure-transfer instructions. Do not place vulnerability details in app-store reviews, public issues, social media or general support.
8. What to expect from DailyScore
For a complete report, DailyScore intends to:
- acknowledge receipt within five business days;
- assign a private reference and confirm the communication channel;
- perform initial triage within ten business days, where reasonably possible;
- prioritize by realistic impact, exploitability, affected people, data sensitivity, active abuse and availability of containment;
- communicate material status changes and request coordinated retesting where useful;
- remediate or mitigate in a risk-prioritized manner; and
- tell you when the issue is resolved or closed, subject to security, privacy and legal limits.
These are service targets, not guaranteed resolution deadlines. Complex issues, third-party dependencies, legal duties and emergency response can change the timeline. A report that reveals active exploitation or personal-data exposure will be escalated immediately to the incident-response process.
We do not require a reporter to sign a nondisclosure agreement merely to submit a good-faith report. We may request reasonable confidentiality during the coordination period. We will not ask you to delete evidence before our response owner confirms that necessary evidence has been preserved securely.
9. Authorization and legal safe harbour
If you make a good-faith effort to comply with the approved and published version of this policy, DailyScore:
- considers your in-scope research authorized by DailyScore;
- will not initiate or support legal action against you for accidental, good-faith violations arising solely from that compliant research;
- will not bring a copyright-circumvention claim for bypassing a control only to the minimum extent necessary to investigate the in-scope vulnerability;
- will not bring a claim under DailyScore's Terms merely because the compliant research tested an in-scope system; and
- if a third party brings an action, may state that your reported activity complied with this policy, where truthful and legally permitted.
This authorization comes only from DailyScore and only for systems it owns or is legally able to authorize. It cannot bind a provider, app store, user, law-enforcement agency, prosecutor or regulator. It does not cover out-of-scope systems, intentional harm, extortion, privacy violations, data use or disclosure, disruption, persistence, social engineering, physical intrusion, unrelated unlawful conduct or activity after we ask you to stop for a credible safety reason.
If you are unsure whether a method or asset is authorized, ask and obtain a written answer before testing. DailyScore will interpret reasonable ambiguity in the published policy in favor of a researcher who acted carefully, stopped on harm and reported promptly.
10. Coordinated disclosure
Please keep the vulnerability and non-public remediation information confidential while we investigate and address it. Our default coordination target is 90 calendar days after receipt of a complete, reproducible report. This is not a guaranteed fix date. We may agree to earlier disclosure after a fix or mitigation, or ask for a specific extension when remediation is complex and users remain protected.
If there is active exploitation or imminent risk, we may issue a warning or mitigation sooner. Before publishing, coordinate the date and content with us so secrets, personal data, exploit instructions that create unreasonable risk, and details of unpatched third-party systems are removed. We will not use coordination merely to suppress accurate research indefinitely.
11. Recognition and rewards
This is not a bug-bounty programme. DailyScore does not promise payment, merchandise, employment, expenses or another reward. A later reward programme will apply only under its own written scope and terms and will not operate retroactively unless it expressly says so.
With your written permission, we may credit a helpful reporter after the issue is safely resolved. We may withhold public credit for reports involving harmful conduct, unresolved identity concerns, legal restrictions or a reporter who does not want recognition.
12. Third-party and open-source issues
If the issue is entirely within a third-party service, library or platform, report it through that provider's policy. Do not test that provider on DailyScore's authority. If the third-party issue creates a specific DailyScore risk, also send us a minimal report so we can mitigate exposure and coordinate with the provider.
Do not publicly expose a DailyScore secret in a dependency or source-code issue tracker. For an open-source issue, follow the project's private security- advisory process where one exists.
13. Researcher privacy
We use report information to validate, investigate, remediate, communicate, prevent abuse, protect users and comply with law. We may share it with limited DailyScore personnel, affected service providers, professional advisers, coordinators such as a national CERT, app stores, insurers, regulators or authorities when necessary and lawful.
You may report without requesting public credit. Anonymous reports are accepted, but we may be unable to clarify, validate or recognize them. Do not include personal information that is not needed. Security-case records are protected and retained under the approved security and legal-retention rules, including longer preservation for an active incident or legal obligation.
14. Security incidents and account problems
This policy is for product vulnerabilities. If you believe your own account was taken over, a device was lost, or a password or one-time code was exposed, use the account-security support route immediately and do not test the account further. DailyScore is not an emergency service.
A vulnerability report can reveal a security incident. DailyScore may then contain the issue, preserve logs, suspend a feature, notify providers, people or authorities, and make legally required reports without waiting for the normal coordination timeline.
15. Changes
We may update this policy as assets, contacts, risks, law and response capacity change. The published version will show the effective date and exact scope. Removing an asset from scope does not retroactively withdraw authorization for good-faith research performed while it was clearly in scope.
This contact and policy are also listed in https://thedailyscore.app/.well-known/security.txt. Historical approved policy versions and change summaries will be retained in the legal- document release record.