Privacy Policy

Masira by Aharsg.com

Website: https://masira.aharsg.com

Operated by Aharsg.com ("Aharsg," "we," "us," "our")

178 Stanislaus Street, Buffalo, New York 14212, USA

Privacy contact: info@aharsg.com

Effective Date: October 3, 2026

Last Updated: November 1, 2026

Table of contents

1. Introduction and Scope

2. Definitions

3. Roles: Institutions Control Student Data

4. Information We Collect, Module by Module

5. Information We Collect Automatically

6. Information We Receive From Google

7. Google API Services and Limited Use Commitment

8. Google Scopes We Request: Complete Detail

9. How We Read and Send Email Through Gmail

10. Human Access to Google User Data

11. Artificial Intelligence and Machine Learning

12. How We Use Information

13. Legal Bases for Processing (EEA/UK)

14. How We Share and Disclose Information

15. Student Data, FERPA, and Children's Privacy

16. Parent, Guardian, and Student Portals

17. Notifications: Email, SMS, and WhatsApp

18. Payments and Financial Data

19. Free Trial, Beta Program, and Accounts

20. Data Storage, Location, and Retention

21. Data Security

22. Your Rights and Choices

23. Revoking Access and Deleting Your Data

24. Cookies and Similar Technologies

25. International Data Transfers

26. California Privacy Rights (CCPA/CPRA)

27. Additional U.S. State Privacy Rights

28. EEA, UK, and Swiss Privacy Rights (GDPR)

29. Language, Calendars, and Localization

30. Third-Party Services and Links

31. Data Breach Notification

32. Changes to This Policy

33. Contact Us

1. Introduction and scope

1.1 Who We Are

Aharsg.com operates Masira (مسيرة), a cloud-based school management system for madrasas, Hifz academies, Dars-e-Nizami (Alim) seminaries, Islamic K-12 schools, and weekend schools, available at https://masira.aharsg.com and through related web, tablet, and phone interfaces (together, the "Service"). Our address is 178 Stanislaus Street, Buffalo, New York 14212, USA. You can contact our privacy team at info@aharsg.com.

1.2 What This Policy Covers

This Privacy Policy explains what information we collect when you use the Service, why we collect it, how we use it, who we share it with, how long we keep it, how we protect it, and what choices and rights you have. It applies to institution administrators, principals, office and finance staff, teachers and muallims, parents and guardians, students, applicants, and visitors to our website.

This Policy gives special attention to data we receive from Google through Google APIs ("Google user data"), including Gmail data, because that data is highly sensitive. Sections 6 through 11 describe which Google permissions we request, why each is necessary, what we do with the data, and what we never do with it.

1.3 Your Agreement

By using the Service you acknowledge that you have read this Policy. If you do not agree, please do not use the Service. Connecting a Google account is optional and always requires your explicit consent on Google's own consent screen. You can withdraw consent at any time (Section 23).

1.4 Our Core Privacy Commitments

• We request only the Google permissions we need to provide features you choose to use.
• We use Google user data only to provide user-facing features that are visible in the Service.
• We do not sell personal information, Google user data, or Student Data. Ever.
• We do not use Google user data or Student Data for advertising, including retargeting, personalized ads, or interest-based ads.
• We do not use Google user data or Student Data to train generalized or non-personalized AI or machine learning models.
• We do not allow humans to read Google user data except in the narrow circumstances in Section 10.
• We do not transfer Google user data to third parties except as described in Section 14.
• Each institution's data is logically isolated from every other institution's data.
• You can disconnect your Google account and request deletion of your data at any time.

1.5 Google API Services User Data Policy Compliance Statement

Aharsg.com's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

1.6 Beta Notice

Masira is in public beta. Features, modules, and integrations are released and changed continuously. This Policy applies to all current features and will be updated before we begin collecting new categories of data or using data in new ways (Section 32).

Gmail features status: The Gmail sending and Gmail expense scanning features described in Sections 7 through 11 use Google permissions that Google classifies as restricted. Google's verification of these permissions is in progress. Until it is complete, institutions cannot connect Gmail to the Service, and the Service shows a notice explaining that the features will be available once verification is finished.

2. Definitions

"Account" means the account you create or sign in to on the Service.

"Account Data" means information used to create and manage an Account, such as name, email address, phone number, role, and profile picture.

"Institution" means the madrasa, Hifz academy, seminary, school, or other educational organization that subscribes to Masira and manages its own students, staff, and families in the Service. Also called "School" in some product screens.

"Student Data" means information entered into the Service by or for an Institution that relates to an identifiable student or applicant, including education records.

"Family Data" means information about parents, guardians, sponsors, and emergency contacts entered into the Service.

"Staff Data" means information about teachers, muallims, administrators, and other staff entered into the Service.

