Privacy policy

1. Data We Process

Filezhare, Inc. ("Filezhare"), a Delaware C corporation, is responsible for this service and the personal data described in this policy. We process account identifiers (such as email), uploaded files, folder metadata, share-link metadata, and download logs (including timestamp and IP address).

If you use paid features, we also process plan and subscription status, Stripe customer and transaction identifiers, payment amounts and currency, invoice details made available to us, and records of subscription terms or consumer acknowledgements. Stripe Checkout and Link collect and process the payment, billing-location, and tax information needed for the transaction; Filezhare does not store your full card number.

If you use the online subscription-withdrawal function, we process the name and account email you confirm, contract and provider references, your statement, timestamps, acknowledgement-delivery state, and cancellation or refund outcome. We use these details to acknowledge the request, prevent another renewal, carry out provider actions, answer disputes, and preserve evidence of what you asked us to do.

To operate transactional email safely, we process provider delivery identifiers and delivery events such as sent, delivered, delayed, failed, bounced, complained, or suppressed. Filezhare stores only a keyed, non-readable digest of the recipient address in its delivery and suppression records, not the raw address from the provider event.

2. Why We Process Data

Data is processed to provide storage and sharing functionality, apply service limits, prevent abuse, maintain security, administer subscriptions, verify payments, provide invoices, calculate applicable taxes, reconcile billing records, and meet legal and accounting obligations.

3. Retention

Files and metadata remain available while your account is active unless deleted by you. Deleted data is removed from active storage through Trash and is scheduled for permanent deletion after 30 days. Temporary ZIP downloads are scheduled to expire after 24 hours. A confirmed account deletion disables the account and active share links immediately and schedules account files for permanent deletion after 30 days. If a service-provider backup contains residual metadata, it ages out under that provider's backup-retention schedule and is not restored as active customer data.

Owner-visible Drive activity is retained for up to 12 months. A recipient network address used for abuse prevention is removed from activity records after 30 days. Terminal ZIP-preparation and delivery-attempt metadata is retained for up to 30 days; live delivery-attempt progress does not store the recipient's IP address and identifies them only as an anonymous link visitor. Generated ZIP files normally expire after 24 hours. Monthly aggregate download totals may be retained separately where needed to operate plan limits, resolve disputes, and keep required billing records.

Minimal transactional-email delivery and signed event records are retained for up to 90 days. A non-readable address digest may be retained longer after a spam complaint, permanent bounce, or provider suppression so that Filezhare does not continue sending to that address. Temporary delivery delays do not create a permanent suppression record.

Hashed, single-use account-action credential records are scheduled for deletion 30 days after they expire. This includes the pending address attached to an email-change request. Recent issuance timestamps remain during that limited period so Filezhare can enforce resend abuse limits; the usable credential itself is never stored in readable form.

Billing and transaction records may be retained after a subscription or account ends when needed for accounting, fraud prevention, dispute handling, or a legal retention obligation. Retention periods depend on the record and applicable law.

After a withdrawal request is resolved or rejected, Filezhare normally removes the readable consumer name, email, and raw Stripe or Link references from its withdrawal queue within 180 days. It keeps non-readable reference digests plus the statement version and text, timestamps, status, and outcome for the applicable billing-record, dispute, and legal-retention period. An unresolved request remains in the operational queue with the minimum readable details needed to finish it, even if account deletion has been requested; those readable details are minimized after resolution. Filezhare does not disable an account while an eligible completed contract remains inside its 14-day online statement window unless the statement has first been durably recorded; an active subscription must also have confirmed cancellation. A legal hold or a mandatory recordkeeping rule may require a longer period.

4. Deletion Requests

You can delete files and folders directly in the app and request deletion of your account from Account settings. We send a confirmation link to the email connected to the account before disabling it and starting the published deletion period. If you cannot access your account, contact support@filezhare.com from the address connected to it. You can also download a copy of your account metadata from Account settings before deletion. Account deletion does not silently erase an unresolved subscription-withdrawal request or prevent required cancellation and refund processing.

5. Security Measures

We use authenticated sessions, request abuse controls, and upload validation. No system is perfectly secure; keep your password confidential and use strong credentials. Report suspected vulnerabilities or abuse to support@filezhare.com.

6. Cookies and Local Storage

Filezhare uses a secure session cookie to keep you signed in. The app may also store limited account and interface preferences in your browser so pages load consistently. We do not use advertising cookies.

7. Service Providers

We use Render for the application, cleanup worker, database, and session infrastructure; Cloudflare Workers and R2 for direct shared delivery plus private file and generated download storage; Netlify for the public website and DNS; and Resend to deliver account and billing messages. These providers process data to deliver their contracted services to Filezhare.

Stripe processes checkout, payment methods, recurring charges, invoices, refunds, disputes, tax calculations, and customer billing-management activity. For eligible Managed Payments transactions, Sold through Link, LLC acts as merchant of record and sends the official payment receipt or invoice. Stripe's and Sold through Link's notices explain how they process data as payment and financial-services providers. A customer-data deletion handled through Onelink may cancel the associated Managed Payments subscription and delete related Stripe billing objects; Filezhare separately retains only records it must keep for service, fraud prevention, accounting, dispute handling, or legal obligations.

8. Your Privacy Rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data, and to complain to a data-protection authority. Some records may need to be kept when required by law or to establish, exercise, or defend legal claims.

9. Contact

For privacy inquiries or account requests, contact Filezhare, Inc. at support@filezhare.com or +1 (302) 487-8557. Our mailing address is 111B South Governors Avenue, Suite 92766, Dover, Delaware 19904, United States.