Privacy Policy

Version: 2026-11-07 Effective date: 2026-11-07

This policy explains what personal data CoGho ("we", "us") collects, what we use it for, who we share it with, how long we keep it, and the rights you have. It is written for everyone who uses CoGho, wherever you are; the region-specific sections in Section 15 add what your local law requires.

In short. We collect what you give us (your account details, your plans, your chats, the finance and food data and files you choose to add) and a small amount of technical data needed to run and protect the service. We use it to provide CoGho to you and to make its AI assistants useful. AI features send your content to an AI model provider to generate replies and to read documents you ask us to import. We do not sell your personal data, show ads, or use advertising trackers. You can view and correct your data, download a copy, and delete your account from inside the app.

1. Who we are and how to contact us

The controller of your personal data (in India, the Data Fiduciary) depends on where you use CoGho. If you are in India it is ABRAM AI SOLUTIONS PRIVATE LIMITED; everywhere else it is ABRAM AI SOLUTIONS PTY LTD. These are separate companies.

Company (outside India) ABRAM AI SOLUTIONS PTY LTD, an Australian proprietary company limited by shares
Registered address 79B Kleins Road, Northmead NSW 2152, Australia
Registration number ACN 698 855 499 · ABN 27 698 855 499
Company (India) ABRAM AI SOLUTIONS PRIVATE LIMITED, an Indian private limited company · CIN U62013KL2026PTC105543
Registered address (India) 4/300A, Ponnarambil House, Mecherippadi West, Venkitangu, Thrissur, Chavakkad, Kerala 680510, Venkitangu SO KE, India
Privacy contact hello@abramaisolutions.com
Data Protection Officer We have not appointed a DPO; contact the privacy contact above
EU representative (GDPR Art. 27) [EU REPRESENTATIVE NAME AND ADDRESS — or "not required: we are established in the EU"]
UK representative (UK GDPR Art. 27) [UK REPRESENTATIVE NAME AND ADDRESS — or "not required"]
Grievance Officer (India) Amalnath Ponnarambil Asokan, hello@abramaisolutions.com, 79B Kleins Road, Northmead NSW 2152, Australia
Brazil data protection officer (encarregado) Amalnath Ponnarambil Asokan, hello@abramaisolutions.com (the same person as the Grievance Officer above)

You can send any privacy question, request or complaint to the privacy contact above.

2. Scope

This policy covers the CoGho web application and the notifications it sends (together, the "Service"). CoGho is for people aged 18 and over (Section 13).

3. The personal data we collect, and why

The table lists each category of data, where it comes from, what we use it for, and (for people in the EEA/UK) the legal basis. Providing most of this data is your choice: features you don't use collect nothing. The data marked required is needed to create and run an account.