"Hifz Data" means Qur'an memorization and revision records, including Sabaq (new lesson), Sabqi (recent revision), and Manzil (long-term revision) logs, quality ratings, mistake counts, and Juz progress.

"Content Data" means the content of emails, attachments, and related message data that we access from a connected email account.

"Metadata" means information about an email rather than its body, such as sender, recipients, subject, date and time, thread identifiers, and label identifiers.

"Google API Services" means the APIs and services provided by Google, including the Gmail API and Google Sign-In (OAuth 2.0 and OpenID Connect).

"Google user data" means any data we receive from Google API Services about you, including Google Sign-In profile data and Gmail Content Data and Metadata.

"OAuth Token" means the access token and refresh token Google issues to the Service after you grant consent. Tokens let us act within the permissions you approved without ever seeing your Google password.

"Scope" means a specific permission the Service asks you to grant on Google's consent screen.

"Restricted Scope" means a Scope Google classifies as restricted because it allows access to especially sensitive data, such as reading the contents of your email.

"Sensitive Scope" means a Scope Google classifies as sensitive because it allows access to private data or actions, such as sending email on your behalf.

"Non-Sensitive Scope" means a Scope that does not require sensitive or restricted verification, such as basic sign-in information.

"Personal Information" means information that identifies, relates to, describes, or can reasonably be linked to an individual.

"Process" means any operation performed on data, including collecting, storing, reading, analyzing, transmitting, and deleting.

"Service Providers" means third-party vendors that process data on our behalf under contract, such as cloud hosting, messaging, and payment providers.

3. Roles: institutions control student data

3.1 Institution as Controller

For Student Data, Family Data, and Staff Data entered into Masira by an Institution, the Institution decides what data to collect and why. The Institution is the data controller (under GDPR), the "business" (under CCPA), and the educational institution responsible for education records (under FERPA, where applicable). Aharsg acts as a service provider and data processor, processing that data only on the Institution's documented instructions and to provide the Service.

3.2 Aharsg as Controller

For our own website, billing, Account administration, free trial and onboarding, security, support, and for data we receive from Google when a user signs in or connects Gmail, Aharsg acts as the controller of that data for the limited purposes described in this Policy.

3.3 Institution Responsibilities

Each Institution is responsible for having a lawful basis to collect Student Data, for obtaining any parental consents required by law, for the accuracy of data it enters, for configuring user roles and permissions appropriately, and for responding to requests from parents and students about records. If you are a parent, guardian, or student and want to access or correct records, please contact your Institution first. We will help the Institution respond.

3.4 Our Commitment to Institutions

We process Student Data only to provide and support the Service to the Institution. We do not use Student Data to build advertising profiles, we do not sell it, and we do not use it for any purpose unrelated to the Institution's use of the Service.

3.5 Data Isolation

Each Institution's data is logically separated from every other Institution's data. Users can access only the data of the Institution that granted them access, according to their role and permissions.

4. Information we collect, module by module

The information collected depends on which modules an Institution uses. Institutions decide what to enter. The list below describes what each module can hold.

4.1 Admission Management

• Enquiry and applicant details: applicant name, date of birth, gender, previous school, desired programme or class, and enquiry notes.
• Parent and guardian contact details provided at enquiry.
• Application status, interview or assessment notes, and decisions.
• Documents uploaded by the Institution or family (for example, birth certificate, prior records, photographs, identity documents).
• On enrollment: registration number, linked family record, and class placement.

4.2 Student Records and Families

• Student profile: name, photo, date of birth, gender, registration number, class, programme (for example Hifz, Alim, or Islamic K-12), enrollment date, and status.
• Contact and residence details, including boarding or day-student status.
• Family and guardian records: names, relationships, phone numbers, email addresses, home addresses, and occupation if the Institution collects it.
• Emergency contacts and authorized pickup persons.
• Sponsor information for sponsored students: sponsor name, contact details, and sponsorship amounts or terms the Institution chooses to record.
• Health and safety notes the Institution chooses to enter, such as allergies, medical conditions, or special needs.

4.3 Academic Management

• Classes, subjects, books and curriculum assignments, timetables, and teacher assignments.
• Exams, assessments, marks, grades, transcripts, report cards, and teacher comments.
• Dual-track grading records for both Islamic and academic programmes.
• Ramadan and prayer-time schedules and other calendar settings.

4.4 Hifz Tracking

• Daily Sabaq, Sabqi, and Manzil logs.
• Quality ratings, mistake counts, and teacher notes.
• Juz-by-Juz progress and heatmaps for each student.
• Completion milestones and revision schedules.

Hifz Data is educational progress data. It can reveal religious practice and the religious education of a child, so we treat it as sensitive and protect it accordingly (Section 21).

4.5 Attendance

