Your information deserves clear protection.

1. Scope of this policy

This Privacy Policy applies to the Skoligo public website, School Admin Panel, staff and teacher experiences, student and parent experiences, connected attendance workflows, support services and other Skoligo services provided by Brindasoft (together, the “Services”).

It covers information handled when you browse our website, request a demonstration or trial, communicate with us, create or use an account, or use Skoligo through a participating school.

External websites, payment services, messaging services and app stores have their own privacy practices. This policy does not replace their notices.

2. The school’s role and our role

Schools: A school generally decides which student, parent, teacher and staff information is placed in Skoligo, the purposes for using it, the accounts that may access it and how long school records should be kept. The school is responsible for providing required notices and obtaining any permissions or consents needed for its use of the Services.

Brindasoft / Skoligo: We operate, maintain, secure and support the platform. For school-managed information, we generally act on the school’s instructions and use that information only to provide the Services, meet legal obligations, protect the platform and address support or security needs.

For public website enquiries, subscriptions, billing relationships and direct support communications, Brindasoft determines how the information is handled for those purposes.

3. Information we collect

Website, trial, demo and contact information

• Name, school name, email address, phone number, city, country, school address, requested workflows and an optional school logo.
• When you request a 14-day trial, we use the submitted details to create an active Basic trial school and its primary School Admin account, generate a temporary password and send account information by email.
• Public demo requests that do not create a trial prepare a message in your email application. That information is sent to us only if you choose to send the email.
• Information you send through email, WhatsApp, a support ticket or another contact channel.

Account and school profile information

• Names, usernames, email addresses, phone numbers, account roles, permissions, school details, status and authentication-related information.
• Subscription plan, capacity, add-ons, billing cycle, invoices, payment status, transaction references and related account history.

School-managed education and operational records

• Student and parent profiles, admissions, family relationships, academic history, classes, sections, subjects and promotion records.
• Teacher and staff profiles, qualifications, work experience, assignments, attendance, leave, salary grades, payroll and payslips.
• Attendance records, check-in and check-out times, leave, assigned NFC/RFID card identifiers, device records and scan audit logs.
• Timetables, homework, submissions, exams, marks, grades, result publication records, certificates, result cards and student ID records.
• Fee invoices, payments, refunds, balances and other school finance records.
• Notices, events, messages, attachments, reports, support tickets and replies.

Technical and usage information

• IP address, browser or app type, device information, operating system, request dates and times, session information and general activity needed to run and secure the Services.
• Error, audit, delivery and security logs, including notification delivery status, account activity and connected device events.
• Mobile notification tokens and device identifiers needed to deliver configured app notifications.

4. How we use information

We use information as reasonably necessary to:

• Provide school administration, attendance, academics, finance, communication, document, reporting and support features.
• Create and manage accounts, authenticate users, apply role permissions and keep each school’s records appropriately scoped.
• Process subscriptions and payment confirmations, maintain billing records and prevent duplicate or unauthorized transactions.
• Deliver notices, messages, scheduled reports and mobile notifications when those services are enabled.
• Activate requested trials and respond to demo requests, questions, support tickets and service communications.
• Monitor reliability, diagnose errors, prevent abuse, investigate security concerns and protect users, schools and the platform.
• Maintain, analyze and improve the Services using information that is appropriately limited for that purpose.
• Comply with applicable legal requirements and enforce our agreements.

We do not sell school-managed personal information or use student records for third-party behavioral advertising.

5. How information may be shared

We may disclose information only as needed for the following purposes:

• Within the school: to authorized administrators, staff, teachers, students or parents according to the school’s account settings, role permissions and publication choices.
• Service providers: to vendors that help provide hosting, email, push notifications, messaging, payment processing, storage, security or technical support. They receive only the information needed for their service and are expected to handle it appropriately.
• Configured integrations: to services selected or enabled by the school, such as attendance devices, Firebase Cloud Messaging, email services or payment gateways such as Easypaisa.
• Legal and safety needs: when disclosure is required by law, legal process or a valid government request, or when reasonably necessary to protect rights, safety, users or the integrity of the Services.
• Business changes: as part of a merger, acquisition, financing, reorganization or transfer of the Services, subject to appropriate confidentiality and continuity protections.

