Legal
Privacy Policy
How we collect, use, and protect your information across Krevo.
Submit a privacy request01Introduction
Krevo operates Cloud file storage, an authenticated client portal, public marketing pages, support tools, and managed website services from Texas. This policy explains what personal information we collect, why we use it, where service providers process it, and the choices available to you.
This policy applies to visitors, account holders, Cloud customers, managed website clients, and people who contact us.
02Information We Collect
Account information
We collect your email address, authentication records, and an optional full name. Krevo processes your plaintext password transiently on its application servers during signup, sign-in, and password reset, but never stores or logs it. Supabase Auth stores password hashes and session data.
To reject passwords exposed in known data breaches, Krevo hashes the entire password locally and sends only the first five characters of that hash to Have I Been Pwned's Pwned Passwords service. The service returns a padded range of possible matches; Krevo compares the remaining hash characters locally, so the full password and full hash are not sent to that service.
Cloud files and metadata
When you use Krevo Cloud, we process the files you upload and metadata needed to operate storage, including filenames, file types, sizes, folder structure, upload state, timestamps, quota usage, and object identifiers. File objects are stored with Cloudflare R2; related metadata is stored in our application database.
If you create a share link, we store the link token, expiry and access settings, and a password hash when password protection is enabled. We do not store the share password in plaintext. Recipients may provide the password and request the file through the public share route.
Billing information
Stripe collects and processes payment-card details. Krevo receives identifiers and billing metadata such as customer and subscription IDs, plan, amount, billing status, invoice references, checkout state, and refund-request records. We do not store full card numbers or CVCs.
Support and privacy requests
We store support subjects, messages, attachments, and conversation history. A public privacy request includes the email address, request type, optional details, status, and submission time needed to verify and complete the request.
Marketing and service inquiries
Lead, proposal, waitlist, and compute-access forms can collect your name, email, company, phone number, selected planning time, and the information you choose to submit.
Usage, security, and device data
We process page views, request timestamps, browser and device information, approximate location derived from IP, server logs, rate-limit events, and bot-detection signals. Storage and share requests also generate operational logs used to deliver files, troubleshoot failures, prevent abuse, and secure accounts.
03How We Use Information
We use information to:
- Create accounts, authenticate users, and recover account access.
- Store, organize, transfer, preview, download, and share Cloud files.
- Enforce quotas, subscription access, security controls, and abuse limits.
- Process subscriptions, invoices, cancellations, and approved refunds through Stripe.
- Respond to support, privacy, sales, waitlist, and service requests.
- Operate managed websites and deliver work described in client proposals.
- Measure aggregate product performance and improve reliability and usability.
- Comply with law, valid legal process, accounting obligations, and security requirements.
We do not sell personal information or share it with advertising networks or data brokers.
04Legal Bases
Where law requires a legal basis, we rely on contract to provide purchased or requested services, legitimate interests to secure and improve Krevo, consent for optional marketing communications, and legal obligation for accounting, fraud prevention, and valid government requests. You can withdraw consent without affecting processing already completed.
05Storage and Security
Account, billing, storage metadata, and support records are held in Supabase Postgres. Cloud file objects are held in Cloudflare R2. The application runs on Vercel. Data is transferred between your browser, Krevo, and these providers using TLS.
We use access controls, authenticated server routes, row-level security where appropriate, scoped object keys, short-lived presigned file URLs, rate limiting, password hashing, security headers, validation, and audit logging. No system can guarantee absolute security, so keep independent copies of critical files and protect your credentials and share links.
06Service Providers
- Supabase provides authentication and Postgres database infrastructure.
- Cloudflare R2 stores Cloud file objects and serves transfers through time-limited URLs.
- Have I Been Pwned provides k-anonymous breached-password screening without receiving the full password or full password hash.
- Stripe processes checkout, payment methods, subscriptions, invoices, billing portal sessions, cancellations, and refunds.
- Vercel hosts the application, edge delivery, server logs, BotID abuse detection, and privacy-friendly analytics.
These providers process data for Krevo under their own terms and privacy commitments. We may replace a provider with a comparable service and will update this policy when a change materially affects personal information.
09Your Rights
Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to processing of personal information, and to withdraw consent or opt out of marketing.
If the Texas Data Privacy and Security Act applies to your request, you may ask us to confirm whether we process your personal data, access it, correct inaccuracies, delete it, or obtain a portable copy of data you provided, subject to applicable exceptions. Texas law also provides opt-out rights for sales of personal data, targeted advertising, and profiling used for decisions with legal or similarly significant effects. Krevo does not sell personal data, use it for targeted advertising, or discriminate against you for exercising your privacy rights.
Use the public privacy request form to exercise your rights. No account is required. We may ask you to verify your identity before acting. We generally respond within 30 days. For requests covered by Texas law, we respond without undue delay and within 45 days of receipt. If we need a permitted extension of up to 45 additional days, we explain why within the initial period.
If we decline a covered request, we explain why and how to appeal. To appeal, use the appeal link below. In the details, write “Privacy appeal,” identify the original request, and tell us what you want reviewed. We provide a written decision on a Texas appeal within 60 days of receipt. If we deny it, you can submit a complaint to the Texas Attorney General.
10Retention
We retain account information, Cloud files, file metadata, and support records while needed to provide and secure an active service. After cancellation or account deletion, we retain or remove data according to the product's communicated access period, operational deletion process, backup rotation, legal obligations, and any open dispute or security investigation.
Billing and transaction records may be retained for tax, accounting, fraud-prevention, and legal requirements. Privacy requests are retained long enough to demonstrate receipt and completion. Public form submissions and operational logs are retained only as long as reasonably needed for review, security, and troubleshooting.
When you need a copy of Cloud files, download them before cancelling or request an export while access is available. Presigned transfer URLs expire quickly, but the underlying file remains stored until it is deleted under the account's storage lifecycle.
11International Transfers
Krevo is operated from the United States, and our providers may process data in the United States and other locations where they operate. Where required, provider agreements use recognized safeguards for international transfers.
12Children's Privacy
Krevo is not directed to children, and accounts require a person able to enter a binding contract. We do not knowingly collect personal information from children under 13. Submit a public privacy request if you believe a child provided information to Krevo.
13Changes and Contact
We may update this policy as products, vendors, or laws change. We will update the date above and provide additional notice when a change is material.
Use the public privacy request form for privacy questions, complaints, or rights requests. Signed-in customers can also contact support through the portal.
Questions about this document? Submit a privacy request. No Krevo account is required, and we keep a record we can both refer back to.