Who operates this website?
India For Tomorrow is independently operated by its founder in a personal capacity. It is a publishing and research project, not a government service or a confirmed university consortium.
For privacy questions or requests, email support@indiafortomorrow.com. The operator’s full legal identity and any applicable service-address details must be completed by the operator; they have not been invented in this notice.
Information you choose to submit
Depending on the form, you may provide a display name, contact email, approximate location, article title and body, sources, pillar selection or proposed research details. Required fields are identified on the form. Submit only information needed for the enquiry or proposal.
The forms accept plain text. They do not provide a confidential case-management or emergency service. Do not upload or paste sensitive identity, medical, financial or survivor records, or personal details about children.
WordPress submissions and guest drafts
When submissions are enabled, pressing a submission button sends the form fields to this website’s WordPress backend. Successful submissions are stored as lead records with a reference number, form type, date and review status. A receipt is evidence of storage, not programme approval.
A successful guest article submission also creates a native WordPress draft for administrator review. It is not automatically published. The administrator may review the text, sources, display name and consent before deciding whether to publish. Sending a proposal does not establish membership, a partnership or an internship.
Local copies and downloaded research briefs
Some original features also keep a local browser draft or generate a downloadable planning brief. These copies are separate from the WordPress submission. A local file or LOCAL-prefixed record is not a server receipt.
Browser drafts may contain the text entered in the form. Use a shared device with care. You can remove local copies using the available delete control or browser site-data settings. That does not delete records already stored in WordPress, sent email, downloaded files or separate backups.
Why information is used and who can access it
Submission information is used to review contributions, investigate a reported website issue, consider a proposal or respond to an enquiry. The management dashboard restricts lead access to authorised administrators. Administrators can add internal review notes, update status and export records for those purposes.
If email notifications are enabled, the configured recipient receives a reference and an admin review link rather than the full submitted text. A mailer-accepted status does not guarantee inbox delivery. Email you send directly is handled through your and the operator’s email services.
Security checks and Google reCAPTCHA
The plugin checks form validation, consent, a request nonce and short-term submission limits. When Google reCAPTCHA is enabled, the browser contacts Google and the server verifies the response before storing a submission. A missing or failed challenge blocks submission while protection is enabled.
reCAPTCHA is optional and is configured by the administrator. Google receives information used by its verification service, which may include network, browser and interaction information, under Google’s Privacy Policy and Terms of Service. It uses the _GRECAPTCHA cookie when executed. Read Google’s reCAPTCHA information.
For short-term rate limiting, the plugin uses a salted hash derived from the network address rather than saving the raw address in the lead record. Hosting and security services may separately keep network logs. No system can promise absolute security.
Cookies, analytics, advertising and external links
WordPress uses browser cookies for administrator login and related session functions. Local drafts use browser storage. Google reCAPTCHA may add its own cookie and requests when enabled. See the Cookie Policy for the distinction between browser copies and server records.
This two-package build does not activate Google Analytics or AdSense by default. If the administrator adds analytics, advertising, another form provider or embedded services, the policy and relevant visitor controls must be updated to match the actual deployment before those services are used. External websites have their own privacy practices.
Retention, backups and deletion requests
The plugin does not automatically expire lead records. The operator must review them and remove information when it is no longer needed for the stated purpose, subject to any applicable retention requirement. A closed or spam status alone does not delete the record. No fixed deletion deadline or provider retention period is promised here.
Administrators can create private exports and backups containing submission data. Copies must be access-controlled and handled separately from the live database. Removing a live record does not automatically erase older backup files. Deactivating the plugin or changing themes does not delete submissions.
To ask about access, correction or removal, email the contact above with a receipt reference or page URL. Start with minimal information; do not send identity documents without an appropriate agreed route. The operator must assess the request and explain any applicable limits.
Children, publication and other people’s information
Children’s contributions should have appropriate adult or institutional support. The forms should not be used to publish identifying information about a child, survivor or other vulnerable person. Obtain permission before sharing another person’s personal information or work.
Publication is a separate editorial decision. Administrators should remove unnecessary personal details before publishing. Directory entries remain proposed contributors or sources of inspiration unless individual consent confirms membership.
Hosting details and policy updates
The final hosting provider, backup location, log retention and any additional processors depend on the deployment selected by the operator. Those specific details remain to be confirmed before public launch. This notice does not claim that unknown provider practices have been audited.
The administrator must keep this notice accurate when the enabled services or handling practices change. This policy explains the implemented features; it is not a claim of legal certification. Contact IFT with a privacy concern.