• Lesson attendance, prayer attendance, Hifz session attendance, and boarding attendance.
• Configurable attendance codes (for example present, absent, late, excused) and absence reasons.
• Kiosk check-in records, including time and location of check-in at the Institution. If an Institution enables kiosk check-in using cards, codes, or photos, the Institution is responsible for informing families and obtaining required consents. We do not collect or store biometric identifiers such as fingerprints or face templates through the Service.
• Automatic daily summaries and reports.

4.6 Fees and Accounts

• Fee structures, invoices, discounts, scholarships, and payment plans.
• Payments received, payment method type and reference, receipts, and outstanding balances.
• Income and expense records, funds, and collections as entered by the Institution.
• Sponsor payments and fund allocations.

4.7 Staff and Payroll

• Staff records: name, contact details, role, employment dates, subjects taught, and schedule.
• Qualifications and ijazah details.
• Roles and permissions within the Service.
• Leave requests and approvals.
• Monthly pay stubs, salary amounts, deductions, and payment records.
• Bank or payment details only if the Institution chooses to enter them for payroll purposes. We recommend Institutions avoid storing full bank account details unless necessary.

4.8 Parent and Student Portals

• Portal login credentials and profile information.
• Records a user views, such as attendance, grades, Hifz progress, invoices, and announcements, according to what the Institution makes visible.
• Messages and acknowledgments a parent or student submits through the portal.

4.9 Communications

• Announcements, notices, and messages sent through the Service.
• Delivery status for email, SMS, and WhatsApp messages (Section 17).
• Message templates and schedules.

4.10 Documents and Files

• Files uploaded by Institutions, staff, or families, such as scans, certificates, photos, and reports.

4.11 Reports and Exports

• Reports and exports generated by the Institution, including PDF and government-format exports where available.

4.12 Account, Trial, and Billing Information (Aharsg as Controller)

• Name, email, phone number, Institution name, role, and country.
• Free trial sign-up information. No payment card is required to start the 30-day free trial.
• Subscription plan, billing contact, and invoices after the trial.
• Payment details processed by our payment processor. We do not store full card numbers.

4.13 Support and Feedback

• Messages, attachments, screenshots, and feedback you send us.
• Beta program feedback, feature requests, and survey responses.

5. Information we collect automatically

• Device and Browser Data: device type, operating system, browser type and version, screen resolution, and language.
• Log Data: IP address, access times, pages viewed, referring URLs, error reports, and crash diagnostics.
• Usage Data: features used, session length, and general interaction patterns, collected to keep the Service reliable and improve it.
• Approximate Location: derived from IP address, used for security, fraud prevention, and legal compliance.
• Cookies and similar technologies: described in Section 24.

We do not knowingly collect precise geolocation or biometric identifiers. However, notes, documents, or emails entered or uploaded by users may incidentally contain sensitive information. Sections 9 and 15 explain how we treat it.

6. Information we receive from google

If you sign in with Google or connect your Google account, we receive information from Google according to the Scopes you approve. Depending on those Scopes, this may include:

• Your Google account email address, name, profile picture, locale, and unique account identifier.
• Whether your email address is verified.
• The content and Metadata of emails and threads in your mailbox (only if you grant the read Scope).
• The ability to send messages from your account (only if you grant the send Scope).

We do not collect your Google password. Authentication happens on Google's servers. We do not collect Google user data beyond the Scopes you approve. We do not combine Google user data with data from other sources to build advertising profiles.

7. Google api services and limited use commitment

7.1 How the Google Connection Works

When you choose "Sign in with Google" or "Connect Gmail," you are redirected to Google's own consent screen. That screen lists the specific permissions the Service is requesting. You decide whether to approve them. If you approve, Google sends us OAuth Tokens that allow the Service to access only the data covered by the approved Scopes.

You can see and revoke the Service's access at any time at https://myaccount.google.com/permissions.

7.2 Limited Use Requirements

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In plain language:

(a) We only use Google user data to provide or improve features that are prominent in the Service's user interface and that you requested. We use it for no other purpose.

(b) We only transfer Google user data to others when it is (i) necessary to provide or improve user-facing features, (ii) necessary to comply with applicable law, (iii) part of a merger, acquisition, or sale of assets with notice to you, or (iv) done with your affirmative, explicit consent for a specific purpose.

(c) We do not use or transfer Google user data for serving advertisements, including retargeting, personalized, or interest-based advertising.

(d) We do not allow humans to read Google user data unless (i) we have your affirmative agreement for specific messages, (ii) it is necessary for security purposes such as investigating abuse, (iii) it is necessary to comply with applicable law, or (iv) the data, including derivations, is aggregated and used for internal operations in accordance with applicable privacy law.

(e) We do not use Google user data to develop, improve, or train generalized AI or machine learning models.

