Security & Privacy FAQ

Frequently asked questions about how NowToPrint protects your data and privacy.

Data Security

Is my data safe?

Access to protected account and organization data is checked at server boundaries. Authentication, active membership, resource scope and effective permissions are separate checks. Use HTTPS and keep sign-in credentials private. This guide does not certify every deployment or promise a single encryption algorithm for all storage and transport.

Browser PDF processing can keep the document local. Explicit server processing, order attachments, approval links and shared reports have different transfer and access boundaries; inspect the action before sharing a file.

How long are my designs stored?

Retention depends on the record, legal obligations and the applicable deletion policy. There is no verified blanket promise here of indefinite active storage, 90-day drafts, one-year order storage or a 30-day recovery window. Keep your own source copy and export important data before requesting erasure.

Account Security

Where can I enroll or use a passkey?

The current onboarding and Profile surfaces do not mount passkey enrollment or management controls. Do not follow an older guide to a nonexistent Your passkeys section. Follow the authentication methods actually offered on the current screen.

How does multi-factor authentication work?

MFA is disabled in the current launch configuration. Reviewed sensitive business actions require recent primary sign-in; a page or session refresh does not renew credential authentication time. Follow the sign-in prompt if your authentication is too old.

A stricter policy can require user-verified WebAuthn proof. Under that policy, TOTP or Google sign-in alone does not satisfy phishing-resistant proof. This is a conditional policy, not a claim that launch accounts must enroll TOTP.

What if I lose my authenticator app?

Use the verified support channel. Where privileged MFA recovery applies, separate authorized actors must request and approve it. Successful recovery revokes application and Firebase refresh sessions, removes the old factor and requires secure enrollment again. Do not give support passwords, codes, cookies or tokens.

I forgot my password. What do I do?

Select Forgot password on the sign-in page.
Enter the account email. The response remains generic whether or not an account exists.
Open the reset link and choose a new password of 8–128 characters, including uppercase and lowercase ASCII letters, a digit and a punctuation/symbol character.
Sign in again. Existing sessions are revoked when the credential change completes.

How is my personal data used?

Read the Privacy Policy for the applicable purposes, recipients and rights. Account, contact, business, billing, order and security records serve different purposes. Do not infer a processor list, anonymous-only analytics or a certification from this FAQ.

Share only the job and contact information required for the chosen workflow. An order attachment or approval link deliberately transfers or shares information; a local PDF inspection does not by itself authorize that transfer. Card checkout and automatic refunds or payouts are not current public payment capabilities.

Profile offers personal-data export and an erasure request. These controls still require authentication, authorization and the current security checks. Erasure is subject to the inventory, worker availability and retention rules described below.

How do you use cookies?

Necessary storage supports authentication and the site's operation. Analytics and marketing are separate choices in the cookie panel; neither should be inferred from a Preferences-page switch. Use Cookie Settings in the footer to review or withdraw your choices.

The consent record is stored locally with its time and policy version and expires after six months. When analytics consent is withdrawn, the implementation removes Google Analytics cookies and reloads the page. The configured GA cookie lifetime is 395 days; this is separate from consent expiry. For the detailed inventory and durations, read the Cookie Policy.

--------------- | ------------------------------------- | -------- | | Essential | Session management and authentication | Session | | Analytics | Anonymised usage statistics | 1 year | | Preferences | Language and theme settings | 1 year | | Marketing | Ad optimisation (opt-in only) | 90 days |

You can update your cookie preferences at any time using the Cookie Settings button in the site footer.

Deleting Your Account

How do I delete my account?

Open Account Settings

Open Profile and find the account security card.

Request deletion

You must be signed in. The app creates a 15-minute confirmation request bound to your own account.

Confirm deletion

Complete the current authentication confirmation requested for your account, then confirm the matching deletion request. Recent sign-in method changes can delay or prevent automatic confirmation. A missing, expired, or mismatched request is rejected. The request is protected by your session and browser CSRF token.

Warning: Account deletion cannot be undone. After confirmation, access is revoked and a resumable deletion process removes the approved personal-workspace inventory. A legal hold can pause erasure until the hold is released.

Deletion progress is checkpointed against a versioned, approved data inventory. Profile identifiers are replaced with a non-reversible privacy-domain pseudonym; authentication sessions, linked accounts and passkeys are removed through the separate identity lifecycle. Records that must be retained for legal, tax, fraud-prevention or dispute obligations are excluded until their approved retention period ends. This controlled path is available only when the production lifecycle worker and retention policy have been activated.

What gets deleted:

Profile personally identifiable fields are cleared and the account is marked deleted
User documents
Studio designs
User preferences and themes
RFQs created by the user
Producer eligibility redress submissions and their evidence references

What is anonymized or retained under policy:

The principal profile is replaced with a non-reversible privacy-domain pseudonym
Minimum IAM/security audit and identity-lifecycle evidence may be retained to prove compliance and prevent abuse

What is retained (legal obligation):

Invoices and transaction logs required for tax, accounting, fraud prevention, or dispute handling
Order and payment records that must remain available for legal or financial compliance

Can I delete individual designs without closing my account?

The current account Profile page does not provide a design-list bulk-deletion control. If a particular library or file surface offers deletion, use its own confirmation and scope. Removing a local browser file, a personal library entry and shared organization content are different operations. Do not assume any of them erases financial records or every shared copy.

Contact & More Information

Where is the Privacy Policy?

The full Privacy Policy is available at Privacy Policy and linked in the site footer.

How do I contact the data protection team?

Use the contact channel in the Privacy Policy or Contact. Include the account email and request reference when appropriate; never include authentication secrets. Applicable legal deadlines depend on the request and jurisdiction, rather than a guaranteed support turnaround in this FAQ.

What happens in the event of a data breach?

Incident handling and notification follow the applicable legal and operational obligations. Authority notification, individual notice and any public report depend on the incident and jurisdiction; a universal promise to notify everyone within 72 hours is not supported here.

General FAQ

Common questions about the platform.

Billing FAQ

Questions about invoices, payments, and subscriptions.

Technical FAQ

Technical questions and troubleshooting.

Authentication

How sign-in and 2FA work.

Can I manage my registered passkeys?

There is currently no passkey-management card mounted in Profile. If access to an existing authentication method needs correction, use the verified recovery channel. Do not send credential IDs, private authentication material or tokens.