About These Guidelines
These are the operational guidelines of KF.Social, a social application operated by KaneFilous Limited, for law enforcement agencies, prosecutors, courts, regulators and other government authorities seeking information about a KF.Social member or account.
KF.Social helps adults make friends through Plans, Clubs, posts and private messages. Accounts are personal, and the records described below are personal data of identifiable people. We treat every request for them as a serious interference with those people's rights, and we handle each one on its own facts.
These guidelines explain what to send us, where to send it, what legal process we require before we disclose, what categories of record we are likely to hold, and how long we hold them. They are written to help you prepare a request we can act on without a further round of correspondence.
These guidelines are for information only. They are not legal advice, they do not create any right or expectation for any person, and they are not a submission to the jurisdiction of any court or authority. Nothing here waives any objection, privilege or defence available to KaneFilous Limited or to our members, and nothing here obliges us to produce information that we are not lawfully required to produce.
Who to Serve
KF.Social is operated by KaneFilous Limited, a private company limited by shares registered in Ireland under company number 680584, with its registered office at 60 Merrion Square South, Dublin 2, D02 HE24, Ireland. KaneFilous Limited is the data controller for personal data processed through KF.Social.
KaneFilous Limited is the only correct respondent for a request about a KF.Social account. We have no subsidiary, branch or affiliate in any other country that can receive service on our behalf, and our service providers are processors acting on our instructions rather than holders of the records in their own right. Legal process addressed to a service provider, an app store, a hosting provider or any other third party does not reach us and we will not treat it as served.
How to Send a Request
Send your request by email to legal@kf.social, with the signed legal process attached as a PDF. Email is our preferred route and the fastest one. Requests may also be sent by post to the registered office above; postal requests take materially longer to reach the right person and we recommend emailing a copy at the same time.
Requests must be submitted in English or accompanied by an English translation. We do not accept service, and we cannot discuss a request, by telephone, through in-app support, through our social media accounts, or through any channel other than the two above.
Please send the request from an official government email domain, and include the following, so that we can authenticate it and identify the account without writing back to you:
- The issuing authority, the name, rank or title and direct contact details of the officer responsible, and a case or reference number.
- The signed legal process itself, and the statutory provision or instrument under which it is issued.
- The account identifier. The most reliable identifiers are the profile URL (kf.social/u/<handle>), the handle, and the email address used to sign in. A display name alone is not an identifier: display names are not unique and members change them.
- A precise description of the records sought, by category, and the date range they relate to, in UTC. A request for "all data" or with no date range is overbroad and we will ask you to narrow it.
- Where content is sought, the specific posts, messages, conversations or media at issue, identified as closely as you can.
- Any statutory non-disclosure obligation, with the provision it arises under and the period it runs for. See Notice to Our Members.
- Your deadline, and whether the matter is an emergency.
A request that does not identify an account we can locate, or that does not attach the legal process it relies on, cannot be actioned and will be returned to you.
Legal Process We Require
We disclose member information only where we are compelled to do so by valid legal process binding on KaneFilous Limited in Ireland, or where the emergency disclosure exception applies. An informal request, a police letter, a badge number or an assertion of urgency is not legal process, and we will decline it. We assess every request against the law that applies to us, including the General Data Protection Regulation, and we narrow, object to or decline requests that are overbroad, unclear, disproportionate, or issued without authority.
We ask for the following, by category of record:
- Basic subscriber information (the existence of an account, registration email address, handle, account creation date, and the most recent sign-in records we hold) - valid compulsory legal process from a competent authority, addressed to KaneFilous Limited.
- Other non-content records (account status and enforcement history, booking and payment references, device and technical records, and records of reports made about or by the account) - valid compulsory legal process from a competent authority, addressed to KaneFilous Limited.
- Content (the text or media of private messages, posts, comments, stories, uploaded photos and video, and identity-verification material) - a court order or equivalent judicial authorisation. We do not disclose content on the basis of an administrative or police-issued instrument alone.
- Special category data (biometric identity-verification data, and dietary or allergy information given for a Plan, which is health data under Article 9 GDPR) - a court order or equivalent judicial authorisation that addresses the category expressly. Dietary and allergy information is held for the safety of the member and is never shared with venues; we will resist a request that sweeps it in without consideration.
These are the minimum standards we apply. Meeting them does not guarantee disclosure: the request must also be lawful, proportionate and sufficiently particularised, and we may still object or seek clarification.
Requests From Outside Ireland
We are established in Ireland and hold the records in the European Union. Legal process issued by an authority outside Ireland does not bind us simply because it is valid where it was issued, and we cannot act on it directly.
If you are an authority outside Ireland, please use the route that makes your request binding on us here. Depending on where you are, that is likely to be:
- a mutual legal assistance (MLAT) request through the Irish Central Authority for Mutual Assistance at the Department of Justice;
- a European Investigation Order, where you are an authority of a participating EU Member State and the instrument is available for the measure you seek;
- a European Production Order or Preservation Order under Regulation (EU) 2023/1543, from the point at which it applies to the measure and the authority concerned; or
- an order of an Irish court, obtained by the appropriate domestic authority.
We will accept a valid instrument of this kind on its own terms. Where no such route is available to you, we may still be able to help with a preservation request while you obtain one, and with an emergency disclosure where a life is at risk. You are welcome to write to us before you start, to confirm that an account exists and that we hold records of the kind you need, so that the process you obtain is targeted.
Emergency Disclosure
Where we form a good-faith belief that there is an imminent risk of death or serious physical injury to a person, and that the information we hold would help prevent or mitigate it, we may disclose that information to law enforcement voluntarily, without compulsory legal process. This is an exception for genuine emergencies, and we read it narrowly: an urgent investigation is not, by itself, an emergency.
To make an emergency request, email legal@kf.social from an official government email domain with EMERGENCY DISCLOSURE REQUEST in the subject line, and include:
- the nature of the emergency and the specific harm you are seeking to prevent;
- why you believe the harm is imminent, rather than serious but not immediate;
- the person at risk, and the account or accounts involved, identified as in How to Send a Request;
- exactly what information you need and how it would help prevent the harm; and
- your name, rank or title, agency and a direct telephone number we can call back on.
We review emergency requests ahead of all other correspondence. We decide each one on the information in front of us, and we may disclose only the part of what you asked for that the emergency justifies. If the emergency passes or the facts do not support it, we will tell you and ask you to proceed by ordinary legal process. We keep a record of every emergency disclosure we make and of the basis for it.
Preservation Requests
Records on KF.Social expire on the schedules described in our Privacy Policy, and members can delete their own content and their accounts at any time. If you expect to seek records, ask us to preserve them before they expire.
Send preservation requests to legal@kf.social with PRESERVATION REQUEST in the subject line, identifying the account and the categories and date range to be preserved. A preservation request does not need compulsory legal process, and we will act on a formal request from a law enforcement agency.
On a valid request we take a snapshot of the records we hold at that moment and hold it, separately from the live service, for 90 days. We extend it for one further period of 90 days on a renewed request before the first period ends. Preservation is not disclosure: it only stops the records expiring while you obtain the legal process needed to compel their production. We will not preserve indefinitely, and if no legal process arrives before the preservation period ends, the snapshot is released and the ordinary retention rules resume.
We can only preserve what exists when the request reaches us. A record that has already expired or been deleted cannot be recovered by a preservation request.
Records We May Hold
What we hold for a given account depends on how the member has used the service and how long ago. Our Privacy Policy is the authoritative description, and its Retention section states the periods. In outline:
- Account records - registration email address, handle and display name, profile details and photos, date of birth and age eligibility, and the sign-in methods used. Kept while the account is active.
- Content - posts, comments, reactions, stories, Club posts and Club chat, and direct messages including text, voice notes, photos and video. Kept while the account and the content remain active, subject to the member's own deletion and to disappearing-message settings.
- Plans and bookings - the Plans an account hosted or joined, join and cancellation status, and the booking and payment references for a paid Plan.
- Payment records - booking and payment references, amounts, currency, payment and refund status, and reconciliation records. Kept for the applicable accounting and tax period. Card details are processed by Stripe and never reach our systems.
- Identity verification - verification status, document type and country, decision records, and, where an automated check succeeded, a biometric face template. Raw document and selfie images are scheduled for deletion after a final decision; the raw-image store has a 30-day expiry rule.
- Reports, moderation and enforcement - reports made about or by the account, blocks, moderation decisions and enforcement actions. Selected enforcement, report, moderation and audit records use a seven-year retention period.
- Restricted moderation evidence - where our automated screening identifies prohibited content, a copy is written to an access-restricted store held separately from the live service, protected against routine deletion for 90 days with a 100-day expiry target, unless a preservation requirement or legal hold extends it.
- Where a member is based, and travel - the area a member has chosen as their base, trips, and area centre points. A trip ends at most 30 days after it starts.
- Live location shares - a member can start a live location share inside a direct message. The session record is scheduled to expire six hours after its scheduled end; a location sent as a chat message follows conversation retention.
- Call records - metadata for voice and video calls, such as who called whom and the duration.
- Technical records - device and push notification tokens, app version, and service, access and diagnostic logs. Logs expire automatically after no more than 90 days, and most application logs after 30 days. This is the shortest-lived category and the one most often lost before a request arrives; if you need technical records, send a preservation request first.
What We Do Not Have
So that you do not spend time seeking records that do not exist:
- Card numbers. Payment is processed by Stripe: card details are entered directly into Stripe's payment interface on the member's device and never touch our systems. We do not store full card numbers or card security codes. For the card itself, address Stripe.
- Call audio and video. Voice and video calls are not recorded by us. We hold call metadata only.
- Real-time interception. We have no facility to intercept, wiretap, mirror or monitor a member's communications in real time, and we will not build one in response to a request.
- Continuous location history. We do not keep a continuous trail of a member's movements. Location is the area they chose as their base, trips, and a live share the member starts themself and that expires as described above.
- Expired or deleted records. Once a retention period ends or a member deletes their account, the records are deleted, redacted or pseudonymised and we cannot produce them. Database point-in-time recovery currently covers up to 35 days, is not an archive, and is not available for ordinary production.
- Records held by others. App store purchase records held by Apple or Google, and records held by our analytics, mapping or payment providers in their own right, must be sought from those companies.
Notice to Our Members
Our policy is to notify the member whose information is sought before we disclose it, and to give them a reasonable opportunity to object, so that they can seek to challenge the request themselves. Members are also told, through our Privacy Policy, that we may disclose personal data where required by law.
We will not give notice where:
- we are prohibited by law or by a court order from doing so, for the period that prohibition runs;
- the request is an emergency involving an imminent risk of death or serious physical injury;
- the request concerns child sexual abuse or exploitation; or
- we have reason to believe that notice would create a risk of serious harm to a person, or would lead to the destruction of evidence or to flight.
If you need notice withheld, say so in your request and identify the statutory provision or order that requires it, and the period it runs for. A general preference for confidentiality is not a basis for withholding notice. Where a non-disclosure obligation expires, we may notify the member then.
How We Respond
We acknowledge requests promptly and work through them in the order they arrive, with emergency and child safety requests taken first. We will tell you if a request will take longer than the deadline you have given us, and we would rather agree a realistic date with you than miss one.
We respond by email to the official government address the request came from, and we encrypt the response. Tell us in your request if you need a different secure route or a specific format. We produce records as they are held: we do not interpret them, summarise them, or draw conclusions from them on your behalf.
We produce only what the legal process compels and what the request describes. Where a request is broader than its stated purpose, we will narrow it and say what we have withheld and why. Where we decline a request, we will say so and give our reason.
Child Safety Requests
Requests concerning child sexual abuse and exploitation are prioritised above all other correspondence. Send them to childsafety@kf.social, which reaches our child safety team directly, and to legal@kf.social if the request carries legal process.
Our prohibitions, detection measures, reporting routes and response steps are set out in full in our published Child Safety Standards. We act on preservation requests from law enforcement and child protection agencies, we cooperate with lawful requests in this area, and we report confirmed material to the appropriate authorities and child protection bodies in line with our obligations.
Costs, Records and Testimony
We do not currently charge for responding to law enforcement requests. We reserve the right to seek reimbursement of the costs of responding where the law permits it and the request is unusually burdensome.
We keep a record of every request we receive, what we disclosed, and the basis for it, and we may report aggregate, non-identifying figures about government requests in a future transparency report.
Where a certificate or affidavit is needed to authenticate the records we produce, ask for it in your request and we will consider it. We do not undertake to provide a witness, to give evidence in person, or to act as an expert, and any such request must be made through the appropriate legal process.
Review of These Guidelines
We review these guidelines at least annually, and sooner where the law changes or where what we learn from handling requests tells us they should be clearer. The version number and effective date at the top of this page record the current revision. Material changes are reflected here on publication.
These guidelines operate alongside our Terms of Service, our Privacy Policy, our Child Safety Standards and our Digital Services Act transparency statement. The notice and reporting routes for illegal content under the Digital Services Act, which are open to authorities as well as to users, are described on that page.
Law Enforcement Contact
KaneFilous Limited maintains a point of contact for law enforcement and other government authorities in relation to KF.Social. It is available from anywhere in the world and you do not need an account to use it. Communications must be submitted in English.
- Law enforcement and legal requests: legal@kf.social
- Child safety: childsafety@kf.social
- Data protection and member rights: privacy@kf.social
- Postal address: KaneFilous Limited, 60 Merrion Square South, Dublin 2, D02 HE24, Ireland, +353 89 941 7178
Mark emergency requests EMERGENCY DISCLOSURE REQUEST and preservation requests PRESERVATION REQUEST in the subject line. If a person is in immediate danger, contact your local emergency services first.
These are the published law enforcement guidelines of KF.Social, operated by KaneFilous Limited, setting out the legal process we require before disclosing member information, our emergency disclosure and preservation practices, the records we hold and how long we hold them, and our law enforcement point of contact. They are not legal advice and create no rights. Version 1.0. Effective 26 October 2026.