Updated · 28 October 2026
Privacy notice
This notice describes the current invitation-only service, including account access, community content and moderator notifications.
Who runs this service
AMT Traveller Connect is a traveller communication app associated with AMT Travel Health. Members can choose a city or destination for their community questions; the current service is invitation-only. The operator and data controller is AMT DIGITAL HEALTH LIMITED (company number NI743195). Its registered office is 26 Ballyveigh Avenue, Antrim, Northern Ireland, BT41 2GX, as listed on Companies House. For privacy requests, write to admin@amt-travelhealth.com. If a data protection officer is appointed, their contact details will be added here.
What we collect and why
- Account and access: phone number or email address (whichever you provide), your traveller name, your adult and rules declarations, account dates, last activity, hashed sign-in and session tokens. These support SMS-code or email-link sign-in, account access and the invitation-only beta. You can add an email address for sign-in while travelling without SMS service.
- Abuse prevention: keyed hashes derived from the request IP address and the email address or phone number used, with timestamps, for sign-in rate limits. The app does not store the plain IP address in this table. Hosting infrastructure may retain operational logs separately.
- Community: your chosen destination or city, category, question and reply text, optional JPEG photos or recorded voice notes, author ID, status, dates, reports and blocks. Questions and replies are reviewed before appearing to other signed-in members. Moderators can review pending questions and reports.
- Private Inbox and invite-only Groups (internal trial): browser-generated public device keys, a browser label, connection and removal dates, encrypted messages and small media, member identifiers, group membership and invitations, timestamps, key versions, and reports. The service does not hold the device private keys. Each signed-in browser can keep its own key; new messages are encrypted for all connected browsers. You can remove an unused browser in Chat devices. Earlier messages may require the original browser or a resend. Participants can voluntarily disclose a selected decrypted message and attachment in a report, which moderators can then read. Group creators can invite or remove their group by deleting it, but cannot access messages that were not delivered to them. This design has not had an independent security review and is not suitable for sensitive content.
- Friend invitations: the name you optionally give an invitation is visible only to you. We store invitation status, expiry and the two member IDs so Pending and Accept connections remain visible before a first message. Invitation links are single-use and expire after 14 days; the server stores a hash of the secret. Closed invitation records are removed after 30 days. Accepted contacts remain linked until an account is deleted.
- Service administration: moderation actions, aggregate membership and post counts, and reviews of the official emergency source. The ordinary owner dashboard shows aggregate counts. Privileged infrastructure and database access can technically reach stored account data; a promise that no administrator can ever access email or content would be inaccurate.
Members may choose to write information about health, safety or other sensitive matters in posts or reports. Please avoid personal medical details and other identifying information.
Visibility and sharing
Approved questions and replies, attachments, chosen destinations and traveller names are visible to signed-in members. Pending and rejected contributions are visible to their authors and moderation staff. Members can report a question or reply, or block a member. Moderators can see reported content and reasons and may remove a reported question from the member feed. Removed questions remain in the live database until the author deletes them or a later approved retention rule applies. Other members may copy or screenshot material they can see.
Service providers: Render hosts the application and database. Twilio Verify processes phone numbers and SMS verification activity when phone sign-in is used. Resend processes sign-in and moderator alert emails. Device push services receive an encrypted, generic moderation notification when you enable push; the app stores your device subscription so it can send alerts. Email and push alerts do not include post text, private messages or contact lists. If server translation is configured and you choose it, the selected community discussion or reply is sent to OpenAI for translation. Private chats are excluded from server translation.
The beta does not request device location and does not use advertising or ad tracking. Choosing a city or destination is not device location tracking.
The private Inbox, invite-only Groups and one-to-one browser calls are enabled for an internal staging trial; public joining remains closed. The server stores message ciphertext and metadata, including who belongs to a group and who received a message. A participant can report and share decrypted content with moderators. Calls use direct browser media and may reveal network addresses to participants; a relay is not configured, so different networks may fail to connect. The private messaging trial has not had an independent security review.
Retention and deletion
Moderation notification events and delivery status are retained for 30 days. Push subscriptions remain until disabled, invalidated by the device provider or deleted with the account. You can turn email alerts off and disable device notifications from Moderation. The server retains its push signing keys so device subscriptions continue to work after a restart.
Email sign-in links expire after 15 minutes and SMS challenges after 10 minutes. Sessions expire after 30 days. Rate-limit records older than one day and expired tokens, sessions and invitations are removed by a periodic cleanup that also runs at startup; removal may happen later than the expiry time.
- Accounts: member accounts inactive for 12 months are flagged in the moderator dashboard for operator review. This is a review point, not automatic deletion. Active accounts and approved questions remain until the member deletes them or a later approved rule applies.
- Rejected questions: deleted from the live database 30 days after the rejection decision.
- Group messages and invitations: group messages are deleted from the live database after 12 months. Single-use invitations expire after seven days and are removed by cleanup. Leaving a group stops future deliveries, but copies on other participants’ devices remain. Direct private messages remain until both participants hide them or an account is deleted.
- Closed reports: deleted from the live database 12 months after resolution. Open reports remain while they need review. Moderation event records are deleted after 12 months.
Cleanup runs at startup and every six hours. A member can use My account to download a JSON export and delete the live account with its associated posts and reports. Hosting backups and operational logs may persist after live deletion; copies made by other members cannot be recalled.
Your privacy choices and rights
Subject to applicable law, you may request access, correction, erasure, restriction or portability, or object to certain uses, by emailing admin@amt-travelhealth.com. You can also complain to the UK Information Commissioner’s Office.