If you contact us through WhatsApp, email, an app store or another external channel, that provider also processes information under its own terms and privacy notice.

6. Student and children’s information

Skoligo is designed for use by schools and their authorized communities. Student information is entered or made available under the direction of the school, and student or parent access is connected to that school relationship.

Schools are responsible for ensuring they have an appropriate basis to collect and use student information, providing required notices, obtaining parent or guardian permission where required, and configuring access appropriately.

We do not use student information for third-party behavioral advertising. If a parent or guardian has a question about a child’s record, they should contact the school first. We will support the school in handling an appropriate request.

7. How long information is kept

We keep information only for as long as reasonably needed to provide the Services, follow the school’s instructions, maintain legitimate school or business records, resolve disputes, protect the platform and meet legal, accounting or security obligations.

Retention periods vary by record type. For example, active account and academic records may be retained while a school uses Skoligo; transaction and audit records may need to be kept longer; temporary logs and notification tokens may be kept for shorter periods.

When information is no longer required, it may be deleted, anonymized or securely archived. Some information may remain for a limited time in backups or records that must be preserved for legal, financial, fraud-prevention or security reasons.

8. How we protect information

We use administrative, technical and organizational safeguards designed to protect information against unauthorized access, loss, misuse or alteration. These measures include authenticated accounts, school-scoped access, role-based permissions, session protections, audit controls, validation and secure connections where supported.

No website, app, transmission or storage system can be guaranteed to be completely secure. Schools and users also help protect information by keeping credentials confidential, using strong passwords, limiting permissions and promptly reporting suspected unauthorized access.

9. Cookies, app storage and device permissions

The authenticated Skoligo platform uses essential session cookies or similar technologies to keep users signed in, protect requests and maintain security. Disabling essential storage may prevent parts of the Services from working.

The public website does not currently use advertising cookies or third-party advertising pixels. It may use basic browser functionality required to display the site and open requested email or contact links.

Mobile apps may store account settings, notification tokens or cached information needed for performance. Features such as attachments, camera use, notifications or NFC-related workflows may request device permissions when needed. Device settings can be used to review or withdraw those permissions, although the related feature may then stop working.

10. Access, correction and other choices

Depending on your relationship with Skoligo and applicable requirements, you may ask to access, correct, update or delete personal information, object to or restrict certain processing, or withdraw a consent you previously provided.

• School-managed records: contact the relevant school first. The school must verify the request and decide how the record should be handled.
• Direct enquiries and account matters: contact Skoligo using the details below.
• Communications: you may ask us to stop non-essential promotional communications. Service, security and account notices may still be sent when necessary.

We may need to verify identity and authority before acting. A request may be limited when information must be retained for school, legal, financial, safety or security reasons, or when fulfilling it would affect another person’s rights.

11. Service providers and processing locations

Skoligo and its service providers may store or process information in Pakistan or other countries where they operate. Data protection rules may differ between locations.

When we use an external provider, we select services based on the function required and seek appropriate confidentiality, security and data-handling protections. Schools should review the terms of any optional integration they choose to enable.

12. Changes to this policy

We may update this Privacy Policy when the Services, our practices or applicable requirements change. The revised page will show a new “Last updated” date. If a change materially affects how school-managed information is handled, we may also notify participating schools through the platform or another appropriate channel.

13. Contact us

For privacy questions about Skoligo, direct enquiries or account-related requests, contact Brindasoft’s Skoligo support team. For a student, parent, teacher or staff record managed by a school, please contact the school first so it can verify and authorize the request.