QUOTAVANI · UPDATED 11 NOVEMBER 2026
Privacy policy.
This policy covers Quotavani’s Android early-testing product and this website. Earlier test builds may still display the previous name, SwiftQuote; the website rename does not change their data handling. Quotavani provides quotes and invoices for sole traders and small service businesses.
For privacy questions, email swiftquotapp@gmail.com or use our support/contact form. For account and associated data deletion, use Delete account. Neither form requires an app installation or Quotavani login.
1. What stays local, and what may leave your phone
| Feature | Information and purpose | Where it is processed |
|---|---|---|
| Transaction interpretation | Typed text, including the customer and work details you enter, becomes an editable quote or invoice proposal. | The reviewed app uses Quotavani’s on-device parser and trade resolver. It does not send the transaction to an external AI interpretation service. |
| Business records & PDFs | Business profile, customer details, bank/tax details you add, items, prices, draft/final documents and manually recorded payment status. | Stored and processed on your phone. Android device backup settings can also affect app-data backups. |
| Google sign-in | Google account identity, name, email, profile photo and authentication identifiers/tokens to sign you in and bind local records to your account. | Google Identity and Firebase Authentication. Profile images may load from Google servers. |
| Phone contacts | Contact names and selected phone/address details to find and confirm the right customer. | Phone contact search runs on the device after permission. Selected details can become local customer records and appear in PDFs you share. |
| Purchases | Subscription product, purchase and entitlement information to determine paid access. | Google Play Billing handles payment. Quotavani does not receive your full payment-card details. |
| Sharing & saving | The PDF and customer information included in it. | You choose the destination, such as email, messaging or file storage. Those services and recipients then handle their copies. |
| Website forms | Tester registration, feedback, support and deletion-request information you submit. | The website’s hosted database and restricted owner dashboard, as described below. |
2. Permissions and your choices
Contacts access supports customer lookup; you can decline it and enter a customer manually. Enter invoice instructions as typed text.
Notifications, if enabled, support owner reminders about documents. You can change permissions in Android Settings. Reminders do not independently verify payments or send automatic messages to your customers.
3. Why information is used
Quotavani uses the information you provide to prepare, calculate, store, preview and share your documents; identify your account; check subscription access; and respond to testing, support and deletion requests. Review interpretations, customer matches, amounts and tax before finalising a document.
Sign-in does not back up or synchronise your business records to Firebase by itself. Local document handling does not make Google sign-in, billing or a chosen sharing service offline.
4. Service providers, analytics and security
Google/Firebase provide authentication and Google Play provides billing. Render serves the public website address; Cloudflare/Sites hosts the underlying website and its database. These providers process technical request, security and service data needed to operate their services.
The app version covered by this policy has no advertising, Firebase Analytics or Crashlytics SDKs. We add no advertising trackers or analytics cookies to this website. Hosting providers and Google services process technical data and operational logs as needed to run their services.
Website requests use HTTPS. Website registrations and requests are available through an authenticated owner dashboard, not a public directory. Private tester links act as access keys: keep them safe. No system can guarantee absolute security. Protect your phone, Google account and exported files.
For provider information, see Google’s privacy policy, Firebase privacy information, Cloudflare’s privacy policy and Render’s privacy policy. Processing locations and provider retention can differ from your country.
5. Website registration and feedback
The tester form collects your first name, email, line of work, invoicing frequency, current method, optional country, Android availability and optional Play-test interest. It records registration time, consent version and any campaign label in the URL. Quotavani uses these to organise testing, contact interested testers and understand feedback, not to add you to unrelated marketing.
Your private tester link lets you submit feedback or permanently delete the active registration and feedback. No confirmation email is sent automatically. Only a hash of the private access token is stored. The website temporarily stores hashed network identifiers and request counts for abuse prevention; entries older than 24 hours are cleared during subsequent form requests.
6. Support and deletion forms
These forms collect the email, topic, optional or required message, consent and submission time. A request reference is returned after saving. The request enters the private owner queue for manual review, and your email is used for follow-up and any necessary ownership verification. Do not submit passwords, verification codes, card details or real customer records.
If you contact swiftquotapp@gmail.com, Google Gmail processes your email address, message and any attachments. Quotavani uses that information to respond and handle your request. Email correspondence is handled separately from the website database and kept while needed for your request and follow-up; it is not covered by automatic cleanup of website request records. Contact support to request removal of email correspondence, subject to any specific retention obligation explained to you.
7. Retention and deletion
Local app records remain on your phone until you remove them or clear app storage; exported PDFs and backups must be managed separately. The app permits Android backup, so review your device backup settings. Google/Firebase account records remain until the account is deleted. Signing out does not delete the account or local records.
Tester data is retained while needed to organise testing unless deleted sooner. Open support and deletion requests are retained while being handled. Closed requests are removed from the active website database after 90 days, with cleanup performed on subsequent request or owner-dashboard activity. Infrastructure backups, security logs and Google billing records follow provider retention rules.
Use the account-deletion request page to request removal of the Quotavani account and associated data without reinstalling the app. Support verifies ownership, confirms the expected completion time and explains any specific legal/security retention exception. Submitting the form is not immediate deletion. Copies already shared with others cannot be removed remotely by this website.
Launch subscriptions and the free calculator
The launch form collects your email and explicit consent for Quotavani Android availability and launch updates. Business type is optional; document frequency is an optional question after signup. Consent wording, version and time, subscription state and a protected private-link identifier are stored in the existing hosted database. Launch subscriptions are separate from tester and support records. Those records are not imported into marketing lists.
Your browser tab can retain only recognised campaign labels and a known public entry path in session storage, so an eventual subscription can retain its source. Arbitrary query strings, email addresses and calculator content are not kept in attribution. Local browser measurement events contain fixed event names and bounded page/outcome labels; no external analytics provider is configured. Server-side subscription totals measure saved records, not page visits or paid conversions.
The calculator processes descriptions, quantities and prices locally in memory. They are not uploaded, stored on the server or included in analytics. Copying uses your device clipboard at your request; if unavailable, you can copy a displayed summary manually.
Launch updates are free. Subscribing does not install the app, activate a paid subscription or enrol you in app testing. When server email delivery is configured and enabled, a new launch signup receives one welcome email through Google Gmail from swiftquotapp@gmail.com. Delivery is otherwise disabled. No automatic launch campaign is enabled. Only active consented launch subscribers are eligible; tester and support records are excluded. Gmail processes the recipient address, message and private management link. We do not add tracking pixels or rewrite links. Delivery job identifiers, status, timestamps and Gmail message identifiers are stored to prevent duplicates and investigate errors; these records are reviewed with launch-data retention. API acceptance does not guarantee inbox delivery.
Save the private management link shown after signup. Its secret stays in the URL fragment, which is not sent with the page request, and the management page is excluded from search. Opening it makes no changes. Use its unsubscribe button to mark the subscription inactive, or contact support from the subscribed email for help or deletion. Keep the link private; anyone holding it can unsubscribe that subscription. Duplicate form submissions do not reactivate an unsubscribed email.
We keep active records while needed for the launch-update purpose and review retention at least annually. A minimal consent and suppression record may be retained after unsubscribe to prevent unwanted re-enrolment. Optional business/need answers are cleared when you unsubscribe. Request erasure through support; provider backups and security logs follow their retention schedules. Launch data is accessible only to the authorised owner and is not sold or used for unrelated marketing.
Knowledge tools and discovery observations
The visible catalog assistant and browser calculator process questions and calculations locally without uploading their inputs. The public read-only API and MCP tools process only the product questions and calculation inputs a caller explicitly submits. The application does not store these API inputs or add them to analytics; infrastructure providers may retain technical request logs. Do not submit customer records, private links, credentials or payment details.
The private owner discovery dashboard stores public product-research observations, including prompt/run identifiers, provider/model/market labels, response text and source URLs, observation times and derived brand-presence counts. This research is separate from launch subscribers and customer records. Only the authorised owner can record, view or remove observations. Retention is reviewed at least annually; the dashboard reports a rolling 28-day sample and permits manual removal. No automatic third-party model research collection or paid API calls are enabled.
8. Policy updates and contact
This policy describes the reviewed early-testing implementation. Different builds or future features may change data handling; the policy and in-app disclosures must be updated before those changes are offered. Use the support/contact page for access, correction, privacy or deletion questions. The latest revision date appears above.