Safety and Reporting Policy

# Via Sanctum Safety and Reporting Policy

Last updated: 12 March 2026

Via Sanctum is a Catholic study app with optional, controlled community event features, operated by Tony Kero in New South Wales, Australia.

## 1. Scope
This policy explains how Via Sanctum handles safety reports for event listings, profiles, host-application misuse, and related account activity.

## 2. Report channels
Reports can be made through:
- in-app `Safety report` or `Contact Safety Team` actions where available;
- safety email fallback: safety@viasanctum.app;
- support email: support@viasanctum.app.

## 3. Triage and response targets
- Report acknowledgement: immediate in-app confirmation where applicable
- Initial triage target: usually within 24 hours, subject to staffing, weekends, public holidays, and incident volume
- High-risk reports: temporary action may be taken where reasonably needed before review is completed

## 4. Adults-only underage workflow
Via Sanctum is for users aged 18 and older only.

For suspected underage accounts:
- reports are prioritised;
- temporary restrictions may be applied during review;
- confirmed under-18 accounts may be removed;
- accounts for users under 16 are explicitly blocked at signup;
- repeated underage signup attempts trigger a temporary device-level signup cooldown.

## 5. User safety controls
Available safety controls may include:
- reporting event listings or profiles;
- blocking users;
- muting users;
- hiding event listings from personal view;
- internal moderator-admin actions on host applications and event listings.

Current release clarification:
- Via Sanctum does not provide in-app direct messaging, event chat, comments, reactions, or open public posting feeds.

## 6. Evidence logging and retention
Reports and moderation records may include:
- timestamp;
- report target;
- report reason;
- reporter details;
- submitted content or attachments;
- review notes and action status.

Moderation evidence logs may be retained for up to 12 months, or longer where reasonably required for incident handling, legal compliance, or safety purposes.

## 7. Escalation
Severe safety incidents may be escalated to internal incident-response handling.

Privacy or security incidents may also be handled under internal incident response and data breach procedures. Where required by applicable law, affected users and regulators may be notified.

## 8. Contact
- Safety fallback: safety@viasanctum.app
- Support: support@viasanctum.app