Privacy Policy

Last updated: 5 November 2026 · Version 2026.11.05

This Privacy Policy explains how Entity Promotions LTD (company number NI721452), a private limited company registered in Northern Ireland, trading as "Swingable" (the "Company", "we", "us"), processes personal data of Members and visitors of the Swingable platform (the "Platform"). It should be read alongside our Terms of Service and Cookie Policy. We act as the Controller of your personal data within the meaning of the UK GDPR and the Data Protection Act 2018.

Swingable is an adult social service. Much of what you choose to share on it will reveal information about your sex life or sexual orientation. Clause 6 explains the additional Article 9 requirements and your choices, and clause 15 explains how to complain.

1

Controller identity & contact

1.1

The Controller is Entity Promotions LTD, a private limited company registered in Northern Ireland (company number NI721452) whose registered office is at 3 Wellington Park, Belfast, BT9 6DJ.

1.2

Privacy contact. Data-protection queries, rights requests and data-protection complaints should be sent to admin@swingable.co.uk.

1.3

Privacy responsibility. The directors of Entity Promotions LTD are responsible for data protection. Send rights requests, complaints and questions to admin@swingable.co.uk. The need for a statutory Data Protection Officer depends on the nature and scale of processing, not company size alone; this notice does not claim an exemption from that requirement.

1.4

Sale and measurement. We do not sell member databases. Optional Google and Meta tags can disclose identifiers and page/event information to those providers when enabled; see clause 8.10 and the Cookie Policy. This is separate from necessary service-provider processing. The Cookie Policy explains the current controls and the information those tags may disclose.

2

Definitions

2.1

"Personal Data" has the meaning given in Article 4(1) of the UK GDPR. "Processing" has the meaning given in Article 4(2). "Special Category Data" has the meaning given in Article 9. "Member" means a person with an individual Member Account. "Shared Profile" means a shared identity that two or more Members act through. "Processor" means a third party processing Personal Data on our documented instructions.

3

Categories of personal data we collect

3.1

Account & identity data. Username, email address, date of birth, gender, orientation, relationship configuration, hashed password, and profile photographs.

3.2

Shared Profile data. Which individual Member Accounts belong to which Shared Profile, the relationship label chosen, join/leave events, and a record of which individual login performed each action taken through a Shared Profile (actor attribution). Some attribution is displayed to the permitted audience on Content. Where a Member leaves a Shared Profile, their individual membership of it ends, but the Shared Profile itself and its Content are not deleted as a result; the Shared Profile may instead be archived or continue to be used by its remaining Members.

3.3

Verification data. A selfie photograph of you holding a handwritten sign showing your username and today's date, submitted for photo verification. That single image is used both to check authenticity (that the person behind the account is a real, present person) and as part of our age assurance process. We apply a Challenge 25 approach: if the reviewer considers you may be under 25, or is not confident of your age from the photo alone, a government-issued identity document showing your date of birth is mandatory before the account can be approved. Images are reviewed visually by human moderators. We do not generate a biometric template from your face and we do not perform automated facial recognition or automated face-matching; the images are photographs assessed by people. We do not hold or claim any Ofcom certification in respect of this process.

3.4

Content and activity. Posts, stories, photos, videos, Vault classifications and approvals, direct and shared-inbox messages, polls, reactions, winks, forum threads, replies, quotations, votes, reports and moderator redactions. We also process feed choices and limited history used to order the feed. Community groups, group chats and chat rooms are no longer available.

3.5

Vault consent data. For each media item: your classification of who appears in it, the registered Members you tagged, and each tagged person's approval, decline or later withdrawal, with timestamps. Where you tag a registered Member, that item does not proceed to moderation review, and is not published, unless and until each tagged Member approves it; if a tagged Member declines, the item is deleted. Where a person shown in the media is not a Member or has not been tagged, we rely on your classification and the uploader's own consent declarations rather than a technical block, and such items may still be reported and actioned like any other Content.

3.6

Payments. Stripe processes card payments for Invite+ and merchandise. We receive transaction and subscription references, payment status, billing information and limited card metadata; we do not store full card numbers or security codes. We process delivery details for merchandise and retain relevant earlier ticket and organiser-payment records. New Event adverts link to external sellers: data you give them is handled under their own notices.

3.7

