Privacy Policy
1. Who we are
iPandith is a product of Ayraa Informatics Inc., registered at 1251 King St W, Toronto, ON, M6K 1G7, Canada.
Ayraa Informatics Inc. is the controller of the personal information described here. Write to contact@ipandith.com and mark your message for the Privacy Officer, Ayraa Informatics Inc., who is the person responsible for personal information under Quebec's Law 25 and our contact for every privacy request in this policy.
2. What we collect
Only what the product stores. Field by field:
| Category | Fields | Where it comes from |
|---|---|---|
| Account | Email address, name, preferred reading language, your sign-in identity reference, and a salted hash of your password if you chose one | You, or Google sign-in via Clerk |
| Workspace | Workspace name, country, plan, token balance, trial dates | You and our billing logic |
| Birth data | Full name, gender, date, time and place of birth, coordinates and time zone, for you and for each person you add to a client file; optional email, phone, notes and family details for clients | You |
| Charts and readings | Computed planetary positions and derived tables; the AI-written reading text and any question you asked | Computed by us; text written by our AI providers |
| Support | Ticket subject and messages | You |
| Sign-in activity | Time of sign-in and sign-out, IP address, browser and operating system, coarse location derived from the IP | Recorded by us at each sign-in |
| AI usage metering | Provider, model, token counts, cost and latency per request (no content) | Recorded by us |
| Consent records | Which policy version you accepted or withdrew, when, from which IP address and browser | Recorded by us when you accept or withdraw |
| Payments | Order, amount, currency, gateway references, card brand and last four digits. Not collected today: online payment is not yet switched on | Payment gateway, once enabled |
Birth data is sensitive by nature: a date, time and place of birth identify a person and support inferences about them. We treat it accordingly and never use it for advertising.
3. Why, and on what legal basis
| Purpose | Data | Basis (GDPR Art. 6 / PIPEDA / Law 25) |
|---|---|---|
| Provide the service you asked for: accounts, charts, readings, client files | Account, workspace, birth data, charts | Performance of our contract with you; your consent to these terms |
| Write readings with AI | Chart data, the name and gender you entered for the person read, reading language, your question | Contract, with the AI Policy disclosing the transfer; you may not use the service without it |
| Keep accounts secure and the service running | Sign-in activity, audit logs | Legitimate interest in security and fraud prevention |
| Bill and keep tax records | Orders and payments | Contract; legal obligation (tax law) |
| Prove consent | Consent records | Legal obligation (accountability) |
| Answer support requests | Support tickets | Contract |
We do not sell personal information, do not use it for advertising, and do not train AI models on it.
4. How it is used, including automated decisions
Readings are generated automatically from your chart by AI models (see the AI Policy). They are guidance for reflection, not decisions about you with legal or similarly significant effects, and no automated decision determines your access, price or eligibility. Plan limits (how many charts or client profiles) are applied by the plan you chose, not by profiling.
5. Who it is shared with
The full list, with what each receives and where, is on the Third-Party Services page. In short: Clerk, Cloudflare, Oracle Cloud Infrastructure, DeepSeek, OpenAI, Geoapify, OpenStreetMap Nominatim, Google Fonts. No one else receives personal information unless the law requires it.
The AI boundary, explicitly: DeepSeek and OpenAI receive the name and gender you entered for the person being read, exactly as typed; that person's birth date, time and place, and the computed chart (planetary positions, houses, nakshatras, dashas); the reading language and the report sections you requested; any question you type for the reading or the report chat. They do not receive your email address and account identifiers, client contact details (email, phone), notes and family details, payment details.
6. Where it goes
Our servers and database run on Oracle Cloud Infrastructure (TODO: confirm - hosting region (OCI region of the ipandith-oci host)). Data leaves that region when it is sent to the providers above: Clerk (United States), Cloudflare (Global edge network; Canadian requests are normally served from Canadian points of presence), Oracle Cloud Infrastructure (TODO: confirm - hosting region (OCI region of the ipandith-oci host)), DeepSeek (China), OpenAI (United States), Geoapify (European Union), OpenStreetMap Nominatim (United Kingdom / European Union), Google Fonts (United States).
7. Transfer safeguards
For users in the EU, UK and Quebec, transfers to providers outside those areas rest on the provider's data-processing terms incorporating the EU Standard Contractual Clauses (and the UK Addendum) and, for Quebec, our assessment of the receiving jurisdiction. The per-vendor status is recorded on the Third-Party Services page; where it reads “TODO: confirm” it has not yet been verified and we say so rather than assert it.
8. How long it is kept
- Account data, charts, readings, client files: until you ask us to delete them. Trial accounts are scheduled for deletion 180 days after the trial ends; automated deletion is not yet switched on, so until it is, deletion happens on request.
- Invoices and payment records: 6 years after the transaction (Canada Revenue Agency requirement). These cannot be deleted on request.
- Consent records: 7 years after your account ends, kept to prove what you agreed to.
- Sign-in and audit logs: 180 days.
When you ask for deletion, your data is removed from our live systems within 30 days of a verified request; encrypted backup copies expire on the backup retention schedule (TODO: confirm - backup retention (OCI Object Storage lifecycle rule for the pg-backup bucket)).
9. Your rights
Wherever you are, you can ask to access, correct, delete or receive a copy of your personal information, object to or restrict a use, and withdraw a consent you gave (withdrawing does not undo processing that already happened). Users in the EU/UK have these rights under the GDPR, in Canada under PIPEDA and, in Quebec, Law 25, in India under the DPDP Act, and in California under the CCPA/CPRA (we do not sell or share personal information, so there is nothing to opt out of).
How: email contact@ipandith.com from the address on your account, or open a support ticket. You can withdraw the consents you gave from Settings at any time. We answer within 30 days, or sooner where the law requires. Account deletion is requested the same way; a self-service button does not exist yet, and we confirm by email once it is done.
10. Children
iPandith is for adults. You must be at least 18 to create an account, and you must not enter another person's birth data without a lawful basis to do so.
11. Security
What we actually do: all traffic is encrypted in transit (TLS through Cloudflare to our server); each workspace's data is isolated at the database level by row-level security; passwords are stored only as salted bcrypt hashes; the application connects to the database with a role that cannot bypass isolation; database backups are encrypted before they leave the server; administrative actions are logged. No system is perfectly secure, and we will tell you and, where required, the regulator, if a breach affects you.
12. Cookies and storage
We set no analytics or advertising cookies. The 9 items we do use are listed on the Cookies & Storage page.
13. Changes
Every version of this policy carries a number and an effective date. A material change is published as a new version, and you are asked to accept it again before continuing to use the service; the previous versions you accepted stay on record.
14. Complaints
Write to us first at contact@ipandith.com. You can also complain to the Office of the Privacy Commissioner of Canada, the Commission d'accès à l'information du Québec, the UK Information Commissioner's Office, the supervisory authority of your EU member state, or India's Data Protection Board.