Privacy Notice

How Hubmatch.Tech handles your information, and your class's.

The short version

Your lesson plans stay in your browser. We hold your account, what you bought, and how much the AI was used — not what you wrote. When you press an AI button, the text of that one field is sent to be processed and is not kept. Learner Context is never sent at all.

Who is responsible

Hubmatch.Tech operates this service at https://hubmatch.tech.

For any question about your data, or to exercise the rights below, write to hello@hubmatch.techButuan City, Philippines.

What stays on your device

These never reach our server at all. They are held by your browser, on your own device, and they are lost if you clear your browser data — so export anything you need to keep.

What we store

Everything our database holds, why, and for how long.

Your Google account identifier, email address, the display name Google supplies, and when you last signed in.

Why: To recognise your account when you sign in and to attach your AI plan credits to it.

Kept: Kept while your account exists. Deleted on request.

A record of every AI plan credit added to or spent from your account, and why.

Why: This is the record of what you bought and used. It is what lets us answer "how many plans do I have left" and settle any dispute about a purchase.

Kept: Kept while your account exists, because it is your purchase record.

Which lesson plans a credit has already paid for.

Why: So that editing the same plan again, or generating its slides, is never charged twice.

Kept: Kept while your account exists.

The GCash reference number you enter, the amount, what you bought, whether it was approved, and any note written when a payment could not be matched.

Why: To check your payment against our own GCash records before adding credits, by hand — the app cannot verify a payment on its own.

Kept: Five years, as a record of a sale for tax and accounting purposes.

Prepaid codes and how many plans each still carries. A code may have a short note recorded by us, such as which school it was issued to.

Why: So a code bought once cannot be redeemed more times than it was paid for.

Kept: Kept while the code can still be redeemed, then as a sales record.

Whatever you choose to put in the feedback form: a satisfaction rating, your role, a message, and optionally your name, school and email.

Why: To understand what is not working and fix it.

Kept: Two years, so that a problem reported once can still be traced later.

One row per AI request: which action it was, how many tokens it used, and the grade level and learning area involved. A random identifier for your browser, and — when you are signed in — which Google account made the request.

Why: To measure what the AI costs to run, which grades and subjects are actually used, and how much of the cost each account is responsible for. That is what pricing decisions are based on.

Kept: Two years, then reduced to counts that identify nobody. This never contains your lesson plan text, and never your name or school — the account is an identifier, and your email is only looked up from it when we read the ledger.

Nothing. This is an unused table left over from an earlier version of the credit system.

Why: None. It has been replaced by the credit record above and is listed here only so this page describes the database completely.

Kept: Due to be removed.

Who else sees it

Anthropic (AI processing, United States)

The text of the one field you are working on, at the moment you press Polish, Translate, Tidy, or draft a plan with AI. It is used to produce the result and is not stored by us. Learner Context is never sent.

Google (sign-in)

Sign-in is handled by Google, so Google knows you signed in to this service. We receive your email address, name and account identifier in return.

We do not sell your information, and we do not share it for advertising.

Cookies

Two cookies, both needed for the service to work: one keeps you signed in, and one is used only by the site owner's admin page. Neither is used for advertising or tracking you across other sites.

The public pages also load Google Analytics, which sets its own cookies to count visits. It is not loaded on the editor or on any signed-in page, so what you write is out of its reach.

Your learners' information

Anything identifying a specific child belongs on your device, not here. That is why AI help is switched off for the Learner Context field, and why attendance records and the Excel files built from them never leave your browser. As the teacher, you remain responsible for your pupils' records under your school's and the Department's own rules.

Your rights

Under the Data Privacy Act of 2012 (Republic Act No. 10173) you may ask what we hold about you, have it corrected, have it deleted, or object to how it is used. There is no button for this yet — requests are handled by a person, using the contact above.

Changes

If what we store changes, this page changes with it. It is generated from the service's own data structures, so it cannot quietly fall out of date.