POLICIES
Privacy Policy
This policy explains what we collect when you use the service, why we need it, who we share it with, and the choices you have.
Who is responsible for your data
Me2u Technology, C/O P.O. Box 250, Mampong-Ashanti, Ashanti Region, Ghana, is responsible for the personal data described here. For any privacy question or request, email support@humanizestudio.app.
What we collect
- Account details: your email address, your name if you give it or sign in with Google, and a one-way hash of your password. We never store your password itself.
- Documents and text: files you submit for a report, the text taken from them, the reports that come back (scores, status, downloads), and text you send for humanization.
- Payments: the pack you bought, the amount, the Paystack reference, the payment status and the date. Card, mobile money and bank details go straight to Paystack and never reach us.
- Security data: sign-in sessions and short-lived counters keyed by IP address and email, which limit repeated sign-in, sign-up and upload attempts.
- Institution accounts: the institution's name, type, billing email and, if given, its tax number; invoice requests with the contact and purchase-order number entered; each member's role and monthly cap; the email addresses invited; a count of the checks and rewrites each member paid from the pool; and a log of admin actions (see below).
Why we use it
- to run your account and keep it secure;
- to produce, store and show your reports, and to rewrite text when you ask;
- to take payment, add your credits and send receipts;
- to run institution accounts: send invites, apply the shared pool and caps, show admins usage counts, and handle invoices;
- to send emails you need: a welcome message, password resets, receipts, "report ready" notices and institution invites;
- to prevent abuse and fraud, and to meet legal and accounting duties.
We do not sell your data and we do not use your documents to advertise to you.
Who we share it with
We share data only with the providers that run parts of the service, and only what each one needs:
- Our checking and rewriting service receives the documents and text you submit, to produce reports and rewrites.
- Paystack processes payments and receives your email and the order amount.
- Our email provider receives your email address and the message we send you.
- Cloudflare hosts the site and stores our database. Cloudflare runs data centres in many countries, so your data may be stored and processed outside Ghana.
- Google, only if you choose "Sign in with Google", confirms your email and name to us.
Some of these providers are based outside Ghana and handle data there. We choose providers that protect data with security measures at least as strong as ours. We may also disclose data when the law requires it.
Institution accounts
If you join an institution, the institution decides why it looks at its members' usage and what it does with that information, so it is responsible for that use. We hold and process the usage information for the institution and on its behalf. We stay responsible for your account and for everything else on this page. If you have a question about how your institution uses your usage information, ask the institution first. We will help it answer.
- What the institution's admins see: your email address, your name if you gave one, your role, your monthly cap, and how many checks and rewrites you paid from the pool, for any date range. They can download this as a spreadsheet. They never see your documents, file names or titles, text, scores or reports, and they never see anything you paid for with your own credits or did before you joined. The join page tells you this before you accept.
- What you see: your own cap and your own usage counts, on the institution pages.
- Invites: when an admin invites you, we store your email address and send you one email with a join link, and the institution's admins can see that the invite is waiting. We keep only a scrambled (hashed) copy of the link's secret. The link works once, only for an account with that email address, and expires after 7 days.
- Activity log: we record who did what in an institution and when: opening it, invites, joining, role and cap changes, removals, purchases and invoice steps. We use this log to keep accounts secure and to settle billing questions.
- After you leave: the institution keeps the usage counts from the time you were a member, because they are part of its billing records. If your account is deleted, your name and email no longer appear next to those counts.
- Students under 18: a school that invites students under 18 must first get any consent the law requires from a parent or guardian.
Stored in your browser
We use one essential cookie, hs_session, to keep you signed in for up to 30 days. Your browser also keeps your theme choice, editor drafts, folders, profile edits and, for Word files, a copy of the uploaded document so formatting survives a rewrite. These stay on your device until you clear them. We do not use advertising or tracking cookies.
How long we keep it
We keep account, report and document text for as long as your account is open. Payment records are kept as long as accounting law requires. Institution usage counts, invoices and the activity log are kept while the institution account is open. Security counters only count attempts from the last hour. When you ask us to delete your account, we delete your account, reports and stored text, except records we must keep by law.
Your rights
You can ask us to show you, correct, export or delete your personal data, or object to how we use it. Email support@humanizestudio.app from the address on your account and we will reply within one business day. If your request is about how an institution uses your usage information, we will pass it to that institution and help it reply. You can also complain to the Data Protection Commission in Ghana.
Security
Traffic is encrypted, passwords are stored only as salted hashes, sessions and invite links are stored only as hashes, and every report is checked against its owner before it is shown. Institution admins can reach only their own institution's records. No system is perfectly secure. If a breach affects your data, we will tell you and, where the law requires, the Data Protection Commission. If it affects an institution account, we will also tell the institution.
Changes
If we change this policy in a way that matters, we will update the effective date and, where reasonable, email you.