1. Who we are and what this covers
Challigo is a challenge, habit-progress and community publishing service operated by GANDAM GNANA THIRUMALESH, an individual based in India. Challigo is the operator's business name, not a registered company. In this policy, “we”, “us” and “our” refer to this operator. Our website is challigo.com.
This policy explains personal information handled through the website, accounts, challenges, articles, discussions, public utility apps, moderation and support. It does not govern independent websites you visit through user-posted links. Our Terms of Use explain the rules for using Challigo.
2. Information you provide
- Account and profile: your name, email address, password, verification information, private self-reported age group (13–17 or 18+) and when/how that group was recorded, and time zone; and an optional bio and the identifier of a selected illustrated avatar. Passwords are stored as hashes, not as readable passwords. A pending new email address is also stored when you request a change. New registrations also record the document version and the time you accept the Terms and acknowledge the Privacy Policy. This is not consent to unrelated processing.
- Challenges and progress: challenges you create or join, tasks, schedules, checkpoints, expected outcomes, precautions, reminders, daily task selections, rest/skip days, outcome responses, leave/reset actions, and the dates and time zone used for your journey. Badge-qualification records also retain the challenge and enrollment identifiers, saved challenge name, milestone order, permanent badge ID (for the first 15 milestones), and recording date.
- Content and interactions: articles, images, comments, replies, likes, reports, appeals, moderation feedback and related activity dates. These records can be associated with your account.
- Support: your email address, message, attachments and any information you choose to send when contacting us. Do not send your password, verification codes or password-reset links.
Basic account information is needed to create and secure an account; optional profile fields and publishing are not required. Without the data necessary for a feature, we may be unable to provide that feature. You can browse public articles and challenges without creating an account. The public apps also work without an account.
Free-text entries and images may reveal health, beliefs or other sensitive information even though we do not ask for medical records, government identity documents, financial information or biometrics. Avoid including sensitive details about yourself or other people. Profile avatars are chosen from 20 supplied illustrations; profile-photo uploads are not supported. Choosing an illustration is not a facial-recognition or identity-verification feature.
3. Public apps and calculator inputs
The Sleep Cycle Calculator, Circadian Sunlight Planner, BMI Calculator, Focus Interval Timer, Reaction Time Test and 5-Minute Starter work in your browser. Their current code does not upload tool inputs, objectives, results or local session records to Challigo's API or database. The sleep, sunlight and BMI tools keep your entered times, choices, body measurements and calculated results only in the current page's memory, rather than deliberately saving them in browser storage. That state is lost when the page instance is discarded, although browser history or caching may temporarily restore a page. The 5-Minute Starter likewise keeps its task, optional first step and countdown only in page memory; it has no saved session history.
The Focus Interval Timer and Reaction Time Test also save limited information on your device, as explained under Cookies and browser storage. This is different from uploading it to an account. Ordinary page requests, hosting logs, and signed-in session checks still occur as described in this policy; using a browser-only calculator does not make the whole website a zero-data service. Avoid entering sensitive information in a timer objective, especially on a shared device.
If you enable the focus timer's browser notifications and grant permission, your browser or operating system can display phase-completion messages to people who can see your screen. You can disable these in the timer and revoke permission in browser settings. Timer sounds are generated on your device without microphone access. The timer may also ask the browser to keep the screen awake while running; the sunlight planner does not request GPS access.
4. Information collected when you use the service
Our servers and delivery providers receive connection information such as IP address, browser/user-agent information, requested paths, time, response status and technical errors. Application request logs record request identifiers, methods, paths, status and response times, not request bodies. Hosting and network providers may keep their own logs.
For account security we keep session dates, sign-in/verification status, failed-login and lockout information, and hashed IP and user-agent identifiers. Hashing reduces direct exposure but does not necessarily make these records anonymous. Rate limits also use hashed identifiers derived from connection or account information.
Accounts support up to three active browser/device sessions. When you sign in while another session is active, we may email a single-use sign-in code. The code expires after ten minutes and can be entered on any device; we store a protected digest rather than the readable code in your account. Signed-out, expired and inactive sessions do not count toward the limit. You can revoke sessions in Settings.
Public article views are counted using a short-lived hashed identifier derived from an account ID when signed in, or IP address and user-agent when signed out. This limits repeated views within a day. Aggregate view totals remain associated with the article.
We detect your browser’s time zone during registration to schedule days correctly; you can change your profile time zone. This does not require GPS or precise-location permission. The current application does not request camera, microphone, contacts or precise-location access.
5. Why we use information
- Create accounts, verify email ownership and manage secure sessions.
- Save challenges, participation and progress; calculate calendars, streaks, statistics and graphs; and show in-app reminders and notices.
- Publish content you submit, deliver images, operate discussions and likes, and provide creators with group-level challenge insights.
- Send verification, password-reset, email-change and other necessary account/security emails. These are operational messages, not a marketing subscription.
- Review submissions and reports, prevent abuse, investigate errors, respond to requests, protect rights and comply with applicable law. Active, verified administrators receive pending article, challenge and modified-submission review summaries every 10 minutes, new report alerts without intentional batching, and reminders of unresolved reports every 15 minutes. The 15-minute reminder also includes a count of nondeleted private challenges that are approved or awaiting review, without their titles, authors, tasks or private links. These are processing intervals, not guaranteed delivery times. Server availability, queue retries and email-provider processing can delay messages. These alerts include shared-submission titles and author names in alphabetical order, report types/reasons and protected review links; reporter identity, report free text and private challenge definitions are not copied into those notifications. If your challenge or article is rejected after submission or editing, or your reported content or article thumbnail is removed by moderation, we email you the decision and reason from our contact address. These messages can include the content title, reference and an account editing or moderation-information link, but not the full challenge definition, article body or discussion text. Approval notices remain in the app. Rejection emails are delivered through the existing queue and can be delayed. When your report is accepted or rejected, we email you the decision and the admin's reason. Report follow-up is available at contact@challigo.com.
We use optional Google Analytics for selected public-page measurement, as explained under Optional Google Analytics. The application has no advertising network, cross-site advertising tracker, payment checkout or marketing mailing-list integration. Its progress graphs and article view counts use first-party service data. Google Search Console and Bing Webmaster Tools are used for website ownership and search-performance management; these are distinct from installing a visitor-tracking tag on the site. Email providers also process delivery and security information under their applicable notices. Any later optional additional analytics or advertising requires an updated notice and appropriate choices before collection begins where required.
Automated submission checks inspect challenge definitions (including tasks, checkpoints, outcomes and notes), article text and contact links, comments/replies and profile bios for English-language content, profanity, possible contact details and some harmful instructions. These checks run within Challigo’s backend; text is not sent to a separate language or moderation service. We return field-specific feedback without storing a separate copy of rejected content or recording its text in request logs. Checks can make mistakes and do not reliably determine every short phrase or detect every risk. Admin review and reporting remain available. These content filters are not applied to passwords, identity names or complaint evidence.
We must have a lawful basis for processing where required by the law that applies to you. Providing this notice is not blanket consent to optional uses, a waiver of your rights, or permission for unrelated purposes. Any new optional processing requiring consent needs a separate choice before it begins.
6. Who can see your content and progress
- Public content: published public challenges and approved articles, their bylines (name, avatar and any official badge), and aggregate counts can be viewed publicly and indexed by search engines. Discussion posts and replies are visible to people who have access to that challenge’s discussion.
- Private and link challenges: private challenges are not shared with other users. Authorised administrators can inspect their definitions and reject them for safety or rule violations. Public and link-shared challenges require admin approval before sharing, and edits require a new review. Approved link challenges are accessible to people with a valid invitation link; recipients can forward it. “Unlisted” or link-only access is not a promise of confidentiality.
- Personal progress: individual task logs and outcome responses are not a public profile or a creator-facing participant list. Creators receive group summaries, including participant counts, activity, average progress, completion rates and comment counts. Small groups can sometimes allow others to infer individual activity.
- Badge sharing: earned badges are shown in your signed-in dashboard and journey. Sharing or downloading a badge is optional. The image and caption include the challenge name, even when the challenge is private. We generate the download on request without storing a separate image. We do not automatically post to social platforms. A platform you choose receives the information you send under its own privacy practices; saved images and posts can remain outside Challigo after you remove them here.
- Moderation and operations: authorised administrators can review accounts, submissions, reports and relevant content, including private challenge definitions. The normal moderation interface does not expose individual task histories. Necessary infrastructure access by the operator and service providers is a separate access boundary.
Email addresses and passwords are not included in public author bylines. Illustrated avatars are delivered with the website. Article thumbnail uploads are delivered through public Cloudinary URLs: anyone who obtains the image URL may access the image, even if the page around it is restricted. Do not upload images that need confidential storage. We resize/re-encode uploads and strip embedded metadata during processing, but the visible image itself may still identify you.
Articles and thumbnail changes require admin review before publication in the public article pages. Personal photographs and thumbnails that expose personal information are not allowed. Administrators can remove an unsuitable thumbnail and explain the removal to its author, without approving unpublished text. Review is a safety measure, not a guarantee that every identifying detail will be detected.
8. Optional Google Analytics
We use Google Analytics 4 (measurement ID G-GS9LZPXM2K) to understand visits to selected public pages and improve the service. The Google tag loads only after you select “Accept all”. “Essential only” keeps optional analytics off and does not prevent normal use of Challigo. You can change your choice at any time through Cookie preferences in Settings or the control below, without signing in.
We supply public-page addresses without query strings or fragments, fixed page titles and no referrer value. Google also receives network and technical information needed for measurement, which can include your IP address, browser/device information, language, timestamps and cookie identifiers. We do not deliberately send account names, email addresses, user IDs, passwords, verification/reset tokens, private challenge details, task objectives, form values or report evidence. Account, administration, editing and individual content-detail routes are excluded. Signed-in accounts declaring ages 13–17 or without an age-group declaration are excluded; an anonymous visitor's age is not independently verified by the analytics choice.
Google Analytics can use first-party _ga and _ga_GS9LZPXM2K cookies to recognise visits. Our tag requests a maximum 180-day cookie lifetime without renewing it on each page view; browsers may shorten it. Your allow/decline preference is stored in localStorage as challigo:analytics-choice:v1 and is honoured for 180 days. An expired preference record may remain until overwritten or cleared, but is no longer treated as permission to measure. If browser storage is blocked, your choice can apply only to the current page session. Essential cookies and local app preferences have their separate purposes described above.
Choosing Essential only disables future collection by this tag and attempts to clear its first-party analytics cookies. It does not automatically erase information already received by Google. Google Signals and advertising-personalisation features are disabled in our tag configuration; advertising consent settings remain denied. No advertising or remarketing service is added by this integration.
Google may process analytics information outside India. Its handling is described in Google's privacy policy and how Google uses information from partner sites. Analytics account-level event/report retention and linked-service settings have not been independently verified; cookie expiry does not establish how long Google retains received reports. Contact us about an analytics privacy or deletion request.
9. Service providers and other disclosures
- Resend delivers transactional email and receives recipient addresses, message contents (including codes/links where needed) and delivery information. See Resend’s privacy notice.
Where open or click tracking is enabled for an email, Resend uses a tracking image to record opens and tracking redirects to record link clicks. Events can be associated with the recipient and message and include timestamps, the links clicked and technical information such as IP address and browser/device details. We use these events to understand email engagement and improve our service communications. Privacy protections and automated email scanners can affect the accuracy of these records.
When email event collection is enabled, verified Resend webhooks provide delivery statistics and, where those features are enabled, open/click statistics. Our email analytics records contain provider event/message identifiers, event types and timestamps for up to 30 days. This collection does not retain message bodies, recipient addresses, clicked URLs, IP addresses or browser/device details. Authorised administrators can view aggregate statistics and queue counts. Resend may separately process information as described above.
Open/click tracking is separate from delivery, bounce and failure records and is not necessary to send account or security emails. Website Cookie preferences control Google Analytics, not email tracking. Accepting our Terms or allowing website analytics does not, by itself, provide consent to email tracking; we must obtain any consent required before using it. For questions or requests about email tracking, contact contact@challigo.com.
- Cloudinary stores and delivers processed article images, their asset metadata and image-request information. See Cloudinary’s privacy notice.
- Amazon Web Services (AWS) hosts the frontend and backend and processes application traffic and operational records needed to run and secure the service. MongoDB Atlas stores account, content, progress and operational database records; the selected primary database region is Mumbai, India. Hosting, network and database providers can also produce technical records and backups. See AWS's data privacy information and MongoDB's privacy notice.
- Email support: correspondence sent to contact@challigo.com is received and managed using Google Workspace (Gmail) so we can respond to support, privacy and complaint requests. Do not send passwords, OTPs or unnecessary sensitive documents.
- Search-management services: Google Search Console and Microsoft Bing Webmaster Tools process ownership-verification and search-performance information under Google's privacy policy and Microsoft's privacy statement. A verification record alone does not install visitor analytics.
We may disclose relevant information when required by valid legal process or applicable law, or where legally permitted and necessary to investigate abuse, protect people or defend legal rights. A report may be shared with those reviewing it; do not include unnecessary personal information. We do not deliberately publish a reporter’s email address in the normal reporting interface.
A future change of operator would require an appropriate lawful basis, notice and safeguards for any transfer of personal information; these terms do not grant unrestricted permission to sell personal data.
10. International processing
The operator and the selected Atlas primary database are in India. This does not establish the location of every log, backup or provider subprocessor. AWS, email and image delivery providers may process information in other countries through their infrastructure and subprocessors. Do not assume that all information stays in India. Storage and delivery locations depend on the providers serving a request. Cross-border transfers must comply with applicable legal requirements; this policy does not claim that information stays in one country or that a particular international compliance certification has been obtained.
Visiting the website or accepting the Terms does not itself supply consent or another legal safeguard for an international transfer where the law requires something more.
11. Retention and account deletion
Account and product records generally remain while you use the service. We also need to consider security, unresolved disputes, legal preservation obligations and other participants’ ongoing journeys. There is currently no automatic age-based purge for all content, moderation or audit records. Retention must remain necessary for the relevant purpose or a legal obligation. You can ask about a specific record or request further erasure through the contact below.
- OTPs, password-reset links and email-change proofs stop working at their configured expiry or when consumed or replaced. Expiry is not the same as physical deletion: some proof digests, attempt counters and security timestamps remain in the account/session record until another action removes them. An unverified registration also does not currently have an automatic account-deletion deadline.
- Earned badges and distinct-challenge completion records remain after resetting progress, leaving, or removal of the original challenge, so milestones cannot be duplicated and your earned history is preserved. These records are included in the badges account export and deleted when you delete your account. At rollout, we credit badge-qualifying challenges still supported by saved attempts; previously erased history cannot be reconstructed. A reconciled badge date records when that credit was added. Badge eligibility requires at least 80% of challenge days completed, rounding up; rest and skipped days do not count. This does not change actual progress or full-completion statistics.
- Article-view deduplication records are scheduled to expire after two days; article view totals remain. Rate-limit records expire after their relevant window, and session records expire at their configured expiry. Database expiry cleanup is asynchronous.
- Queued email payloads are encrypted and cleared when sent or expired. Ordinary email payloads are also cleared on terminal failure; failed admin digest, report-decision and content-rejection payloads remain encrypted for operational review until the queue record expires. Queue records are scheduled for removal seven days after creation. Providers may retain their own delivery records under their terms.
- Pending admin digest events remain until handed off to the email queue, including when no eligible admin is available. They contain submission identifiers/titles or report identifiers/types/reasons, without report free text. After handoff, these event and window records are scheduled for deletion after seven days.
- Replacing or removing an article thumbnail queues the old Cloudinary asset for cleanup after the change succeeds. Cleanup may require retries; cached images or copies already saved by others may remain temporarily or outside our control.
- Previously uploaded profile photos are no longer included in app profiles or bylines. Background media maintenance removes the old avatar metadata and queues known uploaded avatar files for deletion; selecting a new illustration also retires the old photo. Provider cleanup can require retries, and earlier cached or downloaded copies may remain. New avatar choices store only a supplied illustration ID linked to your account, not a photo you upload.
What deleting your account currently does: it disables the account, replaces your name and email with deletion markers, clears the stored password hash, bio and avatar, revokes sessions, and deletes your enrollments, daily progress, earned badges, distinct-challenge completion records and notifications. Your likes are removed. Your authored challenges and articles are withdrawn from normal access; article body text and authored comment text are replaced with a removal marker. Images are queued for cleanup, which may require retries.
What it does not immediately erase: a deleted-account record and internal identifiers; authored challenge definitions; article titles and moderation metadata; report/audit history, the saved time zone, agreement version/timestamps and some account/security timestamps; and challenge snapshots already used in other participants’ journeys. Report free text is removed on account deletion, but associated report records remain. Some removed content is retained internally rather than physically deleted. Cached images, provider records, backups and copies made by other people are not instantly erased. Other users’ independent content is not deleted merely because it mentions you.
Leaving a challenge stops that participation but keeps its history; it is not account deletion. Contact us about further erasure or a specific retained item. We must assess the request under applicable law and explain any lawful need to retain information, rather than promise that the account button achieves complete erasure.
Fixed production retention periods for hosting logs, database backups, recovery points, email-provider records and Cloudinary backup/cache copies have not yet been verified. We do not promise a specific backup erasure deadline or that removing an active record immediately removes all backup copies. A restoration must be checked for previously deleted data before restored records are returned to normal use. Contact the Grievance Officer for a record-specific request or retention explanation.
12. Security
The application uses password hashing, expiring sessions and verification proofs, access controls, anti-forgery checks, request limits, upload validation and encrypted queued email payloads. Production authentication requires secure cookies and HTTPS configuration. These measures reduce risk; they do not make all stored data encrypted, end-to-end encrypted or immune from compromise.
Use a unique password, secure your email account, sign out on shared devices, and report suspected unauthorised access. Where required, we must notify affected people and authorities about a personal-data breach in accordance with applicable law.
13. Your choices and privacy requests
In Settings you can update your profile, time zone, password and email, choose an illustrated avatar, revoke sessions and request account deletion. A protected account-export API provides supported records by resource and page; Settings currently has no export download control. Exports are not a guarantee that every operational record is included. Administrator accounts require operator assistance for deletion.
You can also email us to request access, correction or erasure, ask about processing or recipients, or raise an objection or restriction request where applicable law provides it. Where processing depends on consent, you may withdraw it; this does not undo prior lawful processing and may prevent us from providing the affected feature. You do not need an active account to raise a privacy complaint.
We may need proportionate information to verify a request, not your password or verification codes. We must respond within the time required by applicable law and explain refusals or necessary extensions. Rights depend on the applicable jurisdiction and provisions actually in force; this policy does not claim that every DPDP, GDPR or other statutory remedy is already available everywhere. It does not limit a right to approach a competent regulator, grievance body or court.
14. Children and age eligibility
Challigo is intended for users aged 13 and above, not children under 13. We do not ask for a full date of birth at signup. This product age rule does not override data-protection law: people under 18 may still be children under the law that applies to them. The current app does not provide verified parental consent, and the signup agreement is not a substitute for it. Where that verification is legally required, affected account features must not be used until the requirement is met.
We use your private age group for age-appropriate access controls, not a public age badge or advertising profile. A selection is self-reported, not proof of age or parental consent. Existing accounts without a declaration remain unknown until their owner chooses a group in Settings; we do not guess their ages. Age-group fields are removed on account deletion. Adult-rated challenges currently remain unpublished and unavailable for participation for everyone, including accounts selecting 18+.
When registering in the 13–17 age group, you must declare that a parent or legal guardian has reviewed the Terms and this policy and approved your use of Challigo. We record the time of that declaration with the registration agreement version. This is your statement; it does not verify the parent’s identity, age or consent. We do not collect a parent’s phone number, email address or identity documents through this signup flow. Existing accounts are not retrospectively given a declaration they did not make. Content review and keeping a submission unpublished do not replace any parental-consent requirement under applicable law.
We handle personal information under this policy and applicable law. Challenges involving dangerous activities, bullying, harassment, exploitation, illegal activities or harm to others are prohibited. If content puts a child at risk, or you believe information about a child was collected inappropriately, use Report or contact contact@challigo.com so the issue can be reviewed and addressed. Do not attach illegal images or unnecessary sensitive information to a complaint.
15. Contact, complaints and policy changes
ChalligoOperator: GANDAM GNANA THIRUMALESHOwner and Grievance Officer: GANDAM GNANA THIRUMALESHchalligo.comIndiacontact@challigo.comFor privacy questions or complaints, include “Privacy” in the subject and describe the affected account or content and the action requested. For a content or copyright complaint, include the exact page URL and enough information to identify the issue. Do not send unnecessary identity documents or sensitive attachments. GANDAM GNANA THIRUMALESH, Owner and Grievance Officer, handles user complaints, content reports, privacy and account-deletion requests, and security incidents through the contact above. You do not need an account to email a complaint. Please identify urgent safety or security concerns clearly; routine admin email summaries do not replace grievance handling. Applicable statutory response deadlines and escalation rights are not replaced by this policy.
The effective date appears above. Material changes need appropriate advance notice through the service or email where required, and a separate choice where new processing legally requires consent. Changing a page cannot retroactively authorise an undisclosed use of personal information.