How MyNORSU Social and MyNORSU LMS handle user information.
This policy explains the information processed through accounts, profiles, social features, LMS activity, uploaded content, technical services, support, analytics, and advertising, together with the available request and deletion routes.
1. Overview
MyNORSU Social provides campus community features such as accounts, profiles, posts, comments, reactions, media sharing, groups, messages, announcements, student services, marketplace activity, jobs, tutoring, and related engagement tools.
MyNORSU LMS supports class-related workflows such as courses, course membership, materials, assignments, submissions, attendance, teacher feedback, grades or scores where enabled, and learning activity records.
Users generally create or access their MyNORSU Social account first and then use the same authorized account for MyNORSU LMS where access is enabled.
2. Platform Operator and Scope
| Item | Details |
|---|---|
| Platform operator | CommunityStack Information Technology Services (CommunityStack) |
| Location | Dumaguete City, Negros Oriental, Philippines |
| Platforms covered | MyNORSU Social, MyNORSU LMS, the public website, launch and access pages, support channels, and connected platform services |
| MyNORSU support | support@mynorsu.social |
| Privacy and compliance coordination | jenifer@communitystack.org |
| Primary access page | https://mynorsu.social/start/ |
3. Information We Collect
The platform may collect or process the following categories of information depending on the features used, the user's role, and the current service configuration.
| Category | Examples | Purpose |
|---|---|---|
| Account data | Name, email address, authentication identifier, login and session information | Account creation, login, support, security, and access management |
| Profile data | Display name, profile photo, role, campus, college, program, section, or department details where enabled | User identification, approval, discovery, and role-based platform access |
| Social content | Posts, comments, reactions, groups, messages, announcements, reports, marketplace listings, jobs, and tutoring activity where enabled | Platform functionality, community interaction, communication, and moderation |
| Media and files | Photos, videos, profile images, course materials, LMS submissions, and attachments | Content sharing, class work, communication, and platform features |
| LMS and academic activity | Course membership, assignments, submissions, attendance, scores, grades, and teacher feedback | Learning workflows, class administration, and authorized academic use |
| Technical data | Device and browser indicators, timestamps, application events, logs, error reports, and IP-related technical records where available | Security, debugging, troubleshooting, abuse prevention, performance, and platform operations |
| Advertising and analytics data | Page views, event data, ad impressions, ad clicks, campaign delivery records, and related technical signals | Service measurement, advertising delivery, reporting, fraud prevention, and operational improvement |
| Support data | Support emails, screenshots, issue descriptions, attachments, and account identifiers supplied by the user | User assistance, issue tracking, verification, and escalation |
4. LMS Data
MyNORSU LMS may process class-related information where LMS features are enabled. This can include course membership, materials, attendance, assignments, uploaded submissions, teacher feedback, manual paper-submission scores, grading information, and related learning activity records.
LMS records may involve academic, administrative, or institutional interests. A request to delete or correct an LMS record may therefore require identity verification and coordination with an authorized faculty member or university representative before a change can be made.
Deleting a user account may not automatically erase records that must be retained for grading, academic administration, security, dispute handling, or institutional accountability.
5. How We Use Information
- To create, authenticate, approve, and manage user accounts.
- To operate MyNORSU Social features, including profiles, posts, groups, media, messaging, marketplace, jobs, tutoring, and communication tools.
- To operate MyNORSU LMS features, including class access, materials, assignments, submissions, attendance, scoring, and feedback.
- To provide user support and respond to registration, login, account, app, or LMS problems.
- To maintain security, detect abuse, investigate suspicious activity, and protect platform integrity.
- To moderate content, review reports, and enforce platform rules.
- To measure service use, diagnose performance problems, and improve functionality.
- To support free access through advertising where advertisements are enabled.
- To comply with applicable legal, operational, security, academic, or institutional requirements.
6. Advertising, Analytics, and Monetization
MyNORSU services are intended to be available without a subscription fee to students, faculty, staff, and authorized users. Operational costs may be supported through direct advertising, third-party advertising, affiliate campaigns, and house promotions where enabled.
Advertising and analytics services may process ad impressions, clicks, page views, application events, device or browser signals, and other technical data used for delivery, measurement, reporting, security, and fraud prevention.
Where advertising services provide category and suitability controls, available restrictions may be applied to reduce mature, sensitive, or unsuitable advertising for a general campus audience. Third-party advertising and analytics providers also operate under their own terms and privacy practices.
CommunityStack does not provide advertisers with direct access to private user conversations or sell user account data to advertisers.
Google AdSense and Google advertising cookies
The public MyNORSU website may use Google AdSense to display advertisements. Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google's use of advertising cookies enables Google and its partners to serve advertisements based on visits to this site and other sites on the Internet.
Google and participating advertising partners may process information such as cookie identifiers, IP-related technical information, browser and device information, approximate location derived from technical signals, page visits, ad impressions, ad interactions, and fraud-prevention signals. Depending on a user's region, consent choices, account settings, and the advertising configuration in use, advertisements may be personalized or non-personalized.
Personalized advertising and opt-out choices
Users may opt out of personalized advertising from Google by visiting Google Ads Settings. Users may also visit AboutAds to manage opt-out choices for participating third-party advertising vendors. Opting out of personalized advertising does not necessarily prevent advertisements from appearing; advertisements may instead be selected using non-personalized or contextual signals.
Users can also manage or delete cookies through their browser settings. Restricting cookies may affect advertising preferences, analytics, saved choices, sign-in behavior, or other website functionality.
Consent and regional privacy choices
Where applicable law or Google policy requires consent, a consent notice or consent-management control may be presented before certain advertising or analytics technologies are used. Available choices may include accepting, rejecting, or managing categories of cookies and related processing. Users can use the displayed consent control to make or update their choices where that control is available.
Google processes advertising information under its own policies. Users can learn more through How Google uses information from sites or apps that use its services and the Google Privacy Policy.
7. Third-Party Services and Processors
The platform relies on third-party services for authentication, databases, storage, notifications, analytics, advertising, app access, web hosting, and support. The following list describes major service categories currently used or expected to be used; providers and configurations may change as the platform develops.
| Service or provider | Role | Data possibly processed |
|---|---|---|
| Supabase | Authentication, database, backend services, and storage | Account data, profile data, social content, LMS records, uploaded files, and media |
| Google AdSense | Advertising on the public website, including ad delivery, measurement, reporting, personalization where permitted, and fraud prevention | Advertising cookies or identifiers, IP-related technical information, browser and device information, approximate location signals, page visits, ad impressions, ad interactions, consent signals, and fraud-prevention data |
| Google AdMob | In-app advertising | Ad impressions, ad delivery events, and ad-related technical identifiers or signals |
| Google Analytics and Google Tag Manager | Website and LMS analytics, page-view measurement, and event collection | Page views, event data, device and browser information, and related technical signals |
| Google Firebase or Cloud Messaging services | Application services and push notifications where enabled | Application instance or notification tokens, delivery events, and related technical data |
| Google Play | Android application listing, installation, updates, and distribution services | Device, account, download, diagnostic, integrity, and related technical information processed under Google’s applicable policies and settings |
| Apple App Store | iPhone and iPad application listing, installation, updates, and distribution services | Apple Account, device, download, installation, diagnostic, and related technical information processed under Apple’s applicable policies and settings |
| Web, domain, and hosting services | Public website, launch page, web app, analytics portal, and LMS access | Basic web access records, technical logs, files, and hosting data depending on configuration |
| Email and support providers | Support, safety, privacy, and compliance communication | Email addresses, message content, screenshots, attachments, and support history |
8. Sharing of Information
Information may be disclosed or made accessible only where reasonably necessary for platform operation, support, security, moderation, legal compliance, authorized academic administration, institutional coordination, dispute handling, or third-party service processing.
Information may also be supplied when required by applicable law, a valid legal process, or a legitimate safety or security investigation. The platform may preserve or disclose information where reasonably necessary to protect users, investigate abuse, or prevent harm.
CommunityStack does not sell user account data to advertisers. Advertising and analytics providers may process technical or advertising-related data through their own systems where their services are used.
9. Data Retention and Deletion
Information is retained only for as long as reasonably necessary for the purpose for which it was collected, platform operations, support, security, moderation, legal compliance, academic recordkeeping, dispute handling, audit requirements, or institutional coordination.
| Data type | General retention approach |
|---|---|
| Account and profile data | Retained while the account remains active and then deleted, anonymized, restricted, or retained as reasonably required after a valid request. |
| Social content | Retained while published or until deleted by the user, removed through moderation, restricted, or otherwise required for a legitimate operational purpose. |
| LMS records | May be retained for academic, administrative, grading, audit, security, or institutional purposes even after an account request. |
| Support and safety records | Retained as needed for issue history, verification, accountability, follow-up, moderation, and dispute handling. |
| Analytics, advertising, and technical logs | Retained according to operational needs, configured service settings, provider policies, security requirements, and reporting periods. |
| Backups | Deleted information may remain temporarily in backups until routine overwrite, expiration, or deletion cycles are completed. |
10. Account Deletion Requests
Users may request account deletion by emailing support@mynorsu.social with the subject line Account Deletion Request.
The request should include the registered email address, the user's full name, and a clear statement requesting deletion. Support may require reasonable identity verification before processing the request.
Deletion may not immediately remove every record. Some information may be retained or restricted where necessary for account security, fraud prevention, support history, moderation, legal compliance, academic records, institutional requirements, backups, or audit logs.
11. Security
The platform uses reasonable technical and organizational measures appropriate to its current services, including authenticated access, secure web connections where configured, database access controls, restricted administrative access, storage controls, support escalation, monitoring, and technical logs used for troubleshooting and security review.
No online platform can guarantee absolute security. Users remain responsible for protecting their passwords, devices, email accounts, and access sessions and should report suspected unauthorized access promptly.
12. User Rights and Requests
Subject to applicable law, identity verification, technical feasibility, academic recordkeeping, legitimate retention needs, and institutional requirements, users may request access to, correction of, deletion of, restriction of, or review of certain personal information.
Ordinary account, app, LMS, and deletion requests should be directed to support@mynorsu.social. Privacy and compliance coordination may be directed to jenifer@communitystack.org.
MyNORSU support handles operational requests. Privacy and compliance coordination handles formal privacy review. Official university records or decisions must be raised with the appropriate university office.
13. Compliance and Institutional Coordination
The platform may coordinate with authorized university representatives, legal counsel, data protection personnel, faculty members, or other authorized offices when a formal privacy, safety, academic, or operational matter requires their involvement.
This Privacy Policy is a public transparency document. It is not a legal certification, legal opinion, or representation that MyNORSU Social or MyNORSU LMS is an official university system. Any formal university adoption, approval, or institutional determination must be established separately through official channels.
14. Changes to This Policy
This Privacy Policy may be updated as the platform, service providers, legal requirements, operational processes, or available features change. Updated versions will be posted on this page with a revised “Last updated” date.
Material changes may also be communicated through the platform, website, email, or another appropriate channel where reasonably necessary.
15. Contact Information
| Purpose | Contact |
|---|---|
| MyNORSU account, app, LMS, safety, and deletion support | support@mynorsu.social |
| Privacy and compliance coordination | jenifer@communitystack.org |
| Public contact and routing information | https://mynorsu.social/contact/ |
| Website | https://mynorsu.social/ |