(f) We do not sell Google user data or use it to determine creditworthiness or for lending purposes.

7.3 Minimum Necessary Access

We request the narrowest Scope that lets a feature work. If you never enable a feature, we do not ask for its Scope.

7.4 Incremental Authorization

Where possible, we ask for permissions at the moment you need them. For example, we do not ask for permission to send email until you try to send an email through the Service.

7.5 Verification and Security Assessment

Because the Service requests a Restricted Scope, we complete Google's OAuth app verification and the independent third-party security assessment Google requires, and we repeat that assessment as Google requires. The assessment evaluates how we store, transmit, and protect Google user data.

Current status: As of November 1, 2026, Google's verification of the Service's restricted Gmail scopes is in progress. Google's review typically takes four to six weeks. While verification is pending, connecting Gmail is turned off for institutions in the Service. We will notify institutions when the Gmail features become available.

8. Google scopes we request: complete detail

This section describes every Google Scope the Service requests, how Google classifies it, what it allows, why we need it, how and when we access it, what we store, and what we never do with it.

8.1 SIGN-IN SCOPES (NON-SENSITIVE)

SCOPE: openid

Classification: Non-Sensitive

What it provides: Confirms your identity through OpenID Connect.

Why we need it: To authenticate you securely without handling your Google password.

SCOPE: https://www.googleapis.com/auth/userinfo.email

Classification: Non-Sensitive

What it provides: Your primary Google email address and whether it is verified.

Why we need it: To create and identify your Masira Account, link your Google account to it, send you service notices (security alerts, receipts), and show which Google account is connected.

SCOPE: https://www.googleapis.com/auth/userinfo.profile

Classification: Non-Sensitive

What it provides: Your name, profile picture, and locale.

Why we need it: To personalize the Service (for example, showing your name and photo) and to help you recognize which account is connected.

How we use sign-in data: to create your Account and log you in; display your name and photo; associate your Account with the correct Institution; send transactional messages about your Account, billing, and security; and detect and prevent duplicate accounts, fraud, and abuse. We do not use sign-in data for advertising, we do not sell it, and we share it only with Service Providers under confidentiality obligations (Section 14).

Signing in with Google does not by itself give us access to your email. Mailbox access happens only if you separately grant the Gmail Scopes below.

8.2 SCOPE: https://www.googleapis.com/auth/gmail.send

Classification: SENSITIVE SCOPE

What it allows: Sending email on your behalf from your Gmail address. It does NOT allow reading your mailbox and does NOT allow viewing, modifying, or deleting existing messages.

Why we request it: Institution administrators and staff use Masira to communicate with parents, guardians, sponsors, and staff. This access is necessary so that you can:

• Send fee reminders, invoices, and payment receipts to parents and sponsors from your Institution's Gmail address.
• Send attendance notices and absence alerts.
• Send announcements, event notices, schedule and Ramadan timetable changes, and closure notices.
• Send report cards, exam results, and Hifz progress reports.
• Send admission updates and responses to applicants' families.
• Send staff notices, leave decisions, and pay stub notifications.
• Send individual messages and replies that you write inside Masira.
• Send messages at a time you schedule.
• Send test messages to yourself.

Why messages come from your own Gmail: Messages sent from your Institution's own address land in your Sent folder, thread with replies, and show recipients a familiar, trusted sender, which matters when families decide whether a fee or attendance email is genuine.

How and when we send: We send an email only when you take an explicit action (such as clicking Send), or when you have configured and enabled a schedule or automation (such as an automatic fee reminder). We do not send emails you have not asked for. We never send marketing, promotional, or spam messages from your account.

What we store: A log of what was sent through the Service (recipient, subject, time, and delivery status) so you can review your sending history. The copy of the message body is kept for the period in Section 20.

What we never do with it:

• We never send messages you did not authorize.
• We never send advertising or unsolicited bulk email through your account.
• We never add hidden recipients or hidden tracking.
• We never use the send permission to read your mailbox.

8.3 SCOPE: https://www.googleapis.com/auth/gmail.readonly

Classification: RESTRICTED SCOPE

What it allows: Viewing your email messages and settings, including the full content of messages (subject, body, and headers), attachments, labels, and thread structure. It does NOT allow us to modify, delete, or send anything.

Why we request it: This access is used only for the Expense Capture feature in Masira, which you choose to turn on. It lets Masira:

• Find emails that appear to be bills, invoices, and receipts from vendors and suppliers.
• Read the message text and relevant attachments to extract the vendor name, date, amount, currency, and description.
• Create draft expense entries in the Masira Expenses module so you do not have to enter them manually.

You review and confirm every extracted expense before it is saved to your Institution's accounts.

Why a narrower scope is not enough: Amounts, vendors, and dates appear in the body or attachments of the email, not in the metadata.

