Operational privacy practices

Reviving aims to evaluate privacy impact during workflow design, implementation planning, and vendor selection rather than treating privacy only as a legal document exercise.

The most important controls are the ones that reduce unnecessary data exposure, define roles clearly, and make it easier for customers to configure workflows responsibly.

Customers decide which data sources are connected, which workflows are enabled, who can administer the tenant, and what contractual posture applies to the deployment.

Reviving supports those instructions and helps route privacy, security, and contract questions to the right function, but the customer remains the primary decision-maker for its regulated data environment.

• Collect the minimum website and sales information needed to respond to a request.
• Limit support access to what is necessary to troubleshoot or deliver the contracted service.
• Apply retention review so records are not stored indefinitely without purpose.
• Treat exports, logs, and backup paths as part of the privacy review surface.

Privacy questions, DPA requests, and customer data-handling questions should be routed through documented channels so legal, privacy, and security teams stay aligned.

Questions can be directed to privacy@reviving.app, while contract-driven requests can be initiated through the contact page or the DPA and BAA trust routes.