Device & technical data. IP address, a device fingerprint derived from browser and device characteristics, browser type, operating system, timezone, referral URL, app version, and error logs. Fingerprinting, account-linkage and ban-evasion signals derived from this data may be retained for safety and fraud-prevention purposes; see clauses 5 and 10.

3.8

Location. We process the area or postcode you provide and, for location features you turn on, a device position. Meet Mode uses a captured position on our servers for up to four hours, including while the phone is locked or the app is closed; it does not continuously track movement in the background. Update the position if you move or turn the mode off. Precise coordinates are not shown to other Members, although proximity and pairing results may reveal that people were near each other. Nearby indicators are approximate.

3.9

NFC band data. Where you use a Swingable NFC band, the band identifier, its link to your account, and check-in or meet-verification events recorded when it is used.

3.10

Push notification data. Where you enable push notifications in the mobile app, a device push token issued by the operating-system push service (Apple Push Notification service on iOS, Firebase Cloud Messaging on Android), together with your notification preferences.

3.11

Legacy Telegram integration data. The Telegram integration has been removed. We no longer offer account linking or conversation syncing. Previously stored connection and message records remain subject to the retention and deletion provisions in this policy.

3.12

Safety, moderation & enforcement data. Reports you make or that are made about you, moderator decisions and notes, appeals, risk signals used to prioritise review, multi-account and account-creation-limit signals derived from device fingerprints, ban and block records, and visibility restrictions applied to an account or item.

3.13

Security provenance data. Media shown on the Platform may carry a per-viewer, per-media pseudonymous provenance identifier, together with associated access records. These are used only to investigate leaks or misuse of private media and to support reports of non-consensual sharing. We do not publish the methods or algorithms involved. Access to this data is restricted to a small number of authorised staff.

3.14

Organiser and business records. Organiser approval, listing ownership, event adverts, cover images, external ticket links and contact details. We may also retain earlier ticket, payout, advertiser, Club, Partner or Ambassador records where needed for accounting, disputes or safety. Retired features do not create new access to those records.

3.15

Legal acceptance records. The document and version you accepted, with a timestamp, so we can demonstrate what you agreed to.

3.16

Retired chat rooms. Chat rooms are no longer available and no new room sessions are created. Previously captured report evidence remains subject to the safety retention rules at clause 10.4. This does not change private messages, verification photos or Vault media.

3.17

Special Category Data. Because the Platform is an adult social service, information you submit will reveal data concerning your sex life or sexual orientation within the meaning of Article 9(1) UK GDPR. Additional safeguards apply, described at clause 6.

4

Sources of personal data

4.1

From you. Directly during registration, verification, use of the Platform, or when contacting support.

4.2

From other Members. Where other Members mention you, tag you in Vault media, report you, verify you, or otherwise reference you.

4.3

From our processors. Payment outcomes from Stripe, email delivery and engagement status from Amazon SES, media processing status from our video provider, and fulfilment status from our print partner.

5

Purposes of processing & Article 6 lawful bases

5.1

Providing requested services — Article 6(1)(b). Account and shared-profile administration, messages, forums, media, requested feed ordering, event adverts, subscriptions, merchandise and support. We use necessary account and interaction information for these purposes. This contract basis is not sufficient on its own for special category data; clause 6 applies separately.

5.2

Safety, moderation and illegal-content duties — Art. 6(1)(c) (legal obligation) and Art. 6(1)(f) (legitimate interests). Complying with the Online Safety Act 2023, checking that Members are adults, detecting and removing illegal or harmful Content, handling reports and appeals, and protecting Members from harm. Our legitimate interest is running a safe service for adults; we balance it against your interests and provide the appeal route in the Terms.

5.3

Fraud prevention and account integrity — Art. 6(1)(f). Device fingerprinting to enforce account-creation limits and detect ban evasion, chargeback-abuse detection, and provenance tokens on media to investigate leaks.

5.4

Optional features — Art. 6(1)(a) (consent). Nearby and Meet Mode location, push notifications, non-essential cookies and optional marketing. You can withdraw any of these in Settings or by using the unsubscribe link, without losing access to the rest of the Platform.

5.5

Legal and accounting — Art. 6(1)(c). Retaining transaction records to meet tax and accounting duties and responding to lawful regulatory or law-enforcement requests.

6

Special category data — Article 9 condition

6.1