What we limit: Masira searches only for messages that appear to be bills, invoices, or receipts. We do not browse, index, or store the rest of your mailbox. Messages that are not expense-related are not stored.

How and when we read your data:

• On connection and while connected, we search for new expense-related messages periodically.
• On demand, when you choose to scan for expenses.
• After you disconnect, all reading stops.

What we store: The extracted expense details (vendor, date, amount, description) and, where needed to let you verify them, a copy of the source message or attachment, encrypted, while your account is connected. These are deleted according to Sections 20 and 23. Expense records you confirmed remain part of your Institution's accounts until you delete them.

What we never do with it:

• We never sell it.
• We never use it for advertising or ad profiling.
• We never use it to train generalized AI or machine learning models.
• We never allow humans to read it except as described in Section 10.
• We never transfer it except as described in Section 14.
• We never use it to determine creditworthiness or eligibility for credit, insurance, housing, or employment.

8.4 Summary Table of Scopes

8.5 Granular Consent

Google may let you approve some Scopes and decline others. If you decline a Scope, features that depend on it will be unavailable but the rest of the Service will continue to work where possible. We will not repeatedly pressure you to grant a Scope you declined.

9. How we read and send email through gmail

9.1 What "Reading Your Email" Means

When we say the Service "reads" your email, we mean our automated systems retrieve messages from Gmail through the Gmail API using your OAuth Token and process them to provide the features you enabled. Our personnel do not read your emails as part of normal operations (Section 10).

9.2 When Reading Happens

(a) At connection, to prepare the conversations shown in Masira.

(b) While connected, to check for new replies and keep your view current.

(c) On demand, when you open a conversation or run a search.

(d) Never after disconnection.

9.3 What Parts of a Message We Process

• Headers: sender, recipients, subject, date, message ID, thread ID, and reply-to.
• Body: the plain-text or HTML content of the message.
• Attachments: file names, types, and sizes. We do not open or analyze attachment content except to display it to you at your request.
• Labels and state: such as Inbox, Sent, and read or unread status.

9.4 Why Each Kind of Reading Is Needed

• Displaying replies: you cannot see replies in Masira unless we retrieve them.
• Linking replies to records: matching a reply to the right student, invoice, or absence requires reading its content.
• Search: we index the messages shown in Masira so you can find them.
• Security: limited automated checks to detect malicious use of the Service.

9.5 What We Do With Your Email Content

We use your email content only to (1) show it to you in the Service; (2) run features you turned on, applied to your own mailbox for your own Institution's benefit; (3) maintain, secure, and troubleshoot the Service as it relates to your use; and (4) comply with law or protect against fraud and abuse (Section 10).

9.6 What We Do Not Do With Your Email Content

• We do not sell, rent, or license it.
• We do not use it for advertising, ad targeting, or ad profiles.
• We do not share it with other Institutions or users.
• We do not use it to train generalized AI or machine learning models.
• We do not use it for credit, lending, insurance, or employment decisions.

9.7 Sensitive Content in Mailboxes

Your email may contain sensitive financial, medical, religious, or family information about you and others. We do not seek it, classify it, or profile anyone based on it. We apply the same protections to all message content regardless of subject.

9.8 Emails of Third Parties

Your mailbox contains information about other people, such as parents, guardians, and sponsors. We process their information only as part of your mailbox, only to serve you and your Institution, and subject to the restrictions in this Policy. If you are not a user and believe your information is in our systems, contact info@aharsg.com.

9.9 When We Send

We send email only: (a) when you click Send or otherwise explicitly confirm a message; (b) at a future time you scheduled; (c) as part of an automation you created, reviewed, and enabled (such as recurring fee reminders); or (d) when you send a test message to yourself.

9.10 What We Never Send

• We never send emails you did not initiate, approve, or configure.
• We never send advertising, marketing, or promotional email through your account.
• We never send emails to people you have not chosen as recipients, or to people who are not in your Institution's records.
• We never alter the content of messages you approved, other than adding disclosed items such as a signature you chose.

9.11 Limits and Compliance

You are responsible for using the Service in compliance with applicable laws, including CAN-SPAM, and Google's sending limits and policies. We may impose sending limits to protect your account's reputation and to prevent abuse.

9.12 Tracking

Masira does not use open or click tracking pixels in emails sent through your account. If we ever add such a feature, it will be optional, clearly disclosed, shown only to you, and never used for advertising.

9.13 Control

You can disconnect your mailbox at any time from the Service settings or from your Google Account permissions page, which stops all reading and sending immediately.

10. Human access to google user data

10.1 Default Rule

Our employees and contractors do not read Google user data, including your email content.

10.2 Narrow Exceptions

A person may view Google user data only:

