Privacy Policy

Leviro Toolbay ("Leviro Toolbay", "we", "us") is an online toolkit offered under the Leviro brand and operated from Egypt. We are the party responsible for deciding how the personal data described in this policy is handled.

This policy applies to the Leviro Toolbay website and the tools available on it. It does not cover any third-party site you reach by following a link from us.

Most Leviro Toolbay tools run entirely inside your browser — your file or text never reaches our servers, so there is nothing for us to store. A smaller set of tools ("Pro" or cloud tools) has to send your input to our servers, and some of those send it on to Google Gemini. Every tool page tells you which kind it is before you use it.

We do not sell your data, we do not share it with advertising or data brokers, we do not run advertising networks, and we do not use third-party analytics, remarketing, or session-replay services.

We do not use your content to train AI models, and the AI provider we use is not permitted to train on it either.

Free everyday tools — formatters, converters, calculators, generators, text and image utilities, the audio and video tools, and the text-to-speech voices — execute as JavaScript in your own browser. The content you paste or the file you choose is never uploaded, so we never see it and never store it. These tools work without an account.

Cloud tools are the ones that need a server: PDF text extraction and OCR, the PDF toolkit, document translation, résumé (ATS) analysis, speech-to-text summarising, image background removal and editing, the i18n message translator, website-to-Markdown conversion, data cleaning, and the invoice, proposal, certificate, and signature generators. For those, your file or text is uploaded over HTTPS, held in the server's memory while it is processed, and released when the request finishes. We do not write your original upload to long-term storage and we do not archive it.

When a cloud tool produces a file for you to download, that output is written to short-lived storage under a random, unguessable name and deleted automatically — 10 minutes for general tools, 15 minutes by default for PDF pipeline artifacts. The Data Retention and Deletion Policy lists every window.

You can use every free browser tool without an account. If you create one, we store:

• Account details — your email address, display name, optional avatar URL, and (if you registered with a password) a bcrypt hash of that password. We never store the password itself and no API ever returns the hash.
• Sign-in method — whether you registered with a password or with Google. If you use Google Sign-In we store your Google account ID, name, email address, and profile picture URL as returned by Google. We accept a Google identity only when Google reports the email address as verified.
• Verification state — whether your email has been confirmed, plus single-use tokens for email verification and password resets that expire after one hour.
• Sessions — one record per active sign-in, holding a browser and platform name (for example "Chrome on Windows"), a deliberately truncated IP address, and when the session was last used. We truncate the address on purpose: this exists so you can recognise a session that is not yours and end it, not so we can build a location history.
• Balances and financial records — your credit and point balances, the append-only credit ledger (every grant, deduction, refund, and adjustment), your subscription state, and any payment orders you created.
• Access state — whether the account is premium, billing-exempt, or suspended, and the reason recorded for a suspension.
• Referral and attribution data — your referral code, who referred you, and any ?ref, utm_source, utm_medium, or utm_campaign values from the link you first arrived on.
• Support messages — anything you send through the contact or feedback forms, including the name, email address, and tool path you supply.
• Optional product analytics — only after you consent, we record allow-listed events such as a tool view, a run starting, succeeding, or failing, a coarse input-size and latency bucket, the interface language, whether processing was local or cloud, credits estimated or charged, and a random session ID. The event record has no free-text or arbitrary-object field at all, so filenames, document text, form values, secrets, and uploaded content cannot be stored by mistake.

For paid tool runs we also record which feature was used, when, and how many credits it cost. For AI features we additionally record the model name, the modality, token counts, the measured provider cost, which prompt version ran, how many retries were needed, the response latency, and whether the output passed validation. We do not store the content you submitted alongside any of those records.

We keep operational records that are not tied to an account: server error reports (redacted before they are written, so user content and secrets never reach them), and counters used to enforce rate limits, weekly free allowances, and abuse detection. Abuse detection scores the shape of rejected requests — how many were refused and why — and alerts a human; it does not read or retain request content.

We only process personal data where we have a reason to:

