Identity is stored as a hash
Sign-in is through Google. The raw Google account id never leaves the server. It is converted to a salted, one-way hash, and only that hash is attached to your interactions. We do not store a raw personal identifier for correlation.
Where answers are produced
SAP-grounded questions and any screen you upload are answered on Sharan AI's own infrastructure, never sent to an outside model provider. General, non-SAP questions may be answered by an external model.
What is stored, and why
To provide the service and handle your feedback, your questions, the answers produced, and any feedback you submit are stored on Sharan AI's infrastructure and linked only to the hashed identity described above. Uploaded images are referenced internally and are not forwarded to an outside provider.
How the product improves
Improvements are built from public SAP knowledge sources and reviewed by experts before release. To find where coverage is weakest, we analyse in aggregate which SAP topics and kinds of problem are being asked about. This uses fixed categories and public SAP object names, not your wording. Category counts are only used when shared by several separate users. Timing signals, such as an approaching go-live, are reduced to a broad range and the date itself is not kept.
Feedback
When you rate an answer or submit a correction, that feedback is stored against the interaction. It is used to review and fix answers, and an expert reviews any change before it is released.
Retention and control
Stored interactions are retained on Sharan AI's infrastructure for as long as your account is active, unless you delete them. You can request the data held for your account, or its deletion, at any time — see "Your rights" below.
Sub-processors
The SAP-grounded path uses no third-party sub-processor; it runs on Sharan AI's own infrastructure. A general, non-SAP question may be routed to an external model, which then processes only that minimal request. Payment processing, when a paid plan is used, receives billing details only, never your SAP content.
Your rights, and how to request deletion
You can ask for the data held under your account, and you can have it erased. Both are self-service from your account settings and cover the rights individuals hold under laws such as the GDPR and India's Digital Personal Data Protection Act.
An access request returns the interactions, usage, plan, and key metadata stored for you. A deletion request removes your records across every store — captured interactions, usage history, plan and subscription, trust and session records, rate counters, and any developer keys you own — in a single operation. The deletion is recorded to a tamper-evident audit log that holds only counts and a one-way fingerprint, never the erased content or a raw identifier. Deletion is irreversible. The processing arrangement behind this is described in the Data Processing Agreement.