(a) With your affirmative agreement for specific messages (for example, when you ask support to look at a message to fix a problem);

(b) When necessary for security purposes, such as investigating abuse or a security incident;

(c) When necessary to comply with applicable law or a valid legal process; or

(d) When the data is aggregated and anonymized and used for internal operations in accordance with applicable privacy law.

10.3 Access to Student Data and Support Access

Support personnel may access an Institution's workspace only to provide support the Institution requested, to maintain the Service, or for the security reasons above. Access is limited, logged, and protected by multi-factor authentication. Personnel are bound by confidentiality obligations and receive privacy and security training.

11. Artificial intelligence and machine learning

11.1 No Training on Google User Data or Student Data

We do not use Google user data or Student Data to develop, improve, or train generalized or non-personalized AI or machine learning models, ours or anyone else's.

11.2 No Sharing With AI Providers

We do not send Google user data to third-party AI providers.

11.3 Future Features

If we introduce an AI-assisted feature that processes Google user data or Student Data, it will operate only to serve the user or Institution, only on the data needed for that feature, with providers contractually prohibited from retaining the data or using it for training. We will update this Policy and obtain any consent required before launch.

12. How we use information

We use information to:

• Provide, operate, and maintain the Service and its modules.
• Create and manage Accounts and authenticate users.
• Provision Institution workspaces, free trials, and subscriptions.
• Send service communications (security alerts, billing notices, important updates).
• Process payments and manage subscriptions.
• Provide customer support and respond to requests.
• Keep the Service secure, prevent fraud and abuse, and enforce our terms.
• Diagnose problems, measure performance, and improve the Service using aggregated or de-identified data that does not include Google user data.
• Develop and test new features during the beta, using de-identified or synthetic data where practical.
• Comply with legal obligations and respond to lawful requests.

We do not use personal information for advertising. We do not use Google user data for any purpose other than the user-facing features described in Section 8.

13. Legal bases for processing (eea/uk)

Where GDPR or UK GDPR applies, our legal bases are:

• Performance of a contract: providing the Service you or your Institution requested.
• Consent: connecting your Google account and granting Scopes; optional notifications. You can withdraw consent at any time (Section 23).
• Legitimate interests: security, fraud prevention, service improvement, and support, balanced against your rights.
• Legal obligation: complying with law, tax, and regulatory requirements.

For Student Data, the Institution determines the legal basis as controller.

14. How we share and disclose information

14.1 We Do Not Sell Personal Information

We do not sell personal information and do not share it for cross-context behavioral advertising.

14.2 Who We Share With

• The Institution: information entered or generated within an Institution's workspace is available to that Institution's authorized users according to their roles and permissions. Parents and students see only what the Institution makes visible to them.
• Service Providers: cloud and application platform hosting, file and media storage, email delivery infrastructure, SMS and WhatsApp messaging providers, payment processing, error monitoring, and customer support tools, bound by contracts that limit them to providing services to us and require appropriate security.
• Google: when you connect your Google account, data flows between Masira and Google as needed to provide the features you enabled.
• Legal and safety: when required by law, subpoena, or valid legal process, or to protect the rights, safety, and property of users, Institutions, us, or the public.
• Business transfers: in a merger, acquisition, or sale of assets, with notice to you and with the buyer bound by this Policy. Google user data is transferred only as permitted by Google's Limited Use requirements.
• With your consent: for a specific purpose you approve.

14.3 Google User Data

Google user data is shared only as permitted by Section 7.2.

14.4 Aggregated Data

We may use aggregated or de-identified data that cannot reasonably identify any person or Institution, and that does not include Google user data, to understand and improve the Service.

15. Student data, ferpa, and children's privacy

15.1 FERPA

Where an Institution is subject to the Family Educational Rights and Privacy Act (FERPA), we act as a "school official" with a legitimate educational interest under the Institution's direct control for the use and maintenance of education records. We use education records only for the purposes the Institution authorizes.

15.2 COPPA

Masira is a service for Institutions, not a service directed to children for direct consumer use. Student profiles are created by Institutions and families, not by children. We do not knowingly collect personal information directly from children under 13 without verifiable parental consent or Institution authorization as permitted by the Children's Online Privacy Protection Act (COPPA). Where an Institution collects information from children under 13, the Institution represents that it has obtained any required parental consent or is authorized to consent on parents' behalf for educational purposes.

15.3 Student Data Restrictions

We do not:

• Sell Student Data.
• Use Student Data for targeted advertising or to build advertising profiles.
• Use Student Data for any purpose outside providing the Service to the Institution.
• Allow third parties to use Student Data other than Service Providers acting for us.

15.4 Religious and Sensitive Education Data

Hifz Data, religious education records, and related notes may reveal religious beliefs or practices. We use them only to provide the Service to the Institution and never for profiling, advertising, or any unrelated purpose.

