Privacy policy

1. Who is responsible

PacketShield is the name used for this website preview. A legal business name, postal address, country of establishment and privacy contact are not yet available. No privacy email or registered company is being represented here. These details must be published before the preview is offered as a commercial service.

2. Information handled by the preview

• Website requests. The hosting and delivery platforms may process your IP address, request URL, browser information, timestamps and technical security logs to deliver and secure the website.
• Account registration. Google or Apple supplies a provider account identifier and any email address or name you authorize it to share. PacketShield stores an account and the linked provider identifier in its application database. It does not receive your provider password or retain provider access, refresh or identity tokens.
• Account session. An encrypted, necessary session cookie identifies your registered account. The server checks that account before allowing checkout.
• Customer panel. When you save a service draft, the application stores its name, protection type, hostname or IPv4 address, integration method and creation time against your registered account in its database. Drafts are visible only to that account and can be removed in the panel. Saving a draft does not activate protection. Use example endpoints during the preview.
• Browser preference. If you save cookie settings, this browser stores a necessary-only preference with the time saved and an expiry time. It is not sent to a marketing service.
• Example checkout. After registration, the order form sends the selected plan, billing interval, example hostname or IPv4 address and integration method to the website checkout endpoint. Use example data only. Do not submit credentials, payment details, personal identifiers or confidential infrastructure information.
• Payment return. If a Stripe session exists, the return page sends its session identifier to the website to verify payment status. A success URL alone is not treated as proof of payment.

This application has an account database for registration. It has no contact form, newsletter, installed analytics script or advertising pixel. The fonts are served from this site. Sample order fields are kept in page memory while you use the form.

3. Purposes and legal bases

Technical information is used to deliver the requested pages, prevent abuse and diagnose faults. Account information and necessary session cookies verify your identity and require registration before ordering. The cookie preference is used only to remember a choice you explicitly save. Example order data is used to demonstrate configuration and the checkout flow. Service drafts let you save and retrieve configuration details in your customer panel.

The operator must identify and document the applicable legal bases before launch. Where relevant, these may include legitimate interests in site security, steps taken at a user's request before a contract, and legal obligations for genuine transactions. This draft does not assume that one basis covers every activity. Optional tracking is not installed, and saving a necessary-only choice does not give consent for future tracking.

4. Providers and sharing

The public website is prepared for Netlify hosting. Login and the customer panel continue to use Sites hosting with a Cloudflare Workers runtime. See Netlify's privacy policy. Hosting and security providers may handle request information according to their roles and policies. See OpenAI's privacy policy and Cloudflare's privacy policy.

Account registration redirects to the provider you choose. See Google's privacy policy and Apple's privacy policy. Google sign-in is configured on the hosted customer panel. Apple sign-in is not configured yet.

Stripe checkout is implemented but has not been enabled. If it is enabled for testing, the checkout request sends your account identifier, account email and example plan, asset and integration metadata to Stripe. A checkout status request must belong to the signed-in account. Stripe collects payment and billing information on its own hosted page. Card details are not collected in this site's form. See Stripe's privacy policy.

The application does not sell personal information or share it for behavioral advertising. Provider roles, agreements and any legally required disclosures must be verified for the final service.

5. Retention

Unsaved form choices are held in page memory. Saved service drafts remain in the database until you remove them from the panel or the operator deletes them. Removing a draft deletes that application record, but provider backups may retain it according to their schedules. Registration records remain in the application database until removed by the operator. Automatic account deletion and a customer deletion interface are not yet implemented, so a final account retention and deletion process must be established before launch. Account sessions last up to seven days and are cleared when you sign out. Short-lived sign-in checks expire after fifteen minutes. Signing out does not delete your account. A saved browser cookie preference expires after 180 days. It is removed the next time cookie settings are opened after expiry, or when you choose to remove it.

Hosting logs and any Stripe records are subject to provider settings and applicable requirements. Their exact retention periods have not been configured or audited for this preview. A retention schedule for site logs, support, billing and mitigation data must be established and reflected here before launch.

6. International processing and security

Providers may process information outside your country. The operator must confirm relevant processing locations, contracts and transfer safeguards before live operation. This draft does not claim that a particular transfer mechanism has been put in place.

The website uses HTTPS on its hosted address and performs checkout validation on the server. Those measures do not amount to a guarantee that information can never be lost, accessed unlawfully or disclosed. No real traffic is routed through this preview.

7. Your choices and rights

You can browse plans without registering. Registration or sign-in with Google or Apple is required before ordering. Signing out ends your current PacketShield session. You can open Cookie settings in the footer to save or remove the browser preference. Browser controls can also clear site storage.

Depending on applicable law and the processing activity, rights may include access, correction, deletion, restriction, portability and objection. Where processing relies on consent, you may withdraw that consent. You may also have the right to complain to a competent data protection authority.

A working contact for requests and complaints must be added when the operator is established. There is currently no PacketShield privacy mailbox. For information handled independently by a hosting or payment provider, use that provider's published privacy channels.

8. Children and changes

The preview is not designed to collect information from children. Do not submit personal information about children through the example form.

This notice will be revised when the operator, providers or data flows change. If the service launches, the notice must also explain final account retention, support, actual mitigation traffic and billing. The revision date appears above.