Category What it includes Where it comes from What we use it for Legal basis (GDPR / UK GDPR)
Account and identity (required) Name, email address and/or mobile number, a hashed password (we never store your password itself), sign-in method, account id, last sign-in time, whether the account is verified You Creating and securing your account, signing you in, contacting you about the Service Contract (Art. 6(1)(b))
Profile and preferences Relationship status, job, hobbies, time zone, preferred language, base currency (the optional profile fields are yours to fill in or leave blank) You (time zone is detected from your browser) Personalising the assistants, showing times in your time zone and replies in your language, choosing the payment provider Contract; legitimate interests in personalisation you would expect (Art. 6(1)(f))
Chats and AI content What you type or say to the assistants (task, goals, meal prep, recipes, grocery, finance, onboarding), the assistants' replies, summaries of past conversations You; the AI model Producing replies and actions, keeping context between messages Contract
AI-derived "memory" Short facts the AI notes about you from your conversations (for example preferences, recurring routines, schedule anchors) Derived from your chats Making future replies more relevant. You can see, edit and delete every fact in the Memory tab. See Section 4 Legitimate interests (Art. 6(1)(f)); you can object
Schedule and planning Tasks, goals, reminders (titles, dates, times, notes, repeat rules), schedule anchors You; the assistants on your behalf Running the schedule, goals and reminders features and sending the notifications you set Contract
Connected calendar (Google, Outlook or Apple) Only if you connect one: your account email (Google, Microsoft or Apple ID), the access and refresh tokens Google or Microsoft issues, or, for Apple, the app-specific password you give us (all stored encrypted), which calendars you chose and your sync settings. For the dates you are working on, the title, time and busy/free status of events in those calendars (read when needed, not stored). Calendars that are already on your iPhone are read on the phone and are not sent to us. If you turn on adding tasks to your calendar: the tasks and reminders you confirm, created as events in your calendar You, through Google's or Microsoft's consent screen, or by entering an Apple app-specific password Showing your events in your schedule, avoiding double-booking when the assistant plans your day, and (only if you enable it) adding your tasks and reminders to your calendar. See Section 4 Consent (Art. 6(1)(a)); you can disconnect at any time
Food and living Recipes, meal plans, grocery lists, and dietary preferences you mention You; the assistants on your behalf Meal prep, recipe and grocery features Contract. Dietary preferences can reveal health or religion: see below
Financial information you enter Income, expenses, transactions, savings buckets, assets, liabilities, credit cards (issuer, last four digits, limit, statement day, fees and reward settings) and the transactions on each card, What-If scenarios, forecast settings You Showing your cashflow, wealth, credit cards, forecasts and scenarios, and answering your finance questions. We do not connect to your bank and never receive your bank or card credentials, and we never ask for a full card number Contract
Statements and recipes you import When you choose to import: the file or web link you give us - a bank or credit-card statement (PDF, photo, spreadsheet or document) or a recipe (file, photo or link). From a statement we keep only what you review and confirm: its transactions and a header (period, opening and closing balances, minimum due, due date, reward points) You Reading the document for you so you don't have to type it in, checking that it adds up, and flagging entries you already have. The file itself is read in memory and discarded; we do not store it Contract
Documents Files you upload to the Document Store, their names, categories, size and type You Storing and returning your files. We do not read or analyse the contents of files in the Document Store (importing a statement or recipe is separate: see the previous row) Contract
Family / household Household membership and role, invite codes, the sharing permissions you grant, and the shared grocery and finance lists You and other household members Family plan features. See Section 6 for what other members can see Contract
Subscription and payment Plan, status, and the customer and subscription ids our payment provider issues. Card and bank details are entered on the payment provider's page or widget and are not stored by us You; the payment provider Billing, cancelling, and applying your plan Contract; legal obligation for tax and accounting records (Art. 6(1)(c))
Devices and notifications A push subscription per browser you enable (an endpoint and encryption keys), a device id, and the notifications scheduled for you Your browser Delivering the reminders and alerts you switch on Consent (you enable them and can turn them off in Profile)
Security and technical data Your IP address, sign-in and refresh tokens, timestamps, and request logs (which do not contain the content of your messages) Your device Keeping the Service secure, limiting abusive request rates, diagnosing faults Legitimate interests (Art. 6(1)(f))
Usage and cost data Counts of AI tokens used, per feature per day, and an estimated cost; and, for each calendar month, how many AI chat messages, statement reads and recipe imports you have used, with your plan and its limits at that time. These are numbers only and contain no message content, statement data or recipe content Generated by the Service Operating the Service, controlling costs, enforcing the monthly allowances of your plan, and showing you what you have used on the Subscription page Legitimate interests; contract
Consent records Which version of the Terms and this policy you accepted, and when Generated when you accept Proving what you agreed to Legal obligation / legitimate interests (Art. 6(1)(c), (f))
Your messages to us Anything you send to our privacy or support contact You Answering you and keeping a record of your request Legitimate interests; legal obligation

Sensitive data. We don't ask for special categories of personal data. But what you type into the assistants or the food features can reveal health (for example an allergy, diabetes or a medical diet) or religion (for example halal or kosher preferences), and your financial data is sensitive in its own right. If you choose to give us such information, you consent to us processing it to provide the feature you are using (GDPR Art. 9(2)(a); DPDP Act s.6; LGPD Art. 11). You can withdraw that consent by deleting the information or your account. Please don't enter data about other people that you have no right to share.

4. How the AI features use your data

Google Calendar and Google user data

Connecting a calendar is optional. This section describes what we do with data we receive from Google when you do.

Outlook, Apple and iPhone calendars

Connecting any calendar is optional, and the rules above (use only for the calendar features, events not stored, no sale, no advertising, no use to train AI models) apply to every provider. What differs is how you connect and what we receive:

If the GDPR or UK GDPR applies to you, we rely on:

6. Who we share your data with

We do not sell your personal data, and we do not share it with anyone for advertising or cross-context behavioural advertising. We share it only as follows.

Service providers (processors) process data on our behalf and only on our instructions:

