Built by
Students
Designed from the student side of the table; actively shaped by real campus feedback.
Built by students, for higher education
Pliqd for higher education.
Students get a verified campus app for study, chat, community, and peer connection. Your student-affairs and IT team gets a real administrator portal — with user oversight, report handling, announcement tools, and engagement analytics scoped to your university.
Adoption model
Pilot-first
We deploy with a cohort and measure before scaling to full enrollment.
Eligibility
Verified .edu only
Every account is gated by a valid institutional email on sign-up.
Why institutions invest
See disengaged students before they stop showing up.
First-year attrition is rarely academic — it's isolation. A student who doesn't form peer connections, skips orientation, and stops engaging with campus life often withdraws before anyone catches it. Every returning first-year is $20K–$50K+ of tuition your institution keeps. Pliqd gives student-affairs a live signal of who's disengaging, and a lightweight workflow to intervene while it still matters.
Early-warning signals
Orientation modules not completed. Zero peer connections formed. No groups joined. Campus announcements consistently unread. These are the quiet signals that usually only surface at a midterm grade report. Your Pliqd dashboard surfaces them in week one.
Intervention workflow
Export the at-risk list from orientation analytics with one click. Use the pre-filled outreach template, or push a targeted campus announcement and see who actually read it. Track what worked semester over semester.
Pre-arrival belonging
Incoming students connect with their roommates, their major, their orientation group before they step on campus. The single biggest predictor of first-year retention is whether a student forms meaningful peer connections in the first six weeks. Pliqd compresses that timeline.
Commuter & transfer integration
The populations with the highest attrition risk are commuters and transfers — the ones who don't live in residence halls and miss the passive community-building. A campus-gated app levels the playing field: they find their people without needing to be physically present at every event.
Well-being signal
Reports of harassment, isolation, or unsafe situations flow through the same queue your conduct office already uses. Patterns that would normally live in siloed channels — residence-life complaints, Title IX, counseling — get a single surface so your team can connect the dots.
The math
At an institution with a 15% first-year attrition rate and 2,000 first-years, moving the needle one point back means ~20 students retained. At ~$30K tuition each, that's $600K/year to the institution's top line — before counting the housing, meal plan, and four-year lifetime value.
Honest note: we're a new platform — we haven't yet published a longitudinal retention study. That's exactly why our pilot model co-defines the metrics with you and does a joint readout at the end. If the data doesn't support the hypothesis, we tell you.
What's inside
Academic and community tools, in one verified space.
Students get a single place to study together, find classmates, share campus information, and stay connected — gated by institutional email so the community stays authentic.
AI Study Bots
Course-scoped AI tutors students (or TAs, or faculty) can create by uploading syllabi, slides, and past exams. Offloads repeat questions from tutoring centers and office hours.
Study groups & research collabs
Students form course-specific study groups and cross-discipline research teams, share notes, and run group chat and file exchange within the app.
Campus feed
A community feed where students post announcements, events, housing, and jobs — contained to the verified community, unlike open social platforms.
Smart peer connection
Connects classmates by major, year, and shared courses. Supports first-year integration, transfer onboarding, and commuter-student community building.
Messaging & group chat
Text, voice notes, image, video, and PDF messaging with moderation hooks. All communication stays inside the verified community.
Peer networking (Spark)
A consumer-facing dating/peer-matching surface is part of the student experience. Institutions can discuss cohort-level settings during pilot onboarding; we're open to institutional preferences on visibility.
Your administrator portal
Pliqd gives universities admin control. We run the platform.
Partner universities get a web portal for their student-affairs, conduct, and IT teams. Your admins see and act on data scoped to your institution only — Pliqd runs cross-university operations separately. Below is what's actually in the university admin portal today, not what's on a roadmap slide.
Dashboard
At-a-glance view of total users, active reports, active bans, and active groups on your campus, plus an activity chart and live report feed.
User oversight
Search and filter your campus users. Issue warnings, suspend, or ban with a documented reason. Export the full list to CSV.
Reports queue
Student-submitted reports (harassment, spam, inappropriate content, fake profiles) flow into a triage queue. Resolve with dismiss, warn, or ban — with internal notes.
Bans with scope
Bans can be temporary or permanent and scoped: platform-wide, Spark-only, messaging-only, groups, or events. Revocable with an audit trail.
Campus announcements
Publish general, urgent, event, career, or Spark-related announcements. Pin, schedule expiration, and see read stats — including which students have read each one.
Orientation modules
Create required video, quiz, form, activity, or social modules. Track completion rates, identify at-risk students, and export the list with a pre-filled outreach template.
Campus jobs board
Post part-time, full-time, internship, or contract roles with pay, hours, and deadlines. Track applicants through applied → viewed → interviewing → offer → accepted.
Group governance
Review student-created groups. Verify legitimacy, mark groups as "official," or suspend. Filter by type, privacy level (public / private / secret), and status.
Engagement analytics
Active users, messages sent, Spark matches, engagement rate, and feature-level usage breakdowns — over a configurable 7 / 14 / 30 / 90-day window.
Team & role permissions
Invite additional campus admins with granular permissions: manage users, manage content, manage events, manage groups, view analytics, manage reports, invite members, manage settings. Revocable invitations.
Institutional scope: everything above is scoped to your university. Your admins don't see data from other institutions. Cross-university moderation, platform feature flags, and pricing are handled by Pliqd's platform team — kept separate by design.
Safety & moderation
Built for campus community standards.
We take safety seriously — both the technical controls and the human review process. The public-facing detail lives on our safety page; below is what partner institutions ask about most.
.edu gating
Every account is verified against an institutional email on sign-up. No .edu, no account.
In-app reporting → your queue
Students report users, messages, and posts by type (harassment, spam, inappropriate, fake profile, other). Reports land in your admin queue filtered by status: pending, investigating, resolved, dismissed.
Warnings, suspensions, scoped bans
From a report, your admins can issue a warning (with severity and acknowledgment tracking), suspend, or ban — with ban scope limited to platform, Spark, messaging, groups, or events. All actions audited.
Pliqd platform backstop
Pliqd's platform operators keep a cross-university safety console — so critical issues with platform-wide reach (coordinated abuse, CSAM, legal requests) get handled centrally and routed to the right university.
Block, mute, restrict
Students control who can contact them. Blocked users are mutually invisible across feed, chat, and matching surfaces.
Minor protection
Date-of-birth gating and feature restrictions for users under 18. Dating features are unavailable to underage accounts.
Privacy & identity
Transparent about what we do and don't have.
We'd rather tell you where we are than oversell a compliance badge. Full privacy policy is here; this is the procurement-office summary.
Data minimization
We collect what's needed to run the product — name, institutional email, date of birth, and the content students create. We don't ingest institutional SIS data.
Student-owned data
Accounts belong to the student, not the institution. Students can export or delete their account and content at any time via in-app controls.
Cloud and encryption
Infrastructure on major US cloud providers. TLS in transit, encryption at rest for backend storage. Authentication tokens stored in device secure storage / keychain.
FERPA posture (aligned, not certified)
Pliqd is a student-facing consumer service — not a school official under FERPA in the typical sense — but we handle student records in line with FERPA principles: data minimization, transparency, student consent, and the right to delete. Happy to walk institutional counsel through specifics.
SSO (SAML / OIDC) — on roadmap
Today we verify identity via institutional email. Full SAML / OIDC SSO against campus IdPs (Okta, Azure AD, Shibboleth) is a roadmap item we prioritize for partners with that requirement.
SOC 2 / compliance attestations
We do not yet hold a SOC 2 Type II report. We can share our current security controls document under NDA and prioritize attestation for institutional partners.
Student outcomes we care about
The questions we'd like to help your campus answer.
We're not going to claim retention lift in a brochure. What we will do is co-define measurable outcomes with a pilot cohort and report back honestly — whether the data supports the hypothesis or not.
Hypothesis
Does peer-to-peer connection pre-arrival reduce first-year isolation and flight risk?
Hypothesis
Do AI study bots reduce load on tutoring centers while improving gateway-course outcomes?
Hypothesis
Does a verified campus-only feed reduce student reliance on anonymous / unmoderated platforms?
Hypothesis
Does in-app study-group formation drive meaningful increases in collaborative study hours?
How a pilot works
Low-risk path to a real answer.
1
Scoping conversation
45-minute call with student-affairs / IT leadership. We walk through the product, security posture, and outcome hypotheses. Honest on gaps.
2
Cohort pilot (a semester)
We roll out to a defined cohort (e.g. a residence hall, a first-year class, a specific college) with agreed success metrics upfront.
3
Joint readout
At the end of the pilot we share what worked and what didn't. Scale, adjust, or part ways — your call, no lock-in.
Questions institutions ask.
Is Pliqd free for students?
Yes. The core student experience is free. Premium features exist on a consumer-subscription basis, similar to other consumer apps.
Does the institution pay, and what does it get?
Pilots are currently offered at no cost. Institutional partners get access to the admin portal described above — user oversight, report handling, announcement tooling, orientation modules, jobs board, engagement analytics — at pilot pricing. Post-pilot commercial terms are set transparently based on what we build together; we'll share our current pricing sheet on request rather than publish a placeholder tier on this page.
Can students be forced to use Pliqd?
No. Pliqd is opt-in. Students choose to sign up, and they control their account and data. Institutions can recommend but not mandate enrollment.
What can institutional admins actually see?
The same data a student-conduct office would reasonably need to investigate a report: the user list for your campus, the reports filed against users, message context inside a report, and orientation-completion status. Your admins do not see private DMs outside a report, swipe history, or Spark activity. They do not see any data from other institutions. Platform-wide moderation sits with Pliqd, not with any single university.
What about the dating / Spark feature?
Spark is a peer-matching surface restricted to 18+ verified students. It's opt-in at the user level. We're open to discussing cohort-level visibility controls during pilot design if that matters for your institution.
What's your track record?
Pliqd is new. We're in early pilots and not going to claim a reference list we don't have — we'd rather earn it. If that's a dealbreaker for your institution, we completely understand; if not, we'd love to talk.
Want the long version?
We'll share our security controls document, roadmap, and pilot framework on request. Real answers, no gated webinar.