Security & Trust
Last updated October 11, 2026
Greek Central uses authenticated access and server-enforced permissions around real chapter and institution responsibilities. These are the controls implemented in the product, not a certification or promise that every risk has been eliminated.
1.Access follows responsibility
Protected actions validate the user session and current permissions. Chapter records use workspace and record-level controls; office teams have scoped access. Personal identity remains separate from positions, and last-admin safeguards protect leadership handoffs. Application approval and platform operations are separately authorized.
2.Chapter confidentiality
Prospects do not receive internal notes, ratings, stages or ballots. Conversation access follows participants, and sensitive fields follow purpose-specific permissions. Education and program records and their derived metrics remain available only to authorized chapter users—not routine office/team/national sharing, sponsorship, public pages or standard support.
3.Timed, visible support
Platform support entry requires an authorized owner, a reason and an expiry. The session and actions are audited and a notice is shown to the customer. It never creates real membership or sharing consent. Education and program data remain excluded. Legal or safety requests use a separate scoped review, not ordinary account privileges.
4.Private files and authentication
Uploads use private storage and short-lived authorized download links. Supported file type, signature and size checks are not malware or antivirus scanning. Password handling is supplied by the authentication provider; Greek Central does not expose readable passwords. Connections use HTTPS. Messages are not end-to-end encrypted.
5.Payments and consent
Stripe hosts payment-credential collection. Software subscriptions, chapter dues and institutional registration fees keep separate records and recipient contexts. Provider-confirmed events govern online completion. Autopay requires member consent, fee-inclusive caps, advance exact-amount notice, current eligibility and atomic reservations. Live autopay is off; test-mode UI is not proof of provider production readiness.
6.Voting and AI safeguards
Voting eligibility, timing and configured ballot/result visibility are enforced server-side; role assignment stays separate from a result. Milo’s allowlisted tools use the requester’s permissions and confirmed actions; prompts cannot grant arbitrary database or cross-workspace access. Review AI output before relying on it.
7.Operational limits and reporting
We do not claim SOC 2 certification, independent audit completion, antivirus protection, end-to-end encryption, guaranteed backup restoration or uninterrupted uptime. Scheduled jobs and emails depend on service configuration and provider availability. Report a suspected issue without including passwords, payment credentials or other people’s unnecessary private records. For immediate danger, contact emergency services; this is not a 24/7 emergency channel.
8.Contact
General questions: hello@greek-central.com. Account support: support@greek-central.com. Billing: billing@greek-central.com. Privacy requests: privacy@greek-central.com. Security reports: security@greek-central.com.
Questions about this page? Contact us and a person on our team will reply.