Privacy

Last updated 29 August 2026. GenAiMakers is Australian-built. We collect as little as we can, and we do not sell personal information.

Who we are

GenAiMakers operates genaimakers.com. Contact us at hello@genaimakers.com to ask a question, correct a record, or have your details deleted.

What we collect

• Contact and discovery forms. Name, email, optional organisation, topic, and your message. Used only to reply.
• Trolley (meal planner). First name and email leave the browser if you ask us to send a plan, start a 14-day trial, or opt in to a Sunday re-plan. Age, weight, allergies, pantry contents, household profiles and health details stay on your device and are not stored by us. Entitlement (free / trial / Pro) is stored on the server against email. We do not collect a card number here until Stripe Checkout is enabled.
• House & Land AI. The borrowing form posts income, expenses, deposit and loan term to our server to calculate an indicative estimate from published CDR rates and the RBA cash rate. Lender, corridor and site lookups call our APIs; we do not keep them as credit records. When Domain, Geoscape, Vicmap or PTV keys are configured, those providers receive the search or coordinate you submitted. Domain listings are not stored. OpenStreetMap and ABS requests use public endpoints. Output is general information, not financial, credit, tax or legal advice. If you send an enquiry we store name, email, phone if provided, and your message.
• Plan-to-Estimate AI. Plan pages are rasterised in your browser and posted to our server so a vision model can take off quantities. We do not keep the plan images as files. We log the estimate id, project name, optional email, floor area and total so we can debug and follow up if you asked us to. Follow-up questions reuse the estimate JSON. Figures are indicative, not a quote.
• Sloka Agent. Your request (type, deity, language, mood, and optional intensity / length / metre, occasion and names for a commission) is sent to our server to search public catalogues and, if needed, compose an original sloka, mantra, Vedic-style chant or bhajan. We do not store the prompt as a lasting profile. Optional star ratings and measurement events store only counters (shares, dakshina, commissions, white-label inquiries, premium conversion) — not the verse text. If you sign in, we store email, a session token, optional saved collections, and an API key you issued. The Songs update / extract group on the Sloka Agent page (create group, members, Extract words, Export) stays on your device only: group name, member list and extracted words in localStorage, and the PDF in IndexedDB. We do not receive that data and it is never sent to Ask or the compose model. Sharing is a file you export yourself. If you instead use the signed-in Group PDFs layer, we store the file and extracted text as a group-private collection (review states, copyright flags, and version notes) — not member personal data beyond the account email. Dakshina, occasion commissions, premium, print orders and white-label inquiries store name, email, amount and the brief needed to fulfil them. Form drafts, favourites and history stay in your browser (localStorage). A service worker may cache the agent page and fonts for faster repeat visits. We do not scrape or keep copyrighted lyrics or audio. Rate-limit tokens stay in your browser. Generated verses are labelled as original creative works, not scripture. Public scripture and basic access stay free. Payments go through Stripe Checkout when a key is configured; otherwise we email a payment link.
• Bhajan Mandali. Group name, roster, principal parse, festival copies, assignments, script preferences and the write queue stay on your device (IndexedDB, with a localStorage backup). Optional sync to our host uses an invite code so another device can join; we store that snapshot to fulfil sync, not as a marketing profile. Source PDFs and Word files stay on the device. Invite links carry only the code. A service worker caches the app shell, bundled fonts and libraries so the whole agent — not only reading — works offline. Roman / English is generated on the device from native lyrics; a JSON backup is the canonical copy if the device is lost. This is a separate product from Sloka Agent and from Songs update / extract on the Sloka page.
• Server logs. Standard hosting logs (IP, time, page) for security and uptime. We do not run advertising pixels.

Legal bases and email

Where we send marketing or a meal-plan email, we use double opt-in and a one-click unsubscribe. Transactional replies to an enquiry you started do not need a separate marketing opt-in.

Sharing

We use Hostinger for hosting, and may use Groq to draft recipe methods and plan edits in Trolley, and to compose original slokas, mantras, Vedic-style chants and bhajans when public catalogues have no suitable listing. Nutrient figures are never taken from the model — they are computed from the food table. Sloka search returns links and metadata only. We do not sell lists. We disclose information if the law requires it.

How long we keep it

Enquiries and planner emails are kept only as long as needed to provide the service and meet record-keeping duties, then deleted on request or in routine cleanup.

Your rights

You can ask for access, correction or deletion under the Australian Privacy Principles. Email hello@genaimakers.com. Do not send sensitive health data to that inbox unless we have asked for it in a signed engagement.