Provider What it does for us Data involved Location
Microsoft Azure Hosting, database and file storage, message queue for notifications, cache used for rate limiting, secret storage All data described above, stored in our Azure environment Australia East (Sydney, New South Wales, Australia)
Microsoft Azure OpenAI / Azure AI Foundry Generating the AI assistants' replies and the nightly memory facts, and picking the transactions and recipes out of documents you import The message and context described in Section 4, and the text of documents you import Our Azure AI Foundry resource is in Australia East, but its models are deployed as Global Standard deployments, so your prompts and the models' replies may be processed in any region Microsoft uses for global deployments, not only Australia East
Google (Google Calendar API) Only if you connect a Google calendar: signing you in to your calendar, reading its events and, if you enable it, creating events in it Your Google account email, the calendar data described in Google Calendar and Google user data, and the tasks you choose to add Global
Microsoft (Microsoft Graph, Outlook calendars) Only if you connect an Outlook or Microsoft 365 calendar: signing you in to your calendar, reading its events and, if you enable it, creating events in it Your Microsoft account email, the calendar data described in Outlook, Apple and iPhone calendars, and the tasks you choose to add Global
Apple (iCloud Calendar, CalDAV) Only if you connect an Apple calendar: reading its events and, if you enable it, creating events in it Your Apple ID, your app-specific password, the calendar data described in Outlook, Apple and iPhone calendars, and the tasks you choose to add Global
Microsoft Azure Computer Vision Reading the text in scanned statements, photos and images you import (OCR) The uploaded file's pages or image, for as long as it takes to read it Australia East (Sydney, New South Wales, Australia)
Stripe (most countries) / Razorpay (India) Taking payment and managing subscriptions Name, email address, our account id, plan; card or bank details go straight to the provider [STRIPE / RAZORPAY LOCATIONS]
Browser push services (operated by Google, Mozilla, Apple or Microsoft, depending on your browser) Delivering notifications you enabled The notification text, encrypted end to end so the push service cannot read it, plus your push endpoint Global
[SUPPORT / EMAIL PROVIDER, if any] [Purpose] [Data] [Location]

Other members of your household. If you use the Family plan: everyone in the household can see and edit the shared grocery list, and the shared finance lists if your household uses them. The member who is the household's "driver" makes their recipes and meal plan visible (read-only) to the others. Schedule and finance tabs are private unless you individually grant another member read-only access, which you can revoke. Your Wealth tab, credit cards and statement headers are never shared with the household. The household owner can see who the members are.

Our staff. A small number of authorised people can use internal administration tools that show account details (name, email address, sign-up date, subscription plan) and usage and cost figures, so we can support you and run the Service. They don't routinely read your chats, finance data or documents [CONFIRM: describe the access controls and logging that enforce this].

Legal and safety. We disclose data where the law requires it, to respond to valid legal process, or to protect the rights, safety and security of our users and the Service.

Business changes. If we merge with or are acquired by another organisation, your data may transfer to it, and we will tell you first and honour this policy unless you're told otherwise and given a choice.

7. International transfers

We host the Service in Australia East (Sydney, New South Wales, Australia). Our providers may process data in other countries, including countries with different data-protection laws from yours. Where the law requires a safeguard for such a transfer we rely on one, for example the European Commission's Standard Contractual Clauses, the UK International Data Transfer Agreement or UK Addendum, an adequacy decision (including the EU–US Data Privacy Framework for certified providers), or, for other countries, the transfer mechanisms of the DPDP Act (s.16), LGPD (Art. 33), the Australian Privacy Principles (APP 8) and the UAE PDPL. You can ask us for details of the safeguard used through the contact in Section 1.

8. How long we keep your data

Data How long
Account, profile, tasks, goals, reminders, food, finance data, documents, memory facts, household data Until you delete it or delete your account
Files and links you import (statements, recipes) Read in memory while the import runs, then discarded; never stored. What you confirm is kept like your other finance and food data
Chat history Recent turns are kept in the chat store; older turns are moved to a private archive and summarised. Both are kept until you delete your account. "Clear chat" hides history from your view and from the assistant; it does not erase it. To have your chat history erased, delete your account or contact us [CONFIRM: set and state a maximum retention period for archived chats]
Calendar connection (tokens or app-specific password, account email, settings) Until you disconnect the calendar or delete your account. Calendar events themselves are never stored
Push subscriptions and scheduled notifications Until you turn notifications off, you delete the reminder, or you delete your account
Usage and cost data (including the monthly counts that drive your plan allowances) Until you delete your account. The live counters held in our cache for speed expire after the month or day they cover and can be rebuilt from the stored monthly counts
Consent records Until you delete your account
Sign-in tokens Access tokens: 60 minutes. Refresh tokens: up to 30 days, or until you sign out
IP-based rate-limit counters Minutes to at most one hour, then they expire automatically
Service logs [CONFIRM: retention period in the logging service]. They do not contain the content of your messages
Payment records Held by our payment provider for as long as tax and accounting law requires (commonly 7–10 years), independently of your account
Backups and deleted-data recovery [CONFIRM: any backup, soft-delete or geo-replication that keeps deleted data for a period, and how long]

