Public clarity without institutional exposure.
Replica separates information intended for public product discovery from information created inside authenticated institutional workflows.
Private Matters, Sessions, participants, votes, documents, evidence and organization administration are not intended to become public merely because Replica has a public website.
Different information serves different purposes.
Identity information
Information required to create and secure an account and identify authorized users.
Organization information
Memberships, roles, settings and context required to operate an institutional workspace.
Meeting information
Sessions, participants, agendas, actions, decisions and associated operational records.
Documents & evidence
Materials intentionally supplied to the platform as part of institutional work.
Technical information
Security, application and service metadata required to operate and protect the platform.
Discovery pages are not the institutional workspace.
Search engines and public visitors may access pages explaining Replica, its capabilities and its public policies.
Authenticated institutional content is handled separately. Public metadata, public sitemaps and marketing discovery surfaces should not intentionally enumerate private tenant records.
Some data exists because secure applications require it.
Replica may process session identifiers, security events, connection metadata and other technical information necessary to authenticate users, protect workflows, operate realtime features and diagnose failures.
This operational information should be treated differently from public product analytics or marketing content.
Realtime services receive only the context they need.
Live meetings and collaborative documents require temporary connection information.
Replica can issue scoped credentials for media or collaborative editing rather than exposing permanent infrastructure secrets to participants.
Institutional records may have different retention requirements.
A meeting record, security log, document version and temporary technical session do not necessarily require the same retention period.
Retention should follow the purpose of the record, organization policy, contractual obligations and applicable legal requirements.
Privacy requests need institutional context.
Requests involving institutional records may require verification of identity and authority before information can be accessed, corrected, exported or removed.
This prevents one participant from using a privacy request to obtain or alter records they are not authorized to control.
Optional analytics and the contact map.
When configured, optional Google Analytics is restricted to public product pages. With consent required, it loads only after you choose Allow. Use Analytics preferences to reject or withdraw consent. Replica's custom events describe public feature views and contact or access-link clicks; they do not include meeting records, vote selections, uploaded documents or account content. Public page locations use the canonical URL without query parameters.
The Contact page embeds Google Maps to show Morogoro, Tanzania. Loading that map makes a separate request to Google and is independent of optional analytics. The map indicates a city, not a precise office address. Phone, email and Instagram links open the service you choose.