15.5 Access, Correction, and Deletion

Parents, guardians, and eligible students may review or request correction of records through their Institution. Institutions may export or delete Student Data at any time. On termination of an Institution's subscription, we delete or return Student Data according to Section 20.

15.6 Child Data Collected in Error

If we learn that we collected personal information directly from a child without proper authorization, we will delete it. Contact info@aharsg.com.

16. Parent, guardian, and student portals

16.1 What Portals Show

Parent and student portals let family members view information the Institution chooses to share, such as attendance, grades, Hifz progress, invoices, payments, timetables, and announcements.

16.2 Who Controls Visibility

The Institution controls what each portal user can see and do. A parent sees records of their own children only.

16.3 Portal Accounts

Portal accounts are created or approved by the Institution. We store credentials securely (passwords are hashed), and we do not display one family's information to another family.

16.4 Student Access

Where an Institution gives students portal access, the Institution is responsible for ensuring this is appropriate for the student's age.

17. Notifications: email, sms, and whatsapp

17.1 Types of Notifications

Institutions may send notifications through the Service, including attendance alerts, fee reminders, announcements, and emergency notices, by email, SMS, or WhatsApp (as these channels become available).

17.2 Providers

SMS and WhatsApp messages are delivered by third-party messaging providers acting as our Service Providers. They receive only the phone number, message content, and delivery metadata needed to deliver the message.

17.3 Consent and Opt-Out

Institutions are responsible for having permission to message recipients. Recipients can ask the Institution to stop notifications, and can reply STOP to SMS messages where supported.

17.4 No Marketing

We do not use these channels to send marketing on behalf of third parties.

18. Payments and financial data

18.1 Subscription Payments

If an Institution subscribes after the trial, payments are processed by a third-party payment processor. We do not store full card numbers or security codes. We receive transaction status, the last digits of a card, and billing details needed for invoicing.

18.2 Fee Records

Fee structures, invoices, payments, and balances recorded in the Service are Institution data. Masira records and reports them; it does not itself collect tuition payments from families unless an Institution enables an online payment feature, in which case the processor handles card data and we receive only status and reference information.

18.3 Payroll Records

Pay stubs and salary records are Institution data and are visible only to users the Institution authorizes.

19. Free trial, beta program, and accounts

19.1 Free Trial

The 30-day free trial requires no payment card. We collect the account and Institution details needed to set up your workspace. When the trial ends, you may subscribe, export your data, or request deletion. If you take no action, we may retain trial data for a limited time (Section 20) and then delete it.

19.2 Beta

Masira is in public beta. We may collect feedback and diagnostic information to improve the product. We will not use Student Data or Google user data for beta testing outside your Institution's workspace.

19.3 Accounts

You are responsible for keeping your login credentials confidential and for activity under your Account. Notify us at info@aharsg.com if you suspect unauthorized access.

20. Data storage, location, and retention

20.1 Where Data Is Stored

Data is stored with reputable cloud infrastructure and application platform providers, in data centers located in the United States unless an Institution is told otherwise.

20.2 Retention Periods

• Account Data: kept while your Account is active, then deleted within 30 days of Account closure.
• Institution, Student, Family, and Staff Data: kept while the Institution's subscription or trial is active. After termination, deleted or returned within 30 days of the Institution's request or end of contract, unless law requires longer retention.
• Expired trial workspaces with no action: deleted within 90 days after trial end.
• Gmail message copies and Metadata: kept only while your Google account is connected. Deleted within 30 days after you disconnect, revoke access, or delete your Account.
• OAuth Tokens: deleted immediately upon disconnection or revocation.
• Sent-message activity logs: kept for up to 12 months, or until you delete your Account, then deleted.
• Backups: removed from encrypted backups within 90 days of deletion.
• Security and audit logs: kept up to 12 months.
• Billing records: kept as required by tax and accounting law.

20.3 Legal Holds

We may retain specific records longer when required by law or to resolve disputes, and only for that purpose.

20.4 Institution Retention Choices

Institutions decide how long to keep student, attendance, academic, and financial records, subject to the laws that apply to them. Institutions can export and delete records within the Service.

21. Data security

We use administrative, technical, and physical safeguards appropriate to the sensitivity of the data, including:

• Encryption in transit (TLS 1.2 or higher) and at rest (AES-256 or equivalent).
• Encrypted storage of OAuth Tokens, kept separate from other data.
• Hashed passwords and optional multi-factor authentication.
• Role-based access controls and least-privilege access, with configurable roles and permissions for Institution staff.
• Logical separation of each Institution's data.
• Logging and monitoring of access to sensitive systems.
• Network protections, secure development practices, and regular security testing and patching.
• Independent security assessment as required by Google for Restricted Scopes.
• Employee confidentiality obligations and security training.