We do not make automated decisions that produce legal effects for you. Credit charges, quota limits, and abuse alerts are operational rules, not profiling — a suspension is applied by a person and is recorded with a reason.

If you create a dynamic QR code, we record each scan so we can show you analytics. Per scan we store a coarse traffic source, the referrer, the user-agent string, a device class (mobile, tablet, desktop, or bot), the operating system and browser, and a country name.

The country is resolved by sending the scanner's IP address to the ipwho.is lookup service at the moment of the scan. The IP address itself is not written to our database. We do not identify individual scanners and we do not set cookies on the redirect.

If you are the person scanning someone else's QR code rather than its owner: the data above is collected on behalf of whoever created that code, and it is shown to them.

We use a small number of third-party services. Each one receives only what that specific function needs:

Our own database, cache, and file storage run on infrastructure we control. We do not use third-party advertising, remarketing, session-replay, or product-analytics services, and we do not load third-party trackers.

Because these providers operate globally, data sent to them may be processed outside Egypt. We send each one the minimum it needs for its function, and we do not authorise any of them to use your content for their own purposes, including model training.

In short: uploaded files are not retained; generated downloads expire in minutes; consented analytics and error records expire after 90 days; account and financial records are kept while your account exists. The Data Retention and Deletion Policy lists every category with its exact window.

• All traffic is served over HTTPS.
• Passwords are hashed with bcrypt and are never returned by any API.
• Sessions use httpOnly cookies that JavaScript cannot read, marked Secure in production.
• Refresh tokens rotate on every use. If a already-used token is replayed, the entire session family is revoked rather than just that token.
• You can list your active sessions and end any of them — or all the others at once — from your account.
• Suspension is enforced on every authenticated request, not only at sign-in, so an existing session cannot outlive the decision.
• Uploads are checked against per-tool size limits and real file-signature (magic byte) validation, not just the file extension, and archives are checked for decompression-bomb ratios before anything is expanded.
• Server-side URL fetching validates every redirect hop, pins the resolved address for the connection it validated, and refuses private, loopback, link-local, and cloud-metadata targets.
• Rate limits, per-user and platform-wide concurrency limits, and job-size ceilings apply to heavy and paid work.
• Error reports are redacted before they are written, so user content and secrets are not persisted in them, and no stack trace is ever returned to a browser.
• Administrative actions on accounts, credits, and access are recorded in an append-only audit trail.

No system is perfectly secure, and we do not claim otherwise. If you find a vulnerability, please report it privately to [email protected] before disclosing it. Good-faith security research is welcome under the terms set out in the Acceptable Use Policy.

• Access — you can see your profile, credit ledger, transaction history, active sessions, and payment records in your account at any time.
• Correction — you can update your display name and profile details from your account.
• Deletion — there is no self-service delete button yet. Email us from the address on the account and we will delete the account and its personal data. We may retain the minimum financial records needed for accounting and fraud prevention, detached from your identity.
• Export — email us and we will send you a copy of the personal data associated with your account.
• Withdrawing consent — you can stop using cloud and AI tools at any time and keep using the browser-only tools without an account.
• Product analytics — you can decline in the consent prompt, or clear the leviro.analytics-consent browser-storage entry to be asked again. A browser "Do Not Track" signal keeps analytics disabled without asking.
• Ending a session — you can revoke any active session, or every session other than the one you are using, from your account.
• Complaints — if you think we have handled your data wrongly, contact us first. You may also raise the matter with the competent data protection authority in your country.

We aim to respond to any of these requests within 30 days. We may ask you to confirm the request from the email address on the account before we act on it.

Leviro Toolbay is not directed at children under 13, and we do not knowingly collect their personal data. If you believe a child has created an account, contact us and we will remove it.

If we change how we handle your data, we will update this page and move the effective date shown at the top. Material changes will also be announced in the app.

For privacy questions, deletion requests, or data exports, email [email protected] or use the contact page. Leviro Toolbay is operated from Egypt.