Privacy, by design.

What this does: QC collects only the data needed to run account access, scheduling, and private delivery. We do not sell your personal data or make your moments public.

Why it matters: You can use QC for emotional communication without feeling exposed.

Example: Your message stays in your account context and recipient delivery flow.

What this does: Account details (email, authentication identifiers), moment data (message content, media metadata, delivery timing), recipient contact information (email or phone when provided), and operational logs for security and reliability.

Why it matters: You can clearly see exactly what enters the system and why.

Example: Recipient email is stored only to deliver the intended moment.

What this does: Data is used to authenticate your account, schedule and deliver moments, monitor reliability, and resolve support issues.

Why it matters: Your information is tied to product operation rather than ad targeting.

Example: Operational logs help diagnose delivery failures.

What this does: Moments are delivered through private, time-based access links generated uniquely for each delivery. These links are not publicly indexed or searchable and may be time-limited.

Why it matters: Delivery stays personal and aligned to the exact scheduled context.

Example: A link opens for the intended recipient window and can expire after access.

What this does: QC uses secure authentication systems and tokenized links to help ensure only intended recipients can access a moment.

Why it matters: Account and delivery access are guarded against unauthorized use.

Example: Session controls and scoped link validation block invalid access attempts.

What this does: We do not sell personal data. We do not use your messages for advertising. We do not make your moments public or searchable.

Why it matters: Your emotional content is not converted into marketing inventory.

Example: A private apology is never surfaced in public discovery systems.

What this does: QC uses infrastructure and communications providers to run service operations.

Why it matters: Partners process data only to provide required service functions.

Example: Email delivery provider handles notification dispatch.

What this does: Moments remain associated with your account unless deleted. Delivery access links may expire after a set period or after being accessed. You can request account and associated data deletion at any time.

Why it matters: You have a clear lifecycle for stored moments and delivery artifacts.

Example: A delivered link can expire while your account keeps retained history until deletion.

What this does: You can manage profile, timezone, and notification preferences in Settings, request export or deletion through support, and revoke device permissions at any time in browser or OS settings.

Why it matters: Control over account behavior and data remains in your hands.

Example: Disable browser permissions immediately without leaving your account.

What this does: QC uses minimal cookies and related technologies for secure sessions, product performance, and reliable delivery behavior.

Why it matters: Core functionality works reliably without invasive tracking systems.

Example: Session cookies keep your authenticated context stable across pages.

What this does: QC is designed to meet applicable data protection standards. Users outside the United States may have additional rights based on local law.

Why it matters: Privacy commitments are structured for multi-region responsibility.

Example: Regional requests can include additional access or deletion rights.

What this does: For privacy requests, legal questions, or data-control support, contact our team directly.

Why it matters: You have a direct path for sensitive requests without unnecessary routing.

Example: Email privacy support at vera@qcapp.co for deletion requests.

Recommended layout: Strong opening hero, then anchored legal cards in a clear trust-first sequence.

Continue with the next relevant part of QC.