Safety and privacy
Keep preserved Simply Plural data private and under your control.
A Simply Plural export can contain deeply private System data. Treat exports, backups, screenshots, notes, avatars, fronting history, and account details as sensitive.
PluralBridge is building toward import preview and member profiles in the browser. Until that path is ready, the safest thing to do is protect what you saved and avoid sharing private data in public or semi-public places.
Core safety boundary
Please do not send PluralBridge passwords, export files, screenshots, private notes, member records, avatar files, fronting history, account details, database files, or other private System data.
Public threads, email, direct messages, GitHub issues, GitHub discussions, screenshots, paste sites, shared folders, and public repositories are not safe places for private System data.
What to protect
- Simply Plural export files.
- Backups of export files.
- Notes and text records.
- Avatar files and image folders.
- Fronting history and timestamps.
- Member profiles, custom fields, groups, privacy buckets, and related records.
- Screenshots that show private System information.
- Passwords, account details, or copied authentication values.
- Generated database files, logs, reports, or test files made from real System data.
If you already exported
- Keep the export somewhere private and under your control.
- Make at least one backup copy somewhere safe.
- Keep the export out of GitHub repositories, public folders, screenshots, paste sites, and public support threads.
- Remember where the export is stored so you can use it when PluralBridge import preview is ready.
- If a helper kept a copy, decide whether that copy should be deleted or returned to you.
How to ask for help safely
A useful support question can describe the situation without exposing private data.
- Say which public page you were reading.
- Say what kind of help you need.
- Say what browser or operating system you are using if that matters.
- Describe the general error or confusion without copying private records.
- Ask how to describe a problem safely before sending details.
Do not attach exports, screenshots, notes, avatars, copied member records, logs from real data, database files, .
Contributor safety rules
Contributors should use synthetic data for examples, tests, fixtures, screenshots, documentation, and pull requests.
Do not use real System exports in public issues, discussions, commits, tests, examples, sample databases, documentation, screenshots, or bug reports. Redaction must remove private values, stable identifiers, account details, and anything that could expose a real System.
Future import safety
PluralBridge import work should be deliberate and reviewable. The intended direction is that users can inspect a preserved Simply Plural export before anything is saved into PluralBridge.
Import should respect privacy, user ownership, membership boundaries, and clear control over who can see or change System data.
Project boundary
PluralBridge is an independent project. It is not affiliated with Simply Plural, Apparyllis, or the Simply Plural development team.
PluralBridge does not need your private data to prove that the project matters. Keep your data safe.
PluralBridge will be a free service at no cost to the plural community. Please do not send us money. 😂
Where to go next
If you already exported, keep your export private and backed up. If you want to follow what PluralBridge is building, use the browser release page. If you want to help, start with Help Build and keep real user data out of public project spaces.