An Article 6 lawful basis is not enough on its own for data revealing sex life or sexual orientation. A separate Article 9 condition is also required, and we treat these as two distinct questions.

6.2

Explicit consent — Article 9(2)(a). Ordinary use of sensitive lifestyle information requires an identified Article 9 condition. Where we rely on explicit consent, it must be specific, informed and separately expressed; accepting general Terms, joining the site or leaving a setting enabled is not a substitute. A consent record must identify the purposes agreed to. This notice does not itself obtain consent or turn an existing account, profile setting or earlier activity into a separate consent record.

6.3

Public information is a narrow exception. Article 9(2)(e) applies only to information you deliberately make manifestly public. A member-only profile, feed post, forum thread, direct message or Vault item is not treated as manifestly public merely because other Members can see it. We do not use this exception as a blanket basis for the community.

6.4

Legal claims — Art. 9(2)(f). Where processing is necessary for the establishment, exercise or defence of legal claims, including defending moderation decisions and responding to complaints.

6.5

Specific safety and legal purposes. A legal-claims or safeguarding condition may apply to a particular necessary investigation where its legal tests are met. It does not provide a general basis for everyday social profiling, messages or marketing. Where a Schedule 1 condition requires an appropriate policy document, that document and the relevant safeguards must be in place. Processing without a valid applicable condition must not proceed.

6.6

Withdrawing consent. Where processing relies on explicit consent, you can withdraw it by contacting admin@swingable.co.uk. We must stop the affected consent-based processing and explain any feature that cannot be provided without it. We must not bundle unrelated optional processing into a condition of access. Withdrawal does not affect earlier lawful processing; any continued retention needs its own valid basis and, where applicable, an Article 9 condition. Pausing an account is not itself withdrawal or erasure.

7

Marketing & electronic messages

7.1

Consent. We only send electronic direct marketing where PECR permits it — either because you have given consent, or because a valid soft opt-in applies (clause 7.2) — and every marketing message includes a means of opting out. Opting in is separate from accepting the Terms and is never a condition of using the Platform.

7.1a

Preferences and permission. An enabled email preference is not proof of consent. Invitations, return-to-site reminders, offers and promotional digests are marketing even when they describe activity on Swingable. They require a valid marketing permission or an applicable soft opt-in; having an old account or email address alone is not sufficient. Marketing opt-out does not stop necessary security, verification or billing messages.

7.2

Soft opt-in. Where you have bought or negotiated to buy a product from us, PECR permits us to email you about our own similar products and services, provided we gave you a simple means of refusing at the point your address was collected and in every message. We rely on this only within those limits.

7.3

Service messages. Transactional and safety messages (billing, verification outcomes, moderation decisions, security alerts) are not marketing and are sent for as long as you hold an account.

7.4

Opting out. Every marketing email contains an unsubscribe link, and you can change your preferences in Settings at any time.

8

Sharing with processors & third parties

8.1

We share Personal Data with the following recipients, each acting under a written data-processing agreement or, where indicated, as an independent controller. This list reflects the integrations actually implemented in the Platform.

8.2

Infrastructure. Amazon Web Services provides the current application hosting, authentication gateway, database, file storage, processing and delivery infrastructure. Authorised staff and service providers access data only for their permitted operational purposes.

8.3

Payments. Stripe provides payment and subscription services and processes card data under its own legal responsibilities as well as our payment arrangements. Current payments include Invite+ and merchandise; retained records may include earlier event ticket sales.

8.4

Email. Amazon SES delivers authentication, service and permitted marketing emails. Delivery events and, where enabled, open/click events can be processed. Opening or clicking an email can generate measurement data; marketing messages include the applicable unsubscribe route. Technical delivery logs are distinct from permission to send marketing.

8.5

Media. Current uploads and video processing use AWS storage and media services. Older media or an enabled legacy broadcast may use Cloudflare Stream where its delivery address is retained. Media access remains subject to its audience and signed-delivery controls; using a delivery provider does not make private media public.

8.6

Retired chat rooms. Chat room camera and microphone connections are no longer offered. Previously captured report evidence remains subject to the safety retention rules at clause 10.4. This does not change private messages, verification photos or Vault media.

8.7

Merchandise fulfilment. Printful receives the order, product and delivery details needed to make and fulfil your merchandise order.

8.8

