Function lets people upload things: event cover photos, profile pictures, photos and clips from events, review photos, and text. Almost all of it is created by the person posting it. Some of it won't be.
This page is Function's process for handling claims that something on the platform infringes someone's copyright, under the Digital Millennium Copyright Act (17 U.S.C. § 512). If you own a copyright in something posted here without your permission, section 3 tells you how to have it removed. If something of yours was removed and you believe that was a mistake, section 6 tells you how to respond.
The DMCA is a copyright statute and nothing else. It does not create a takedown process for other kinds of claims, and several of those are more common at an events platform than copyright is:
Those are real claims and Function will act on them. They just don't travel through this page. Send them to hello@function.cx with a description of the problem and a link to the listing, profile, or post.
Send copyright notices in writing to Function's copyright contact:
Copyright notices — Function
Email: hello@function.cx — put DMCA notice in the subject line.
Postal:
We make the function LLC
Attn: DMCA Agent
1183 University Drive, Ste 105 #2292
Burlington, NC 27215
United States
Notices sent to either address above are read and acted on. Function's designated agent is not yet on file with the U.S. Copyright Office, and until that registration is complete Function cannot rely on the section 512(c) safe harbour. That is a filing Function still owes; it does not change how a notice you send is handled.
You do not need a Function account to send a notice. Do not use the in-app Report button for a copyright claim — see section 9.
To be effective, 17 U.S.C. § 512(c)(3)(A) requires a notice to include substantially all six of the following. A notice missing any of them may not obligate Function to act.
Note where the perjury statement attaches: to your authority to act for the owner, in item 6. It is not a sworn statement that the material infringes.
If your notice is incomplete but does identify the work, the material, and how to reach you, Function will reply and tell you what's missing rather than ignore it.
On receiving a notice that meets section 4, Function will act expeditiously to remove the material or disable access to it, and will take reasonable steps to notify the person who posted it — including a copy of the notice, so they can respond.
What "removed" means here, precisely. Taking material down removes it from the platform: the listing, post, review or profile stops being served to anyone. Where the material is an image or clip, the underlying file also has to be deleted from Function's media storage, and that is a separate step from removing the item that showed it. Until that deletion completes, a direct file link somebody copied earlier can still resolve, because those links are long, unguessable and unsigned rather than access-controlled. If your notice concerns an image or a clip, say so and we will confirm the file itself is gone, not just the post around it.
Function does not publish a fixed turnaround time. The statute requires acting expeditiously and deliberately does not define that in hours; a specific number here would be a promise about staffing rather than about copyright.
Removing material is not a finding that anyone infringed anything. It's the response the statute requires while the two parties sort it out.
If your material was removed and you believe it was a mistake or a misidentification — for example, you hold the rights, you have a licence, or your use is fair use — you can send a counter-notification to the same address in section 3.
Under 17 U.S.C. § 512(g)(3), a counter-notification must include:
Read item 4 carefully before sending one. A counter-notification is not an appeal to Function; it is a step that hands the dispute to the courts. Function is required to forward a copy of your counter-notification, including your name and address, to the person who filed the original notice.
When Function receives a counter-notification that meets section 6, it will promptly send a copy to the person who sent the original notice and tell them the material will be restored in 10 business days.
Function will then restore the material not less than 10 and not more than 14 business days after receiving the counter-notification — unless it first receives notice that the complaining party has filed a court action seeking to restrain the poster from the activity in question. If that happens, the material stays down.
What Function can actually put back depends on what was taken down. An event listing can be restored as it was. A post or a review cannot — taking one down deletes it, and Function does not keep a hidden copy to reinstate. For material of that kind, restoring means Function will lift the block and tell the complaining party the material is being restored, but you will need to post it again yourself, and any media file will need to be re-uploaded. This is a limitation of how the platform stores that content, and it is stated here rather than discovered at day 14.
Under 17 U.S.C. § 512(f), anyone who knowingly materially misrepresents that material is infringing — or that material was removed by mistake — can be held liable for damages, including costs and attorneys' fees, incurred by the other party and by Function.
That applies to notices and counter-notifications equally. Before sending a notice, consider in good faith whether the use might be fair use. A takedown is a legal instrument, not a complaint form.
Function's Report button covers spam, harassment, nudity, dangerous behaviour, and fake listings. It has no copyright option, it collects no signature and no sworn statement, and it limits how many reports one account can file about the same target. None of that is compatible with what a copyright notice has to be.
Copyright notices must be sent in writing to the address in section 3. That channel does not require a Function account.
Function terminates, in appropriate circumstances, the accounts of users who repeatedly infringe copyright. This policy is part of Function's Terms of Service, which every account holder agrees to.
Function records the copyright notices it receives and what it did about each one, and uses that record when deciding whether an account has become a repeat infringer. That record is kept by hand, and termination for repeat infringement is a manual decision — there is no automatic strike counter and no threshold that trips on its own. Whether circumstances are appropriate depends on the case; Function does not commit to a fixed number of notices before terminating an account, and does not treat any number of them as a free allowance.
Function does not monitor what people upload looking for infringement, and is not required to. It responds to notices, and it acts on infringement it otherwise becomes aware of. Nothing on this page should be read as a claim that content posted on Function has been cleared or licensed.
By uploading a photo, a clip, or text to Function you are representing that you have the rights to it, or permission from whoever does. Cover images and flyers are where this goes wrong most often: an image found through a search engine or lifted from another platform is somebody's property, and the person who uploads it — not Function — is the one a rightsholder will pursue. See the Terms of Service for the licence you grant Function in what you post, and the Community Guidelines for what belongs here.
Music matters here too. A recorded track picked up in the background of an event clip involves two separate copyrights — the recording and the underlying song — and neither is automatically cleared by the clip being short.
Copyright notices, counter-notifications, and questions about this page: hello@function.cx