1. Who we are
TailPass is operated by Iurii Kaliagin PR Računarsko programiranje TAILLAB Beograd, registration number 66758613, tax ID 113347390, Čika-Ljubina 12, stan 3, 11102 Stari Grad, Belgrade, Serbia. Contact us about privacy or your data at support@tailpass.app.
2. Information we process
- Account and access: email, display name, user ID, language, sign-in provider, authentication and session information, and records of accepted terms and notices. Email registration uses a password; Google and Apple sign-in use information and tokens provided by those services.
- Pet records and files: profiles, photos, microchip numbers, health history, visits, medications, lab results, notes, reminders, uploaded images and PDFs, and AI scan drafts/history. Documents may also contain information about owners, veterinarians or other people. Please upload only information you are entitled to use.
- Sharing and collaboration: workspace membership, invitations, transfers, public contact details, link identifiers, permissions and expiration settings.
- Support: your name, email, messages and any attachments you provide.
- Purchases: products, transaction identifiers, purchase tokens, subscription status, store verification results and related billing records. The app stores handle checkout; TailPass does not receive your full payment-card details through these purchases.
- Technical and usage information: app and device information, push tokens, notification settings, time zone, interactions with features, error reports, diagnostic identifiers and audit events. Website and infrastructure providers also process IP addresses, request information and other technical data needed to deliver and protect the service.
3. Why we use this information
We use information to provide accounts and secure access; store and share records; deliver reminders; process scans and translations you request; administer purchases and plan limits; provide support; understand feature use; diagnose failures; prevent abuse; and meet applicable legal obligations.
Where applicable data-protection law requires a legal basis, we rely on performance of our agreement for requested app features, legitimate interests for proportionate support, security, diagnostics and product improvement, and legal obligations for required records. We request relevant device permissions and obtain consent where applicable law requires it.
4. AI scans and translations
When you request a document scan, TailPass sends the selected images or PDFs and processing instructions to Google's Gemini models through Vertex AI to extract editable draft records. The configured Vertex model processing location is the EU; other Google service operations may involve other countries.
Under the applicable Google Cloud terms, customer data is not used to train Google's models without permission. Temporary caching and safety or abuse-monitoring retention may apply; selected data may be reviewed by authorized personnel for those purposes.
Translation of supported record text is processed on our backend. Files and scan history may also remain in TailPass storage so you can review drafts, link records and manage your documents. AI and translations can be wrong: compare results with the original records before saving or sharing them. See our AI Disclosure and Medical Disclaimer.
5. Who receives information
We use providers for specific parts of TailPass:
| Provider | Purpose and information |
|---|---|
| Supabase | Account authentication, database, file storage, realtime updates and backend functions; account, pet, document and operational information needed for these features. |
| Vultr | Backend hosting in Frankfurt, including scan processing and translation. |
| Google Cloud / Vertex AI | Document extraction as described above. |
| Cloudflare | Website and public-page delivery, shared content, downloads and related request/security information. |
| Sentry | Error and crash diagnostics, technical information and identifiers needed to investigate stability issues. |
| Expo, Apple APNs and Google FCM | Push delivery: device tokens, notification text and routing data. Reminders may include pet names and event titles. |
| Resend | Delivery of account emails, including confirmation and recovery links. |
| Inbound email delivery for our support address and the messages or attachments you email us. | |
| Telegram | Delivery of in-app support conversations and images to our support operator through bot chats. |
| Google and Apple | Optional sign-in and store purchases, including provider account information, TailPass account/workspace identifiers used to associate purchases, transaction information and purchase verification. |
Some website pages load flag images from FlagCDN, whose servers receive the request and ordinary browser connection information. Providers may use subprocessors to deliver their services.
We do not sell personal data. We also disclose information to people you invite or share links with, where legally required, to protect rights and security, or in connection with a business transfer subject to applicable safeguards.
6. Public links and shared workspaces
Anyone with a valid vet-share or lost-pet link can view the information exposed by that page. Depending on the feature, this may include health records, attachments, notes or contact details. Workspace members can access information according to their role. Check what you share and revoke or expire links when access is no longer appropriate. Revoking a link cannot retract copies already downloaded, photographed or otherwise saved by recipients.
7. Notifications and support
You can control notifications through device and app settings. Notification text can appear on your lock screen or other connected devices. Medication reminders scheduled locally are handled by your device rather than sent as remote messages through Expo Push Service. Delivery is not guaranteed.
Our support operator receives in-app messages and images through Telegram. Email support is processed through our email providers. These services and recipients may retain copies under their own systems and policies; deleting a TailPass account does not automatically erase all messages or attachments from Telegram, email or recipient devices. Avoid including unrelated sensitive information in support requests.
8. Locations and international processing
Our main Supabase database and file storage are configured in Frankfurt, Germany, and our backend is hosted there. Website delivery, authentication, notifications, support, diagnostics, payment processing and provider operations may involve other countries.
We take applicable international-transfer requirements into account when selecting providers and using their contractual protections. Contact us for information about arrangements relevant to your data.
9. How long we keep information
We keep account and product data while needed to provide the service and your chosen features, subject to deletion requests. Uploaded scan files and drafts can remain in your scan history or document storage until removed through the relevant product or account-deletion process.
Technical client error records in our database are scheduled for deletion after 30 days, and raw feature-usage events after 90 days. Cleanup runs periodically, so deletion may occur at the next successful cleanup. These periods do not apply to every provider's logs or to purchase records.
Support, purchase-verification, audit and security records are retained as needed to resolve requests or disputes, protect the service, verify entitlements and meet applicable obligations. The appropriate period depends on the record, its purpose and any applicable legal requirements. Some purchase-verification records remain after account deletion. Backups and provider systems may retain copies beyond deletion from the active app; deletion from the app does not immediately remove these copies.
10. Deletion and your rights
You can request account deletion in app settings or by emailing support@tailpass.app from your account email. A 30-calendar-day grace period applies before the scheduled deletion process. Account deletion includes your account and data owned through it, subject to shared ownership, transfers and the retention exceptions above. Deleting a workspace owner's account can affect other members' access to that workspace's data. See Account Deletion for details.
Depending on applicable law, you may request access, correction, deletion, export, restriction or objection, and withdraw consent where processing is based on it. Withdrawal does not affect the lawfulness of earlier processing. You can contact us to exercise these rights; we may need to verify your identity. You may also complain to the competent data-protection authority.
11. Browser storage, security and children
We use functional browser or device storage for sessions, settings and requested features. We do not currently use advertising cookies, ad pixels or session replay on our public website. If this changes, we will provide notice and seek consent where required.
We use access controls, private storage and other safeguards appropriate to the service. No system is perfectly secure; protect your devices, account and sharing links.
TailPass is not directed to children. If a child has provided personal data without appropriate permission, contact us so we can review the situation.
12. Changes
We may update this Policy as the service changes. We will communicate material changes through appropriate channels, such as the app, website or email, and request consent where required.