Push notifications. Apple Push Notification service and Firebase Cloud Messaging, where you enable push in the mobile app.

8.9

Former Telegram integration. The integration has been removed; Swingable no longer syncs data with Telegram. Telegram remains an independent controller for its own service.

8.10

Optional measurement. The current analytics setting also controls loading of Meta Pixel and Google advertising tags. These can send identifiers and page/event information to those providers. Swingable’s own feed and Invite+ reporting also checks the browser’s analytics choice. Use the Cookie Policy controls to change your choice without losing account features. Reload open pages after refusing optional tracking; already loaded tags may continue until then. This notice does not authorise new processing or replace the Article 9 requirements in clause 6.

8.11

Moderators. Our internal moderation team and, where engaged, vetted external moderators bound by confidentiality obligations.

8.12

Event organisers and external sellers. Following a ticket link takes you to a separate seller with its own privacy terms. An advert does not send the organiser your private profile or payment details. Earlier Swingable orders may require limited purchaser information to fulfil or resolve that booking. Where the internal order-reveal facility is available, access is limited to authorised organisers for that event and each deliberate billing-details view is audited.

8.13

Regulators and law enforcement. Where required by lawful request, or where reporting is required or justified to protect people from serious harm, including reporting child sexual exploitation and abuse to the National Crime Agency where the statutory duty applies.

9

International transfers

9.1

Where Personal Data is transferred outside the United Kingdom, we rely on (a) an adequacy regulation of the UK Government, or (b) the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses, together with supplementary technical and organisational measures.

9.2

Members located outside the UK. We accept Members who access the Platform from outside the United Kingdom. This Policy, and the Terms of Service, are nonetheless governed by the law of Northern Ireland, and the protections described in this Policy apply regardless of where you access the Platform from.

10

Retention

10.1

Retention approach. We retain information only for a necessary purpose and review whether it can be deleted or de-identified. Some limits are enforced by scheduled cleanup; other records require manual review. Expiry from display, removal of an author link and deletion from every storage system are different. A legal hold can delay deletion of specifically relevant evidence, but is not a reason to retain everything indefinitely.

10.2

Active accounts. Account and Content data is retained for as long as your Member Account remains active.

10.3

Deletion and surviving conversations. Account deletion does not necessarily remove forum threads or replies: the author link may be removed and the contribution labelled “Deleted User”. Identifying text can still be personal data. Shared-profile contributions and messages held by other authorised participants may also remain. Ask us to review personal details or content that should be erased; statutory erasure rights and necessary safety/legal exceptions still apply. Deleted material may remain temporarily in restricted backups pending their normal replacement.

10.4

Financial, safety and dispute records. Transaction records, moderation decisions, reports, appeals, evidence and limited anti-fraud indicators may need longer retention than an account. Retention must be justified by the applicable accounting requirement, an actual or reasonably anticipated claim, or a documented safety purpose. Several categories rely on manual review rather than an automatic deletion period. You can ask for the category-specific period or criteria and request erasure.

10.5

Verification images. Government-ID images are deleted through the review workflow when a decision is made, including rejection or a request to resubmit. The handwritten-sign verification photo is stored separately and is retained while the account is active as evidence of verification, subject to account deletion and any necessary, documented safety/legal hold. Minimal decision metadata may be retained separately. These two image types do not have the same retention rule.

10.6

Stories. Ordinary stories normally stop displaying after 24 hours. An official promotional story may have a different stated expiry. Display expiry does not guarantee immediate deletion of every stored copy, backup or item held for a necessary moderation investigation.

10.7

Meet Mode and feed records. Saved-location pairing is limited to the active Meet Mode window of up to four hours; server cleanup handles expired coordinates. Pairing and verification records are separate from those coordinates. Feed ranking uses a bounded seven-day seen-post window (up to 500 entries); inactive history records are cleaned up after 30 days. Hide post and Show less preferences expire after 30 days. Consent-gated feed reporting records have 70-day retention; the admin reader returns aggregate results with a minimum five-viewer threshold, not a list of individual browsing histories.

10.8

Retired features. Legacy group content and group chats were removed when Forums replaced them. Other retained evidence or records from retired features, including earlier Telegram links and safety reports, remain subject to their purpose-specific retention and erasure rules. Retirement is not permission for new collection.

10.9