No system is completely secure. If you believe your Account has been compromised, contact info@aharsg.com immediately.

22. Your rights and choices

Depending on where you live, you may have the right to:

• Access the personal information we hold about you.
• Correct inaccurate information.
• Delete your information.
• Export your data in a portable format.
• Restrict or object to certain processing.
• Withdraw consent at any time.
• Opt out of sale or targeted advertising (we do neither).
• Not be discriminated against for exercising your rights.

To exercise a right, email info@aharsg.com. We may verify your identity first. For Institution-controlled data, we will refer you to or coordinate with your Institution. We respond within the time required by law, generally within 30 to 45 days.

23. Revoking access and deleting your data

23.1 Disconnect Google From Masira

Go to Settings in Masira and choose Disconnect Google Account. This stops all access and sync.

23.2 Revoke From Google

Visit https: //myaccount.google.com/permissions, select Masira, and choose Remove Access. We lose the ability to read or send immediately.

23.3 What Happens After Disconnection

• We stop all reading and sending through your Google account.
• OAuth Tokens are deleted immediately.
• Stored Gmail message copies and Metadata are deleted within 30 days (Section 20).
• Features that depend on the connection are disabled.

23.4 Delete Your Account or Data

Email info@aharsg.com from your registered address with the subject "Delete My Data." We delete your Account Data and Google user data within 30 days, subject to legal retention requirements. Institution administrators can request deletion of the Institution's entire workspace.

24. Cookies and similar technologies

We use cookies and similar technologies for:

• Essential functions: keeping you signed in, security, and load balancing.
• Preferences: language, calendar (Hijri or Gregorian), and display settings.
• Analytics: aggregated usage statistics to improve the Service.

We do not use advertising cookies and do not use cookies to target ads. You can control cookies in your browser settings; blocking essential cookies may stop the Service from working. We do not currently respond to Do Not Track signals, because we do not track users across other sites.

25. International data transfers

We are based in the United States, and data is processed there. Institutions in other countries use the Service by transferring data to the U.S. Where required, we rely on appropriate safeguards such as Standard Contractual Clauses for transfers from the EEA, UK, or Switzerland. Institutions outside the U.S. are responsible for assessing local legal requirements for sending student data abroad.

26. California privacy rights (ccpa/cpra)

California residents have the right to know what personal information we collect, use, and disclose; to delete it; to correct it; to opt out of sale or sharing (we do not sell or share personal information for cross-context behavioral advertising); to limit use of sensitive personal information (we use it only to provide the Service); and to be free from discrimination. In the past 12 months we have collected the categories described in Sections 4 through 6 for the business purposes in Section 12, and have not sold or shared personal information. Submit requests to info@aharsg.com. An authorized agent may submit a request on your behalf with proof of authorization.

27. Additional u.s. state privacy rights

Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, and other states with privacy laws may have rights to access, correct, delete, and obtain a copy of their data, and to opt out of targeted advertising, sale, and profiling. We do none of the latter. To exercise rights or appeal a decision, email info@aharsg.com with the subject "Privacy Request" or "Privacy Appeal."

28. Eea, uk, and swiss privacy rights (gdpr)

If you are in the EEA, UK, or Switzerland, you have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to withdraw consent at any time without affecting prior processing. You may lodge a complaint with your local data protection authority. For data controlled by your Institution, contact the Institution first. Our contact for data protection matters is info@aharsg.com.

29. Language, calendars, and localization

The Service offers English and Arabic interfaces and supports Hijri and Gregorian dates. Your language and calendar preferences are stored as part of your Account settings and used only to display the Service in the way you choose. This Policy is provided in English; if a translation is provided, the English version controls unless local law requires otherwise.

30. Third-party services and links

The Service may link to or integrate with third-party services (for example, Google, messaging providers, and payment processors). Their privacy practices are governed by their own policies. We encourage you to review them. Google's Privacy Policy is at https://policies.google.com/privacy.

31. Data breach notification

If a security incident affects your personal information, we will notify affected Institutions and users, and regulators where required, without undue delay and in accordance with applicable law, describing what happened, what data was involved, and what steps to take.

32. Changes to this policy

We may update this Policy as Masira evolves, including as new modules (such as online admissions, expanded portals, and SMS and WhatsApp notifications) are released. We will post the new version with a new "Last Updated" date and, for material changes, notify you by email or in the Service. If we change how we use Google user data, we will obtain your consent where required. Continued use after changes means you accept the updated Policy.

33. Contact us

Aharsg.com (Masira)

178 Stanislaus Street

Buffalo, New York 14212, USA

Email: info@aharsg.com

Website: https://masira.aharsg.com

Company website: https://aharsg.com

End of privacy policy