Privacy Policy

Last updated: 12 November 2026

This Privacy Policy explains how CampusShield AI collects, uses, stores and protects personal information when you use the platform, including account, campus identity, safety reporting, community and academic-support features.

Privacy contact

Service: CampusShield AI. For privacy questions, access, correction or deletion requests, contact campusshieldaitechnologies@gmail.com. We may ask for reasonable information to verify a request and protect account security.

1. Information you provide

• Account and profile information: email address, display name or public username, requested account type, institution, and other fields you submit during onboarding or profile editing.
• Campus identity and verification: institution, student or staff identifier, verification status, and identity documents submitted through an enabled review workflow. Identity files are designed to be stored in a private storage area, with access limited by configured authorization policies.
• Safety and help requests: incident category, severity, location details, narrative, attachments, review status, and information needed to manage a report.
• Community and campus-life activity: posts, replies, group or event activity, bookmarks, requests, and content you choose to submit to available features.
• Messages to support: information you choose to include when contacting us.

2. Information handled by the service

Authentication, hosting and security components may process request timestamps, browser/session information, technical diagnostics and security logs. The app uses device-local storage for limited settings and session-related functionality. Technical details and data flows depend on which integrations are enabled in the deployment you use.

3. Service providers and when they may receive data

The current code identifies the following services. Inclusion here does not mean every optional integration is enabled in every environment.

• Website hosting providers: deliver the public website and support deployment, availability and security. Providers may process normal request and operational logs.
• Supabase: provides application authentication, database, private object storage and server-side functions. Account/profile data, campus membership, safety reports, identity-review records, and notification subscription records may be stored in the configured Supabase project.
• OpenAI: ShieldMind sends a user's permitted academic question and selected chat history to the OpenAI API when the server-side OpenAI key is configured and the request passes the app's checks. Where the user has verified campus access, excerpts from approved public campus pages may also be included. Do not submit sensitive information; automated checks cannot guarantee that every sensitive detail is detected.
• Paystack: if checkout is enabled, the billing function sends the confirmed account email, plan/amount/currency, payment reference and checkout metadata for transaction initiation and verification. Payment processing is subject to Paystack's own terms and privacy notice.
• Google and Supabase Auth email delivery: Google sign-in is optional and is only available where configured. Account confirmation and recovery emails are handled through Supabase Auth and the email-delivery configuration for that project; the configured SMTP/email vendor was not identifiable from the repository review.
• Browser push infrastructure: when a user enables background notifications, the app stores a push subscription with the configured backend and sends generic notification messages through web-push. The relevant browser/platform push service may process the subscription endpoint and delivery request.

Service providers process information only as needed to deliver, secure and support the features they provide. Their own privacy notices and terms may also apply when you use those services.

4. Why information is used

Information may be used to create and secure accounts, maintain campus membership, review identity or staff applications, receive and route reports to authorized reviewers, operate community features, send requested service notifications, prevent abuse, troubleshoot failures, and meet applicable legal or security obligations.

5. Who may see information

• Authorized campus reviewers may access information necessary for their assigned verification, incident, or support responsibilities, subject to configured access controls.
• Public or community content may be visible to other users when you submit or publish it in a feature designed for sharing. Do not place private information in public posts.
• Infrastructure providers and enabled feature providers may process information on behalf of the service, as necessary to provide hosting, authentication, storage, notifications, AI responses, or payment processing.
• Information may be disclosed when reasonably necessary to protect users, investigate abuse, comply with law, or respond to valid legal requests.

Access depends on configuration and authorization rules; choosing a role on a sign-in screen does not itself grant the role's permissions.

6. AI features and external services

If an AI assistant or other AI-powered feature is enabled and you use it, the text or context you submit may be sent to the AI provider configured for that feature so it can produce a response. Avoid including unnecessary sensitive details. AI output can be incomplete or wrong and is not a substitute for human review or professional advice. If Google sign-in or payment checkout is enabled, those services are governed by their own privacy notices and terms.

ShieldMind saved conversations: when you use the paid ShieldMind workspace, the service stores your conversation title, text questions, and text answers in the configured Supabase database so you can search for and reopen previous study sessions. These records are protected by account-ownership database policies. You can delete an individual conversation from the ShieldMind history panel; deleting a conversation also deletes its messages. Conversation records are not shared in CampusPulse or with other students. The text you choose to submit is still sent to the configured AI provider to produce an answer, as described above.

Study images attached to a ShieldMind request may be sent to the AI provider for that individual response, but image files and image binaries are not saved in chat history or CampusShield storage. The saved transcript may include personal information if you type it into a prompt, so do not include student IDs, passwords, incident reports, medical details, or other sensitive information.

7. Retention and security

No fixed, time-based retention schedule was verified in the project materials. Therefore this notice does not promise deletion after a specific number of days. At present, records may remain in the configured services while they are needed to operate accounts, review incidents or identity applications, preserve safety/audit history, reconcile payments, or address security and legal obligations. Backups and provider logs may follow separate service-specific retention settings.

ShieldMind conversation retention: saved conversation text remains in your account until you delete the conversation or the associated account is deleted, subject to any provider backups, legal holds, or other obligations described above. No automatic age-based expiration is implemented for saved ShieldMind conversations.

• Accounts and profiles: no published automatic deletion timeline was verified.
• Safety reports, identity-review records and community moderation: no universal expiration period was verified; retention must be set according to approved safety, review and legal requirements.
• Payment records: retained in accordance with the enabled billing workflow and applicable accounting requirements; no exact period is stated here.
• Push subscriptions: intended to be removed when a user disables the feature or the subscription is invalidated, subject to the configured implementation.
• Hosting, database and security logs/backups: governed in part by the configured service-provider settings, which must be checked in the relevant dashboards.

This is a disclosure of what is currently known, not a claim that a retention policy has been fully implemented. The operator must approve and publish category-specific retention periods, deletion processes, backup windows and exception handling before public production launch.

8. Applicable privacy law and complaints

We take privacy seriously and aim to handle personal information with due regard to applicable data-protection requirements, including the Nigeria Data Protection Act 2023. You may raise a privacy question or make a request using the contact details in this policy. For the official legislation, see the Nigeria Data Protection Commission's NDP Act 2023 page.

CampusShield AI is designed to use authentication, role-based access, database policies and private storage for sensitive submissions. No online service can guarantee absolute security. Never send passwords or secret keys to support.

9. Your choices and requests

You can review or update available profile fields in the app. For access, correction, or deletion requests, contact campusshieldaitechnologies@gmail.com from the account address where possible. We may need to verify your request and may retain some records where required for safety, security, or legal reasons.

10. Emergency limitations

CampusShield AI is not an emergency dispatch service and does not automatically contact emergency services. In immediate danger, contact your campus security control room or the appropriate local emergency service directly.

11. Updates and questions

This policy may be updated as the platform and its services evolve. The current version and last-updated date are shown at the top of this page. For privacy questions, contact CampusShield AI support.