Legal 02
Privacy Policy
Contents (25 sections)
- 2.1 Our commitment
- 2.2 Information you provide
- 2.3 Research and AI information
- 2.4 Technical and security information
- 2.5 Payment and subscription information
- 2.6 Why information is processed
- 2.7 Ginie processing safeguards
- 2.8 Messages and marketing
- 2.9 Cookies and analytics
- 2.10 Service providers and transfers
- 2.11 Retention and protection
- 2.12 Your choices and rights
- 2.13 Children, changes and contact
- 2.14 Controller, scope and regional applicability
- 2.15 Personal-data inventory by feature
- 2.16 Collection methods and transparency points
- 2.17 Legal grounds and purpose limitation
- 2.18 Recipients and processor control
- 2.19 AI conversation handling and training boundary
- 2.20 International data access and safeguards
- 2.21 Retention by record type
- 2.22 Rights verification and handling
- 2.23 Children and account eligibility
- 2.24 Security incidents and meaningful notice
- 2.25 Changes to privacy practice
2.1 Our commitment
Dear INRGIFT user, this Policy explains how INRGIFT may handle personal information when you browse our website, establish a verified account, save research, contact support or use paid membership features. It is intended to describe processing that is actually conducted; optional or future integrations must not be represented as active until the technical and vendor inventory confirms them. The accountable legal entity is identified in the Corporate Disclosure.
2.2 Information you provide
Depending on the feature, we may process your name, verified email address, mobile number, country, language, account preferences, consent decisions, profile information, support messages and records of account recovery. We do not require you to disclose your Google password or an OTP to support staff. Verification providers may confirm that a contact method has been verified without exposing all underlying credentials to us.
2.3 Research and AI information
When you create watchlists, comparison sets, saved research records, scenario assumptions, alert rules or Ginie conversations, we process the submitted research, instrument identifiers, saved outputs and supporting metadata needed to maintain those features. User-authored theses may reflect personal investment interests. Private research is intended to be protected by account-scoped access controls; team-sharing or publication occurs only through a separately designed and authorised feature.
2.4 Technical and security information
Services may record IP address, approximate network region, browser and device attributes, session identifiers, login events, timestamps, application errors, API rate-limit events and security telemetry. We use these categories to operate the site, prevent abuse, diagnose failures, manage account access and protect data. We should avoid recording plaintext passwords, OTPs, payment-card security codes, unrestricted access tokens or unnecessary private research in application logs.
2.5 Payment and subscription information
If billing is enabled, we may receive order identifiers, plan and renewal information, invoice details, transaction status, tax records, refund records and limited processor references. Authorised processors should handle payment instruments. Processing for chargebacks, fraud review and legal accounting may continue when otherwise required after a subscription ends. The final policy must identify material payment processors or categories actually deployed.
2.6 Why information is processed
Information is used to provide accounts and contracted features; verify identity; authenticate sessions; maintain research; compute user-requested models; enable notifications and saved work; administer subscriptions; respond to grievances; prevent fraud; comply with law; and improve reliability. Where required, the specific legal basis, consent notice or legitimate-use ground should be presented before the corresponding processing begins.
2.7 Ginie processing safeguards
Information sent to Ginie may be transmitted to the configured inference infrastructure and authorised retrieval/calculation services solely to fulfil the requested task. We will not represent private research as eligible for model training or third-party analytics without a separately disclosed lawful basis and any consent required. AI prompt and response logs should be minimised, access-limited and subject to documented retention.
2.8 Messages and marketing
Transactional email, security notices and service messages are distinct from optional promotional email or WhatsApp marketing. Where the law requires opt-in, each promotional channel should have an independent, unticked consent choice. Users must be able to withdraw optional marketing consent through account controls or an appropriate unsubscribe route without losing the core service. Suppression records may be retained to respect an opt-out.
2.9 Cookies and analytics
Essential cookies support account sessions, security and saved preferences where necessary. Optional analytics, advertising or similar technologies are subject to required notice and choice before they load. Users should be able to reopen their choices through Cookie Preferences. The final cookie inventory must list actual purposes, vendors, lifetimes and storage mechanisms; this Policy does not invent their identities.
2.10 Service providers and transfers
Information may be shared with tightly scoped hosting, database, authentication, communication, payment, support and security providers for specific purposes. We should maintain written contracts and appropriate access protections. Hosting regions, international transfers, subprocessors, onward sharing and applicable restrictions must be verified before the product makes country-specific claims. We do not describe a sale of personal data as an ordinary feature of INRGIFT.
2.11 Retention and protection
Retention must be based on an approved schedule distinguishing account records, research content, billing records, security logs, marketing consent and backups. Different laws may impose retention or deletion obligations. We use reasonable access controls, encryption where appropriate, audit trails and response processes, but no digital service can promise absolute protection. Backups and legal holds may affect the timing of complete erasure; those exceptions must be explained truthfully.
2.12 Your choices and rights
Depending on your residence and the rules then in force, you may request information about processing, access, correction, completion, erasure, withdrawal of consent, portability or objection, and grievance redressal. Requests may require identity verification to prevent improper disclosure. Optional consent withdrawal affects future processing but does not necessarily invalidate previously lawful actions or eliminate mandatory records.
2.13 Children, changes and contact
The platform is intended for users 18 or older. We should not knowingly open children’s research accounts. Policy changes will be dated, material changes will receive legally appropriate notice and additional consent will be requested where necessary. To raise a privacy concern or request account data, email support@inrgift.com with the subject Privacy Request; never include a password or OTP.
2.14 Controller, scope and regional applicability
The legal entity operating INRGIFT and the processing roles of its vendors must be verified in the corporate register and production contracts. This notice covers the public site, enrolled accounts, research activity, support, subscriptions and enabled AI features. It does not automatically cover a separate external investing platform after the user independently visits that service. Where INRGIFT targets or monitors individuals in another jurisdiction, an applicable regional supplement will identify additional rights, representatives, legal bases or disclosure requirements.
2.15 Personal-data inventory by feature
Registration can involve name, country, verified email, phone, sign-in provider identifier, security events and communications choices. Research features can involve watchlists, selected instruments, saved hypotheses, note versions, report outputs and AI prompts. Billing can involve a subscription record, order or invoice reference, tax information and payment status without requiring INRGIFT to store complete payment-card credentials. Support can involve complaints, uploaded evidence and call metadata. A maintained system inventory must identify what is truly collected, not merely what the product might support later.
2.16 Collection methods and transparency points
Information may be supplied directly by the user, created when the user uses a tool, received from approved identity or payment providers, or generated as minimal technical security metadata. The registration form, first use of AI, optional communications, checkout and any collection of unusually sensitive material each need a just-in-time explanation appropriate to the data and purpose. A general privacy link alone is not an adequate replacement where the law requires specific notice before a particular collection.
2.17 Legal grounds and purpose limitation
Where GDPR-style legal-basis rules apply, each purpose must be supported by the correct basis: performance of a contract where genuinely necessary, compliance with a legal duty, consent where required, legitimate interests following an appropriate balancing test, or another available basis. The same operation may require different reasoning under India's DPDP regime. Optional advertising or marketing must not be described as essential account processing. New secondary use of saved research, training data or customer profiles needs a separate assessment and disclosure.
2.18 Recipients and processor control
Processor categories may include cloud hosting, authentication, email/SMS delivery, payment processing, fraud/security services, customer support and AI infrastructure. The production inventory should distinguish controllers from processors, identify actual contractual recipients, limit provider permissions, review subprocessors, and prohibit unsupported onward use or cross-account leakage. Private saved research must not be visible to marketing vendors merely because marketing tools are enabled elsewhere on the site.
2.19 AI conversation handling and training boundary
The Platform must explain whether prompt text, retrieval context, source documents, generated responses, safety logs and tool execution records are retained and where. Model training, evaluation on user-owned research, or transfer to a new inference provider is a distinct privacy decision; no unconditional training promise is made until contracts and runtime configuration are verified. Users should be told when an AI request can include their selected private notes.
2.20 International data access and safeguards
The location of a database alone does not establish where all data are processed. Support staff, backups, email gateways, analytics, model APIs and payment processors can create separate international transfers. Relevant jurisdictions may require adequacy arrangements, contractual clauses, risk assessments, local storage or additional notices. Before targeting a market, map recipient country and transfer mechanism for each processing flow, and make no blanket promise of data residency without technical evidence.
2.21 Retention by record type
A single blanket deletion period is not appropriate for account identity, financial invoices, security telemetry, research snapshots, complaints, optional marketing suppression and backups. Adopt and publish meaningful retention criteria or periods after approving the records schedule. Erase or anonymise eligible data after the relevant lawful purpose ends, subject to legal holds and other requirements. Research exports, routine backups, search indexes and AI logs must be accounted for in the technical deletion plan.
2.22 Rights verification and handling
Applicable rights may include access, explanation, correction, completion, erasure, portability, objection, restriction, withdrawal of consent and grievance escalation. Rights depend on law, purpose, technical capability and justified exceptions. A request should receive a reference, secure identity verification proportionate to the risk, a deadline computed for the applicable law, a reasoned response and a review route. The system must prevent one account from requesting another person's data by substituting an email address.
2.23 Children and account eligibility
INRGIFT presently plans adult-only membership. The 18+ rule should be enforced during registration and reflected in legal text, without implying that a self-declared age automatically proves eligibility. If the product ever permits children in a jurisdiction, age-verification, parental authorisation and applicable restrictions on tracking or profiling must be reassessed before launch. A person reporting an underage account should have a clear, safe contact channel.
2.24 Security incidents and meaningful notice
Security controls should address role-based access, encryption in transit, secrets, staff access, audit logging, incident triage, restoration and provider responsibility. Depending on law, incidents may trigger notifications to individuals and/or regulators and preservation of evidence. Public privacy language should describe commitments accurately and avoid asserting absolute protection or a breach-notification timeline that the organisation has not implemented.
2.25 Changes to privacy practice
This policy carries a version identifier and a last-updated date, and we give notice of material changes. A new recipient, analytics technology, retention rule or AI use may require revised consent or a new legal assessment, not merely a silent text update. We retain the notice presented to each member when consent was collected and use consistent policy wording in registration, checkout, messaging and request screens.