1. Who controls your information
Tag Along is operated by Fortwit Technology Limited (“Tag Along”, “we”, “us” or “our”). We determine why and how personal information is processed for our service and act as its data controller, or the equivalent role under applicable law.
Fortwit Technology Limited, 6B Abiola Okeke Close, Medina Estate, Gbagada, Lagos, Nigeria. Company email: Tagalong@fortwit.com. Website: www.mytagalongapp.com.
Use our published contact channel for privacy questions or to exercise a right. Include “Tag Along privacy” in the subject where practical. We will route the request to the person responsible for privacy. Any legally required regional representative or data protection officer contact will be included in the published contact details before the relevant offering begins.
2. Scope and your choices
This policy covers visitors, account holders, event hosts, attendees, people who contact us, and people whose information appears in a report or community contribution. It explains collection, use, disclosure, retention and your choices across our website and mobile applications.
Hosts, venues, external booking services, linked websites and sign-in providers may process information independently. Their own notices apply to that processing. We remain responsible for the information we control and for service providers acting on our instructions.
Providing account information needed to authenticate you is necessary to create an account. Event details are necessary to publish or join an event. Optional profile fields, marketing, precise device location and optional tracking have separate choices; declining them does not authorise us to collect them anyway. Some requested features may be unavailable without the information they need.
3. Adults-only service
You must be at least 18 and old enough to enter a binding agreement where you live to create an account. We do not knowingly permit underage accounts. If you believe a child is using the service, contact us. We will investigate, restrict the account where appropriate and erase information that we are not legally permitted or required to retain. An adult age rule does not remove our obligation to protect children whose information reaches us.
Accepting our Terms of Service is not blanket consent to every use of personal information. We ask separately whenever consent is the legal basis.
4. Categories and sources
| Information | Examples and source |
|---|---|
| Account and profile | Name or display name, email, phone number where requested, account identifier, authentication records, age eligibility, profile photo and optional interests. You provide these directly or through an enabled sign-in provider. |
| Events and community | Event title, description, venue/address, time, capacity, joins and leaves, saved events, reviews, captions, photographs, video and stories that you submit. |
| Communications | Messages and associated sender, recipient and time information; support enquiries, complaints, safety reports and attachments. We also receive information when another person reports content or mentions you. |
| Device and service use | IP address, device/browser type, operating system, app version, timestamps, basic interaction and error records, authentication events and notification tokens. Optional tracking is subject to the Cookie Policy. |
| Location | Approximate location derived from IP address or an area you choose. Precise device location only when you enable a feature and give the required permission/consent. An event address you publish is community content. |
| Moderation and choices | Report records, content moderation labels/scores, review decisions, block lists, appeals, consent selections, privacy requests and the minimum information needed to verify them. |
5. Sensitive information and permissions
Messages, images and event choices can reveal sensitive matters such as religion, health, ethnicity, sexual orientation or precise whereabouts. Please share carefully and avoid posting another person’s sensitive information without authority. We do not infer sensitive traits for advertising. Where processing requires an additional legal condition, we obtain explicit consent or rely on another condition that the law permits; otherwise we do not undertake that processing.
Camera, microphone and photo access is limited to the feature you choose. A permission prompt does not itself give consent for unrelated purposes. We do not upload your entire address book or continuously track background location under this launch policy. If these activities are introduced, we will first explain the purpose, recipients, retention and separate controls.
For third-party sign-in, we receive the information you authorise, such as an account identifier, name and email. We do not receive your Google or Apple account password. We do not use photos or videos for facial identification or build biometric identity profiles.
6. Purposes and legal grounds
Where a law requires a legal basis, we use the grounds below for the stated purpose. A separate sensitive-data condition is also needed where applicable. We use consent where local law requires it rather than treating these grounds as interchangeable.
| Purpose | Information and legal basis |
|---|---|
| Deliver the service | Account, event, participation and message data to authenticate you, publish your chosen content, connect participants and deliver messages. Necessary to perform our agreement with you. |
| Safety and reliability | Limited device, use, report and moderation records to prevent abuse, investigate complaints and secure the service. Our legitimate interest in protecting people and systems, after considering effects on your rights; legal obligation where a specific duty applies. |
| Optional features | Precise location, optional tracking and other permission-based functions. Your consent where required, with feature-specific information and an easy way to withdraw. |
| Marketing | Contact information and communication preferences to send optional product or event promotions. Opt-in consent for this launch; withdrawal through the message or contact channel. |
| Support and claims | Support content to answer service questions under our agreement; limited records to resolve disputes or establish/defend claims based on legitimate interests or a specific legal duty. |
| Improve the service | Minimal reliability and aggregate use information to identify failures and improve usability. Legitimate interests for necessary, proportionate operational analysis; consent before optional analytics or tracking. |
7. Discovery, moderation and human review
Discovery may use the area or filters you choose, event timing, availability and interests you provide. We do not use sensitive-trait advertising profiles. Where personalised ranking is introduced, we explain its material inputs and available controls before use.
For media moderation, the selected launch design uses AWS Rekognition to return content labels and confidence scores. Clear violations can be rejected automatically; uncertain uploads stay unpublished until reviewed; uploads that pass screening can publish. Humans may also review reports and relevant content, including messages reported to us. Screening can make mistakes and is not a guarantee that every harmful item will be detected.
You may contest a restriction and request meaningful human review through our support contact. We consider your explanation and relevant context. We do not use solely automated decisions with legal or similarly significant effects without the safeguards required by applicable law. Unrelated training of general AI models with your content is outside the purposes of this policy.
8. What others can see
Other users and the public. Your chosen display name, profile image and content are shown to the audience indicated by the relevant feature. Public events and contributions may be copied, shared or indexed outside Tag Along. Before you publish, check the audience and avoid including private contact details or a home address unnecessarily.
Hosts and participants. Joining an event shares the profile and participation details needed to coordinate that event with the host and the audience identified in the join flow. Hosts do not receive private contact details or precise live location by default. Attendance export, if offered, is limited to disclosed fields and legitimate event administration; it is not permission for independent marketing.
Messages and location. Messages are available to their intended participants and may be accessed by authorised staff where needed to operate, secure or investigate the service. We do not represent chat as end-to-end encrypted. Optional live location sharing must identify the recipients and duration, remain off until activated, and provide a stop control. Sending an event address is different from sharing your live device location.
9. Organisations receiving information
| Recipient | Reason for disclosure |
|---|---|
| Service providers | Hosting, database, authentication, media storage, delivery, notification, security and support suppliers process the minimum needed on documented instructions. Cloudflare R2 stores uploaded media; AWS Rekognition processes moderation inputs when enabled. |
| Sign-in and external services | Google, Apple or another service you deliberately use may receive data needed to complete that interaction and process their own account information under their notices. |
| Advisers and authorities | Professional advisers and authorities receive information when necessary and legally justified for claims, legal duties or serious safety incidents. We assess requests and disclose proportionately. |
| Business successors | If a reorganisation, financing or business transfer involves personal information, access is limited to what is necessary under confidentiality and applicable safeguards. Material controller or purpose changes are notified. |
We do not sell personal information, share it for cross-context behavioural advertising, or permit providers to use it for their own unrelated advertising. This does not prevent the service disclosures explained above. We do not offer payment for surrendering privacy rights. A materially different practice requires updated notices and the choices or consent required by law.
10. How long we keep information
We keep identifiable information only as long as needed for the disclosed purpose. The following launch schedule applies unless earlier deletion is required or a specific lawful exception justifies longer retention. Account deletion covers content, media and associated records, not only the login.
| Record | Proposed retention commitment |
|---|---|
| Account, profile and saved items | While the account is active. Review after 24 months of inactivity; give at least 30 days’ notice before closing an inactive account. Active-system deletion within 30 days of a confirmed deletion request. |
| Published events, posts, reviews and chat | While needed for the feature and account, subject to user deletion and periodic necessity review. Remove the user’s identifiable content when the account is deleted unless a specific lawful exception applies. |
| Stories and abandoned uploads | Stories stop displaying after 24 hours. Delete the underlying active media within 3 days after expiry. Delete unsubmitted uploads within 3 days after abandonment and rejected media within 3 days after the final review, unless lawfully held. |
| Precise live location | Stop sharing when you stop the feature or its session ends. Delete service copies within 24 hours after the session ends, unless needed for a specific reported incident. User-published venue addresses follow content retention. |
| Routine logs; support and safety | Routine security/debug logs: up to 90 days. Closed support and safety cases: up to 24 months from closure where necessary, with minimisation. Specific legal holds are reviewed at least every 6 months. |
| Choices and deletion records | Minimal proof of consent, withdrawals and request handling: up to 24 months from the relevant action. A minimal suppression record may be kept as long as needed to honour an opt-out. |
| Backups and recovery copies | Deleted information expires or is securely removed within 90 days of the confirmed request or scheduled deletion trigger. It is isolated from routine use; deletions are reapplied before restored data returns to service. |
11. International processing
Our Nigerian operations and service providers may involve international access and transfers. Before a restricted transfer, we establish an applicable lawful mechanism, such as an adequacy decision or approved contractual safeguards with required assessments and additional protections. We do not rely on accepting this policy as blanket transfer consent. You may ask for destination and recipient information and a copy or explanation of relevant safeguards, with lawful confidential details redacted.
12. Security and incidents
We apply proportionate technical and organisational safeguards, including controlled access, protection of information in transit and storage, authentication controls and incident handling. No service is risk-free. Where legally required, we notify the relevant authority and affected individuals within the applicable period. We do not promise a universal 72-hour notice to every user.
13. Requests available to everyone
Contact us for access, correction, deletion, a portable copy, recipient information, consent withdrawal or review of a privacy decision. Applicable law may also give rights to object, restrict processing, limit sensitive uses or contest significant automated decisions. We do not unfairly discriminate for exercising a right.
We acknowledge within 5 business days and aim to complete requests within 30 calendar days of receipt or a shorter legal deadline. Identity checks are prompt and proportionate; verification does not automatically restart the statutory clock. We explain lawful extensions, refusals and complaint routes within the applicable deadline. Requests are normally free. Any legally permitted fee requires justification. An authorised agent may act with proof of authority.
14. Regional rights and deadlines
| Where applicable | Additional protection |
|---|---|
| Nigeria | Rights under the Nigeria Data Protection Act 2023 and applicable NDPC guidance, including access, correction, objection, erasure, portability and safeguards for automated decisions. Complaints may be made to the NDPC. |
| EEA and United Kingdom | GDPR/UK GDPR rights include restriction and objection, including an unconditional objection to direct marketing. Respond within one calendar month; a lawful extension of up to two further months requires timely notice. You may complain to your local supervisory authority. |
| California and other US states | Where relevant statutes cover the processing, rights may include knowledge/access, correction, deletion, portability, opt-outs from sale/sharing or targeted advertising, limits on sensitive uses and an appeal. California access, correction and deletion generally have a 45-day response period, with a permitted further 45 days on notice; our shorter target still applies. |
| Canada, Australia, Brazil and South Africa | Local rights may include access, correction, consent withdrawal, objection, deletion and a complaint to the competent regulator. Brazil provides immediate simplified confirmation/access or a complete statement within 15 days where Article 19 applies. Local deadlines and any stronger protections take priority. |
15. Appeals, preferences and complaints
Reply to the decision or contact us with “Privacy appeal”. We arrange review and respond within 30 days or a shorter required period. You may complain directly to the NDPC, an EEA supervisory authority, the UK ICO, a US state authority, Canada’s OPC, Australia’s OAIC, Brazil’s ANPD, South Africa’s Information Regulator or another competent body. Our process does not restrict that right. We honour legally required opt-out signals, including Global Privacy Control, for covered activities.
16. Changes
We publish the adopted policy’s effective date and version and highlight material changes before they take effect where required. We obtain new consent where needed; continued use does not authorise a new consent-based purpose.