When you delete your account we erase your data from the systems above and cancel any subscription with our payment provider, except for what we must keep by law. Data held only in backups or replicas is removed when those are overwritten.

9. Your rights and how to use them

Self-service in the app. You don't need to ask us to:

Or contact us at the privacy contact in Section 1. We may need to check it's really you before acting on a request (we will usually ask you to write from your account email address). We answer within the time your law requires, and in any case within one month (some regions set a shorter or a longer period: see Section 15). We don't charge a fee unless a request is clearly unfounded or excessive.

Your rights, in general. Depending on where you live you have the right to: be told what we do with your data (this policy); access it; have it corrected; have it erased; restrict how we use it; object to our use of it; receive it in a portable form (portability); withdraw consent at any time; not be subject to a solely automated decision with significant effects; and complain to a regulator. Section 15 lists the rights and regulators for each region. We won't treat you worse for using your rights.

10. How we protect your data

No system is perfectly secure. If a personal-data breach is likely to put you at risk we will tell you and the relevant regulators as the law requires (for example within 72 hours to a GDPR supervisory authority, where required).

11. Cookies, local storage and similar technologies

CoGho sets one cookie on the website, and it is strictly necessary: it keeps you signed in. We have no analytics, advertising or tracking technologies, and we set no third-party cookies. On top of that, the website keeps a few things in your browser's local storage, and only for things the Service can't work without:

Item Type Purpose How long
cogho_refresh (an httpOnly, secure cookie set by our API; scripts on the page cannot read it, and the browser sends it only to our sign-in address) Cookie Keeping you signed in, by letting the website get a new short-lived access token Up to 30 days, or until you sign out
Your short-lived access token, a marker that you are signed in, and your user id Local storage Keeping you signed in Until you sign out
A device id Local storage Recognising the browser you enabled notifications on Until you clear your browser data
Your language, avatar colour and which calendar sections you have opened or hidden Local storage Remembering your display choices Until you clear your browser data
A calendar event you were adding while you connected a calendar Session storage Finishing that action when you return Until you close the tab
Copies of the screens you looked at recently Local storage Showing them when you are offline Up to a week, and removed when you sign out
Your best score and sound setting in the offline game Local storage Remembering them Until you clear your browser data
A service worker and push subscription (only if you enable notifications) Browser Receiving notifications when the app isn't open Until you turn notifications off

Because these are strictly necessary, they don't need a consent banner. If you pay by card in India, the Razorpay checkout script is loaded on the payment step and may set its own cookies under Razorpay's policy. We don't load any font, script or image from advertising or analytics networks. The mobile apps do not use cookies; they keep your sign-in in your phone's secure storage.

12. Voice input

The microphone button uses your browser's built-in speech recognition. Depending on your browser, the audio is processed by the browser's vendor under its own privacy policy (for example, Chrome sends audio to Google). We receive only the resulting text, never the audio. Your browser asks for permission before using the microphone.

13. Children

CoGho is for people aged 18 or over. We don't knowingly collect personal data from anyone under 18. If you think a child has given us data, contact us and we will delete it.

The Service can create links that open WhatsApp, Telegram or SMS so you can share a grocery list. That is your choice; once you leave for those apps their own policies apply.

15. Information for specific regions

15.1 European Economic Area and United Kingdom (GDPR / UK GDPR)

15.2 India (Digital Personal Data Protection Act, 2023 and IT Rules)

15.3 United States, including California (CCPA / CPRA)

15.4 Brazil (LGPD)

15.5 Australia (Privacy Act 1988 and the Australian Privacy Principles)

15.6 United Arab Emirates (Federal Decree-Law No. 45 of 2021, "PDPL")

16. Changes to this policy

We may update this policy as the Service or the law changes. Each version has a date at the top. If a change is material, we'll notify you in the app and ask you to accept the new version before you continue; the previous versions and the record of what you accepted are kept.

17. Contact and complaints

Questions, requests or complaints about your personal data: hello@abramaisolutions.com, or by post to 79B Kleins Road, Northmead NSW 2152, Australia. You always have the right to complain to your data-protection regulator; details are in Section 15.