Privacy and data controls

These controls govern T-Guru’s own optional usage tracking. You can change your choice as a guest or while signed in. Guest and account choices are separate; declining this tracking does not prevent use of the reading tools.

Optional tracking starts only after a confirmed choice. No choice, a declined choice, an unresolved account, offline use or an unconfirmed choice keeps it off. T-Guru does not load the Google/Firebase Analytics SDK or Trustpilot review widgets. An ordinary Trustpilot link opens its external site only if you choose it.

• Account and profile: your email, sign-in details and the profile fields you choose to provide support account access and saved preferences. Birth details are used by tools that need them. An optional profile avatar is stored as an account file.
• Reading inputs and results: questions, birth details, photos and other submitted information are used to produce the requested response. Saved text and structured results can contain sensitive personal details, including information about other people.
• Credits and payments: the application keeps credit movements, purchase references, amounts, currency and fulfillment status for delivery, reconciliation and duplicate prevention. Card details are entered through Stripe Checkout.
• Browser storage: sign-in state, recovery references and interface preferences use browser storage or cookies. Optional internal tracking also uses stored consent and session choices, bounded campaign labels and referring-site information.

Provide only information needed for the tool. Do not submit another person’s private information or photo without the right to use it.

• Google AI: reading inputs, including face and palm photos, are transmitted for AI processing. The application does not intentionally store the original face or palm input image bytes as report data. This does not mean the AI provider immediately deletes them. Provider retention and data use depend on its terms and the service configuration.
• Firebase and Google Cloud: support authentication, application data, uploaded account files and hosting.
• Stripe: processes payments. The application receives the payment references and status needed to deliver credits.
• Google Maps: when the local birth-location data is insufficient and the fallback is configured, a location lookup may send a place name or address, or coordinates and a time, to Google Maps for geocoding or time-zone information. This is separate from AI processing.
• Trustpilot: report pages offer an ordinary external review link. Following it takes you to Trustpilot under its own privacy policy; its widget is not loaded by T-Guru.

These services may process information in more than one country. Their policies explain their own practices: Firebase privacy, Google AI terms, Google privacy, Stripe privacy and Trustpilot privacy.

Explicit translations use the text of your own available saved report, up to 12,000 characters. You can start at most three new free translation requests in a rolling 24 hours. Each report and target language has one request: checking it again retrieves the saved result and does not generate it again. Failed or uncertain requests are not automatically generated again. A translation is cached under that report, without replacing its original text or creating a new reading. Archive and permanent deletion remove its cached translations; minimal once-only request guards remain under your account until account cleanup.

Saved reports remain until you permanently delete them or delete your account. There is no automatic 45-day deletion. In your profile, use the report list to load more results and include archived reports.

For recent personalization linked to saved reports, the application uses eligible, active sources from the last seven days. Older, archived, deleted and other accounts’ reports are excluded. Older personalization without a reliable source link is excluded too. This is different from the information you enter in a new request.

Archive retains a report privately, removes its generated personalization caches and revokes its shared link. Restoring it keeps the original date and does not automatically share it again.

Permanent report deletion removes saved content and linked copies. If older personalization cannot be linked to one report, the confirmation asks you to reset that older personalization as well. Other independently saved readings may still contain information you supplied.

Anyone with a shared report link can read the full reading, including names or questions inside it. Removing account fields does not make that text anonymous. Shared pages ask search engines not to index them, but this cannot guarantee removal from search results or someone else’s copies.

Revoking a link or deleting a report stops access through that link after the source check. It cannot recall copies already downloaded or data already sent to a provider. An AI request already in progress cannot be recalled; report lifecycle checks prevent revoked source content from being saved or shared again by a late result.

Account deletion first blocks account use, then runs cleanup of saved reports, staged results, personalization, course progress, tracking data and owned files. Cleanup can remain pending if a step fails and needs retry. Removing the sign-in account alone is not proof that every cleanup step finished.

Minimal, restricted payment, credit, operation and deletion references remain for reconciliation and to prevent duplicate processing or deleted-account data being recreated. These references are pseudonymous, not anonymous. Immediate removal of every historical diagnostic, backup or external copy is not promised.

A reading receipt connects a credit deduction, saved result and any credit return. When a provider outcome is uncertain, it is not automatically requested again. Use the recovery controls in your profile; some cases need a reviewed credit decision. Returning reading credits is separate from refunding a Stripe payment.

Application diagnostics use fixed event codes in place of raw prompts, photos, reading text and error payloads. Saved readings are still account content. Optional usage analytics are separate from the operational records needed to deliver and reconcile a request.

Withdrawing analytics consent stops future optional collection. It cannot recall a request already sent and does not itself erase earlier events. Core sign-in, consent-saving, reading and payment services remain separate from optional tracking.

Use your profile while signed in to review saved details and reports, archive or delete readings, and start account deletion. The profile guide explains the available controls.

Depending on the law that applies, you may have rights to access, correct, erase, restrict or object to processing, receive portable data, withdraw consent where processing relies on it, and complain to a data-protection authority. Account controls do not replace these rights. Withdrawal does not change the lawfulness of earlier processing.