pifamy

Care for what you share

Security and safety

Privacy needs clear boundaries and careful everyday operation.

Safeguards we use

Pifamy uses encrypted transport, private media storage, audience and authorization controls, account/session protection, limited server permissions, operational monitoring and encrypted off-site recovery copies.

Messages are not end-to-end encrypted. Necessary service systems can process content, and legitimate safety review is scoped to relevant reports. Private does not mean absolute secrecy or a guarantee against every incident.

A restrained notification design

Device Push is being prepared and is not yet active in the live service. It requires your explicit Enable action and operating-system permission. The prepared payload is a generic notification without message text, Family names or media URLs. It is not a guarantee of delivery.

Protect your account

Keep your email account and phone secure, do not share sign-in codes, and keep invitations within their intended audience. Review media metadata before uploading if location or device details matter to you. Recipients can retain independent copies.

Report a concern

Contact . Describe the issue and the relevant app action without sending secrets, unlawful material or unrelated private content. Do not probe other people’s data or disrupt the service. For immediate danger, contact emergency services.

For data-rights requests, use . General help is at . We do not promise continuous monitoring or a fixed response time; applicable legal duties still apply.