Privacy Policy
Last updated 29 October 2026
How we handle the information needed to help you write, save and share your tabs.
Who we are
Swift Tab Writer is operated by Luke Dunn, a sole trader in England, trading as Swift Tab Writer. Luke Dunn is responsible for the personal information described here. Contact support@swifttab.app about privacy or your account.
Account and authentication
We process your email address, first and last name, account identifier and authentication information to create, secure and manage your account. Supabase provides authentication and our application database. When you choose Google Sign-In, we receive identity information such as your Google email address, name, basic profile details and provider identifier where supplied. We use this to authenticate your SwiftTab account. We request only openid, email and profile scopes—not access to Gmail, Google Drive or Contacts.
Your songs and collaboration
We store the song, tab, section, instrument, tuning and other creative content you save to your account so it can be loaded and synced. Collaboration records include invitations, participants, permissions and lightweight editing presence. People you give access to can see or edit content within their permissions. Presence communicates activity such as the section or tab position being edited; it is not a public activity feed.
Public shared tabs
Creating a public share publishes a read-only snapshot. Anyone with its link can view and pass on that snapshot. Private song tables are not directly exposed by the public viewer. Removing access to a link cannot recover copies, images or text that others have already saved. Only share content you intend others to receive.
Support and feature requests
In-app submissions contain the details you enter, your account reference and limited technical context such as version, platform, environment and screen. We do not automatically attach private tab content. Screenshots and videos are supplied deliberately by email to support@swifttab.app, not uploaded into the app database. Email attachments are still processed and retained in the support mailbox; do not send passwords, payment details or unnecessary private information.
Subscriptions and payments
RevenueCat helps associate paid Premium access with your SwiftTab account. We process subscription identifiers, plan, purchase provider, transaction/status information and entitlement history. Web Billing uses RevenueCat and its payment provider, Stripe; Apple or Google Play handles billing when purchasing through those stores, where available. Full payment-card information is handled by payment providers rather than stored in the SwiftTab application database. Complimentary Premium is recorded separately from paid subscriptions.
Why we use this information
We use account and creative data to provide the service you request and fulfil our contract with you. We rely on legitimate interests to secure the service, prevent abuse, troubleshoot faults and respond to enquiries, taking account of your rights. We process records where necessary to meet legal obligations. Where processing needs your consent, you can withdraw it; this does not affect earlier lawful processing. We do not sell your personal information or use your private tabs for advertising.
Service providers and international processing
Our service providers include Supabase for authentication and data, Cloudflare for hosting and delivery, RevenueCat and payment platforms for subscriptions, Microsoft email services for transactional/support email, and GitHub for deployment and encrypted backups. Google processes sign-in under its own privacy terms. Providers may process information outside the UK. Applicable contractual and transfer safeguards are used where required; contact us for details about the arrangements relevant to your data. We may also disclose information where required by law or necessary to protect users and the service.
Local storage and cookies
The public website stores your theme preference locally and does not include advertising or analytics trackers. The app uses browser/device storage for authentication, preferences, cached notebooks and pending changes. The public viewer stores its theme choice. Hosting, authentication and payment providers may use security/session technologies on their own services. Browser or device restrictions can affect offline saving. Clearing app storage can remove changes that have not synced.
Retention and deletion
We retain your account and saved work while needed to provide your account, unless you delete it or ask us to remove it. Delete account is available in app Settings; if you cannot sign in, email support@swifttab.app from your account email to request deletion. We may verify your identity. Account deletion removes owned content, profile, shares and associated access records; other users’ independently owned content remains. Limited financial and security records may remain for reconciliation, legal obligations and abuse prevention, with account identity removed where supported. Technical diagnostic events are configured to expire after 14 days. Encrypted backups may retain deleted data until their 30-day retention ends. Support emails are kept while needed to resolve enquiries and meet applicable obligations, then reviewed for deletion. Deleting your account does not itself cancel a store subscription—manage renewal with the original billing provider.
Security
We use access controls, encrypted connections and encrypted backups to protect information. Access is limited to service operation and authorised administration. No online service or device can be guaranteed completely secure. Tell us promptly if you suspect unauthorised account access.
Your rights
Depending on the circumstances, you can request access, correction, erasure, restriction or portability of your personal information, and object to certain processing. Contact support@swifttab.app; we may ask for information to verify your identity. You can also complain to the UK Information Commissioner’s Office. Contacting us first can help us resolve the issue but is not a requirement for complaining.
Changes to this policy
We may update this policy as the product or legal requirements change. The date above identifies the current version. We will provide appropriate notice of material changes.