Other categories. Where a category is not listed above we keep it only for as long as it is needed for the purpose it was collected for, retained no longer than necessary, and we review retention periodically. If you want to know the position for a specific category, ask us at admin@swingable.co.uk.

11

Your rights

11.1

Under the UK GDPR you have the right to: (a) access your Personal Data; (b) request correction of inaccurate data; (c) request erasure; (d) restrict processing; (e) data portability; (f) object to processing based on legitimate interests or for direct marketing; and (g) withdraw consent where processing is based on consent.

11.2

How to exercise, and how long we take. Contact admin@swingable.co.uk. We will respond without undue delay and in any event within one month of receiving the request. Where a request is complex, or where you have made a number of requests, we may extend that period by up to a further two months and will tell you within the first month if we do. We may ask for information reasonably necessary to verify your identity. There is no fee unless a request is manifestly unfounded or excessive.

11.3

In-product tools. You can delete your account, or pause it temporarily, from Settings → Data. An in-product self-service data export is not currently available; ask us at admin@swingable.co.uk and we will provide a copy of your data.

11.4

Limits. Some rights are qualified. For example, we may decline erasure where retention is necessary for legal claims, accounting, or the protection of others.

12

Automated decision-making & profiling

12.1

Feed ordering and measurement. “For you” uses a server-side rules-based algorithm, not generative AI. It considers eligible posts, recent interactions, seen-post history, recency and variety; Show less reduces similar author content and Hide post removes that item from your feed for the applicable period. “Most recent” primarily orders eligible posts by time. Featured posts, verification summaries and inserted forum/event/store placements can affect presentation in both modes. Privacy and block checks still apply. Personal and shared-profile preferences are scoped separately. Optional aggregate reporting requires analytics consent; essential service operations and the feed choices you request are distinct from that reporting.

13

Security

13.1

We maintain appropriate technical and organisational measures including encryption in transit and at rest, role-based access controls, row-level security on our database, signed time-limited URLs for private media, staff access controls, and security testing. No system is perfectly secure; please notify us immediately of any suspected breach at admin@swingable.co.uk.

13.2

Personal data breach notification. Where a personal data breach is likely to result in a risk to your rights and freedoms, we will notify the Information Commissioner's Office within seventy-two (72) hours of becoming aware in accordance with Article 33 UK GDPR and, where the risk is high, notify affected Members without undue delay under Article 34.

13.3

Child sexual abuse material. Such material is prohibited absolutely. Where it is detected through reporting or moderator review it is preserved on legal hold, the account is terminated, and it is reported to the National Crime Agency where the statutory duty applies and, where appropriate, to the Internet Watch Foundation or the police.

13.4

Private messages. Direct messages are not end-to-end encrypted. Authorised shared-profile participants can read their shared inbox. The former AI explicit-text screening and media-permission request system are no longer active. Reporting, account privacy, blocking and safety investigations remain. Staff access must be limited to a necessary, authorised purpose; this notice does not promise that every legacy access path has a verified per-view audit trail.

14

Children

14.1

Under-18 accounts. Swingable is restricted to adults. If we discover an under-18 account, we restrict access, investigate and remove data that should not be held, subject to necessary lawful safeguarding or evidential retention. Notify admin@swingable.co.uk if you suspect a child is using the service. We do not intentionally permit children to use member features.

15

Data-protection complaints

15.1

How to complain to us. If you are unhappy with how we handle your personal data, send a data-protection complaint to admin@swingable.co.uk with the word "data protection" in the subject line. You can also raise it through the in-app contact form.

15.2

What we will do. In line with the Data (Use and Access) Act 2025 we will acknowledge your data-protection complaint within thirty (30) days of receiving it, take appropriate steps to investigate it without undue delay, and tell you the outcome.

15.3

Escalating to the regulator. You may complain to the Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, telephone 0303 123 1113, website ico.org.uk. The ICO may ask whether you have raised the matter with us first.

16

Deceased Members

16.1

On satisfactory evidence of death we will memorialise, restrict or delete the account in line with the deceased Member's documented wishes or reasonable requests from their personal representative. We do not grant access to a deceased Member's private messages.

17

Changes to this Policy

17.1

We may amend this Policy from time to time. Each version carries a version number and date at the top of this page. Material amendments will be notified in-app or by email at least fourteen (14) days before they take effect.