Sign in

Part of the legal pack — see also: Terms of Service · Privacy Policy · Data Processing Addendum · Refund Policy. A plain-English summary of how Profusia handles personal data is at /privacy.

Profusia AI — Acceptable Use Policy

Effective date: 12 November 2026

The short version. This box is a plain-English summary for convenience. It is not part of this AUP, and where it differs from the numbered sections below, the sections govern.

Profusia hosts documents that businesses share with their clients. Do not use it to host or send anything that is illegal, harmful, deceptive or somebody else's, and do not put health records, card numbers or other regulated data into it.

Do not attack it, overload it, or get around its limits, trials or seats. Security research that follows Section 4.3 is welcome.

A link is a key. Whoever holds a link can open what it opens, so share with that in mind.

If something breaks these rules, we usually take down the one document first, tell you why, and look again if you ask. Child sexual abuse material is reported to NCMEC and its Workspace is suspended at once.

Report a problem to legal@profusia.ai — send the address, never the material. Security problems go to security@profusia.ai.

This Acceptable Use Policy (the "AUP") is part of the Agreement under the Profusia AI Terms of Service (the "Terms") between the Customer and Evadaroo & Company, LLC, a Pennsylvania limited liability company trading as Profusia AI ("Profusia", "we", "us"). Capitalized words this AUP does not define — such as Agreement, Customer, Customer Content, Recipient, Service, User and Workspace — mean what the Terms say they mean.

Who it applies to. This AUP applies to you, to everyone you invite into your Workspace, and to everything an assistant connected to your Workspace does. It also applies directly to anyone else who uses the Service — a person opening a link, visiting a portal, or reading our public pages — whether or not they have accepted the Terms. An owner accepts this AUP as part of the Terms, and every other User accepts it when they join a Workspace; each confirms that they are 18 or older, and we keep a record of each acceptance. You are responsible for the conduct of the people you or your Users give access to — your Users, and the Recipients you or they share with — and for what they do with that access, except to the extent that the access resulted from our breach of the Terms or from a Security Incident. In Sections 1 to 7, "you" means anyone this AUP applies to; in Sections 9 and 9A it means the person writing to us — the person reporting, the person shown in an image, or the person sending a copyright notice or counter-notice; everywhere else it means the Customer.

How it fits with the other documents. If this AUP and another part of the Agreement disagree, Section 16.2 of the Terms decides which one governs. Section 8 of this AUP is the enforcement procedure that Sections 8, 11.3 and 11.4 of the Terms refer to, and where it differs from those Sections, Section 8 of this AUP prevails (Section 16.2 of the Terms).

1. Do not break the law or harm people

You may not use the Service to store, publish, share or send content, or to do anything, that:

  • violates any applicable law or regulation, or helps someone else do so;
  • infringes a copyright, trademark, patent, trade secret, right of publicity or any other right;
  • sexually exploits or endangers a minor, or contains or links to child sexual abuse material. We report apparent child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC), as US law requires; we preserve the material and the records connected with it for as long as the law requires, including by holding the Workspace so that a deletion already under way does not run (Section 8.10); we cooperate with law enforcement; and we suspend the Workspace involved — which shuts out every User in it — and may terminate the Terms, without notice or a cure period. We never provide an export, copy or restoration of that material;
  • is non-consensual intimate imagery, including imagery made or altered with AI (Section 9.3 says how the person shown can have it removed);
  • threatens, harasses, stalks or defames a person, or incites violence or hatred against a person or group;
  • publishes another person's private information — such as a home address, an identity document, or financial or health details — to harass, expose or endanger them;
  • promotes terrorism or violent extremism;
  • promotes or facilitates prostitution or sex trafficking;
  • facilitates any other human trafficking, illegal weapons or drug sales, or the exploitation of vulnerable people;
  • violates US export-control or sanctions law, or knowingly gives access to anyone in an embargoed country or region or on a US restricted-party list.

We may block access to the Service from embargoed jurisdictions. We do not currently screen users or block access by location, so each Customer remains responsible for its own compliance (Section 16.7 of the Terms).

2. Do not deceive, and do not abuse our hosting

You may not use the Service for phishing, credential harvesting, fraud, pyramid or Ponzi schemes, fake invoices, counterfeit goods, impersonation of a person or organization you are not, or any page designed to make a reader believe it comes from someone else.

You may also not use the Service: as a general file locker, content-delivery network or download mirror for material unrelated to your business; as a link shortener, a redirector, or a landing page used to get traffic past a filter; for search-engine spam, doorway pages or link farms; or to host any page whose purpose is to collect passwords, payment details or other credentials.

Published pages are served from addresses that carry our name. Every Workspace is served from an address ending in profusia.ai, so one abusive page can get our domain flagged by browsers, email providers and blocklists for every customer at once. Content designed to abuse that trust is the specific harm this Section exists to stop, and any such risk is a reason for us to act first under Section 8.4.

What the product already does about it: published pages cannot submit forms or load content from other websites — though a page's own script can still send a reader, and what they type, to another website; and until a Workspace opened through self-serve sign-up is paid for, its pages run in an isolated sandbox under a notice telling readers that the Workspace is unverified, and it cannot publish ZIP archives, older Office files (.doc, .xls, .ppt) or pages whose markup contains a password field (Section 4.12 of the Terms). These safeguards do not catch every deceptive page, and they do not make deceptive content acceptable.

3. Do not put regulated or hazardous data in the Service

This Section is the one list of data that must not be put into the Service; the Terms and the DPA refer to it. The Service is not designed, certified or sold for, and you may not put into it:

  • protected health information subject to HIPAA — we will not sign a Business Associate Agreement;
  • payment card data subject to PCI DSS (card numbers, security codes, magnetic-stripe or chip data);
  • government-classified information, or technical data controlled under export-control law;
  • personal information collected from children under 13, or under the age of digital consent where you operate;
  • biometric identifiers, such as fingerprint, face or voice templates;
  • government identity numbers or financial account credentials in bulk — for example a list of Social Security or passport numbers, or of bank-account sign-ins;
  • special categories of personal data (health, racial or ethnic origin, religious or philosophical beliefs, political opinions, trade-union membership, sex life or sexual orientation, genetic or biometric data) and criminal-offence data, in bulk or as the main content of a document or table — for example medical records, a staff health register, or a list of criminal convictions;
  • data whose handling requires a certification we do not hold. We hold none ourselves (see profusia.ai/trust).

Incidental mentions. An incidental mention of special-category or criminal-offence data in ordinary business records — for example, a note that someone is on sick leave — is not a breach of the special-categories item above. It does not excuse any other item in this list. The Customer decides whether the security measures described in Annex II of the DPA are adequate for such content, and remains responsible for having a lawful basis for it.

Where data is held. We do not choose, and cannot guarantee, the country where your content is stored or processed: our storage locations were chosen by Cloudflare when they were set up and are not pinned to a region. Do not put in data that the law or a contract requires to stay in a particular country or region.

High-risk uses. You may not use the Service where its failure could lead to death, personal injury or severe environmental damage — including aircraft or vehicle control, life support, nuclear facilities or emergency dispatch.

4. Do not attack, overload or get around the Service

4.1 The Service itself. You may not:

  • try to reach another Workspace's data, another customer's account, or any system, credential or address you were not given;
  • probe, scan or test the security of the Service, except good-faith security research that follows Section 4.3;
  • circumvent or interfere with authentication, rate limits, usage allowances, spending caps, entitlements (the limits of a plan), or audit logging;
  • introduce malware, ransomware, cryptominers or destructive code — including inside a document you publish;
  • overload the Service with automated traffic, get around any rate limit or usage allowance (for example by spreading use across Workspaces or accounts), or use the Service as a denial-of-service origin. The Service runs on capacity that every customer shares, and we may slow or refuse traffic that threatens it. Reaching an allowance, or making requests the Service refuses because one has been reached, is not a breach: the Service stops creating more, as Section 4.5 of the Terms describes;
  • reverse engineer, decompile or try to derive source code from the Service, except where the law expressly allows it, and then only to that extent;
  • scrape or mirror the Service, or use it to build a competing product. This does not restrict exporting, copying or reading your own Customer Content through the export, the MCP tools or any other interface we document, or automating your own normal use within the limits we publish.

4.2 Accounts, trials and seats. You may not:

  • open more than one Workspace or account to get another trial, to multiply the Free plan's allowances, or to get around a limit of the Free plan or a trial, or around a suspension (paying for a further Workspace is not a breach); open a Workspace or account by automated means, with false details, or with someone else's details without their authority; or get around the restrictions placed on a trial or unverified Workspace (Section 4.12 of the Terms), such as its sandbox or its unverified notice;
  • let more than one person use one User's sign-in, or get around the seat count or a plan's member limit — for example by working around the check that refuses an invitation past the seats paid for. An assistant used by the person who connected it is not another person. If a Workspace has more people than paid seats for any other reason, Section 4.1A of the Terms says what happens, and keeping people after a move to a smaller plan is governed by Section 4.7 of the Terms; neither is a breach of this AUP;
  • resell or sublicense access to a Workspace itself without a written agreement with us. Inviting your own clients into your Workspace, or sharing pages, sites and portals with them, is ordinary use and not reselling.

4.3 Security research. We welcome good-faith security research that follows all of these rules: test only against a Workspace you own or have written permission to test; do not access, copy, change, delete, keep or share data that is not yours, and stop and tell us at once if you come across any; do not degrade the Service for anyone — no denial-of-service, load or spam testing, no social engineering of our customers or of us, and no physical testing; report what you find promptly to security@profusia.ai and give us a reasonable time to fix it (we suggest 90 days) before disclosing it; and do not ask for payment as a condition of telling us. Research that follows these rules is authorized by us, and we will not bring a legal claim against you for it. That authorization is ours alone: it cannot bind a third party — such as a customer whose data you reach — or a law-enforcement authority, and it does not authorize testing of the services we depend on (such as Cloudflare, Paddle, Resend and the AI providers), whose own policies apply. These rules are our vulnerability disclosure policy; if you are unsure whether something falls within them, ask security@profusia.ai first.

4.4 Scripts in pages you publish. An HTML page you publish can run its own scripts in the browser of everyone who opens it, and you are responsible for every script in a page you publish. On a signed-in member's screen such a page can act with that member's permissions, so publish only pages you trust.

5. Use the AI features responsibly

This Section applies to every AI feature of the Service, including the in-app AI features that read Workspace content (Section 6.1 of the Terms) and the help assistant.

5.1 Prohibited uses. You may not:

  • use the AI features to generate content prohibited by any other section of this AUP;
  • use them to generate content designed to deceive a reader about whether it was machine-generated, where doing so would be unlawful or misleading in context;
  • circumvent, extract or interfere with a model provider's safety systems, or try to extract model weights or system prompts;
  • automate bulk requests with the purpose of exhausting an allowance, degrading service for others, or reselling model access;
  • produce legal, medical, financial or safety-critical advice with the AI features and then present it to others as reviewed when it was not. AI output may be wrong; you are responsible for reviewing it before relying on it;
  • use the AI features, or anything they produce, as the sole or principal basis for a decision that has a legal or similarly significant effect on a person — about employment, credit, housing, insurance, education, healthcare, legal services or access to public services — without meaningful human review, or for any practice the EU AI Act prohibits.

5.2 Prompt injection. You may not put content into a document, page, comment, card or dataset that is designed to make an AI system that reads it — ours, a reader's own assistant, or another customer's — act against the interests of the person using it ("prompt injection"), for example hidden instructions to send data elsewhere, invite someone, or create a share link.

5.3 Model providers' own policies. In-app AI is answered by third-party model providers, named in our Privacy Policy, and their own usage policies also apply to what you ask. You may not use the AI features for anything the published usage policy of any of those providers prohibits. If a provider tells us that requests from your Workspace breach its policy, we may switch in-app AI off for your Workspace while we look into it, and we will tell you.

5.4 The help assistant. The help assistant — the question box on our help pages, the "Ask about Profusia" assistant, and the Uiia assistant on profusia.ai/help — answers from Profusia's own published help and reads no Workspace content. It is answered by third-party AI services, some of which may use what you type to improve their models. What you type into it is not Customer Content, so the rule that keeps Customer Content away from such services (Section 6.5 of the Terms) does not cover it: do not type personal, confidential or customer information into it.

6. Do not misuse email or sharing

  • Email the Service sends is for running the Service, never for promotion. The Service sends: mention and card-owner notifications to members of your Workspace, once an owner or admin turns email on for the Workspace and unless the member turns it off; an invitation to an address someone in your Workspace invites, with the exceptions below; password-reset links, and a notice when a password is changed through one; confirmations and notices when someone changes their sign-in email; confirmations to people who open a Workspace through sign-up; and notices to a Workspace's owners about the Workspace itself, such as a reminder before a yearly plan renews, a notice before a price rise or a feature taken off a plan reaches a paying plan, or a warning before an unused Workspace is erased. The Privacy Policy describes what each one contains. You may not use any of them to send unsolicited, bulk or commercial messages, to reach people who have not asked to hear from you and have no business reason to, or to deceive the person who receives them. Invite only people you have a business reason to invite. Text you choose that appears in our email — your Workspace's name, your display name, a comment or a card — must not advertise, solicit or impersonate anyone, and must not carry a link or instruction designed to mislead. Invitation email is limited per Workspace per day and across the Service; an invitation requested over MCP — by a connected assistant or with a Workspace access key — is never emailed by us, and is handed back for a person to send; and a Workspace opened through self-serve sign-up emails no invitations until it is paid for (Section 4.12 of the Terms). We may refuse, limit or stop sending any message, and where a Workspace misuses email we may suspend it under Section 8.4.
  • Do not mint share links, portals or embeds for content you do not have the right to distribute.
  • Every outward link the Service mints is a bearer link — a share link, a site link, an embed, a project link, a portal: whoever holds it can open what it opens, and a link forwarded is a link that works. A password on a share link stops someone who has the link but not the password; it does not help once both are passed on. A handling notice and a document's state label ("Draft", "Approved") restrict nothing — they tell the reader something. A space narrowed to a group hides the space, not the documents inside it. The data address behind a live page works for anyone who has it, unless it is a table built from a project, which answers only the page's own ticket or a signed-in member. A link does not expire unless you set an expiry, and a link posted somewhere public can be found and indexed by search engines. Choose what you share with that in mind; revoking a link, or rotating a table's address, is how you take access back.

7. Connected assistants and services

  • An assistant acts as whoever connected it. An assistant a person connects with their own sign-in acts as that person, with that person's role and only what they can see. An assistant connected with a Workspace access key acts for the whole Workspace and is not limited by roles. Either way, everything it does, including acts prompted by instructions it read in a document, comment, page or dataset, is the Customer's act under the Terms. What the Service returns to a connected assistant leaves Profusia and is held by that assistant's vendor under your own terms with it. Connect only assistants you control, check what you let them do without asking you first, and never share your sign-in or a Workspace access key with anyone outside your organization.
  • Disconnecting an assistant. Disconnect an assistant as soon as you no longer trust it. A person disconnects their own in Personal settings › Assistants. In People, an owner can disconnect anyone's, and an administrator a member's or a viewer's. An owner can disconnect every connected assistant in the Workspace at once, after entering their password, in Workspace settings › Sharing & governance › If something leaked; that is the only control in the product that disconnects an assistant approved by pasting a Workspace access key, because such a connection belongs to no person, and we can also do it for you. An owner can rotate the Workspace access key in the same place. That stops the key itself, and anything that sends the key directly, from working; it does not disconnect any assistant connected through an approval, whether the approval was given by signing in or by pasting the key, so disconnect those as well.
  • Google Drive sync. The optional Google Drive sync writes only into files Profusia creates, in a Google account you connected. Do not attempt to widen its scope or use it to move content you have no right to move.

8. Enforcement

8.1 What we may do. If we reasonably believe that content or conduct breaks this AUP, we may: take down a specific document; ask the Workspace owner to remove content, revoke a link or remove a User; switch off a specific feature for the Workspace where the Service gives us a way to (for example in-app AI); suspend the Workspace; rotate its access key or disconnect its connected assistants; terminate the Terms; or take any other step reasonably needed to stop the harm or to comply with the law. Whether something breaks this AUP is decided by us, in our reasonable judgment, and we may restrict access to material we consider in good faith to be harmful or otherwise objectionable, whether or not it is lawful. We generally prefer the narrowest step that stops the harm — usually taking down one document before suspending a Workspace — but we decide which step fits. If an owner we ask to act does not, we may take one of the other steps.

8.2 Content first, without waiting. Taking down one document, or switching off one feature, is not a suspension and does not wait for a cure period. We may do it as soon as we receive a notice that appears valid (such as a copyright notice or a court order), or reasonably believe the content is unlawful, deceptive or harmful, and we tell the Workspace owner when we do, as Section 8.5 describes.

8.3 Notice and cure before suspension or termination. For a paid Workspace, unless Section 8.4 allows us to act first, we will tell the owner by email what is wrong and give at least 5 business days to fix it before we suspend the Workspace or terminate the Terms. If it is fixed in that time, we will not suspend or terminate for it.

8.4 When we act first. We may suspend or terminate without prior notice or a cure period where we reasonably believe that: (a) there is a risk of harm to any person, to the Service, to other customers or to us — including child sexual abuse material, malware, phishing, an attack on the Service, or a threat to the standing of our domains with browsers, email providers or blocklists; (b) the law, a court or a regulator requires it; (c) the Workspace is on the Free plan or a trial, or has not been paid for; (d) the same or a similar violation has happened before, after we gave notice of it; or (e) the account or Workspace was opened with false information or to evade an earlier suspension. We will tell you why as soon as we can, unless the law forbids it or telling you would put a person at risk or compromise an investigation.

8.5 Telling you why, and looking again. When we take down content, switch off a feature, or suspend or terminate, we will tell the Workspace owner by email what we did, which content or conduct it concerns, which part of this AUP or which law it rests on, whether a report prompted it, and how to ask us to look again — subject only to the exceptions at the end of Section 8.4. Reply to that message, or write to legal@profusia.ai, within six months. A person will review the request and tell you the outcome. If you ask about a termination within the 30 days in Section 8.10, we do not erase the Workspace while your request is open; and if we got it wrong, we will put back what we still hold as soon as we can. This review is in addition to any remedy the law gives you. Every takedown, suspension and reinstatement we make is also recorded in your Workspace's own audit trail, with the reason we recorded (which, where the exceptions at the end of Section 8.4 apply, may say no more than which part of this AUP it rests on).

8.6 Taking down one document. Where a single document breaks this AUP, we can take that document down on its own, without suspending its Workspace. While it is down, every share link, embed, site page and portal stops serving it, and so does the in-browser reader; link previews of it and pictures inside it stop too. Anyone who opens it at one of those doors sees only a notice that Profusia has taken it down, without the reason. Its name stays listed wherever a site lists it, though no words from inside it are quoted there. It cannot be given a new version, a new share link or a new embed. Your Workspace keeps it: members see it listed with the reason we recorded (qualified as in Section 8.5) and the address to write to, they can still export it, and an assistant connected to the Workspace can still read it; the optional Google Drive sync also keeps copying it into the Google account the owner connected, and a live data table it reads keeps working. Taking it down deletes nothing — though members who can delete documents can still delete it, as they can any other — and lifting the takedown restores it exactly as it was. For material that is unlawful to hold or pass on, we may suspend the Workspace instead. To report a document, see Section 9.

8.7 What a suspension does. A suspended Workspace is closed to everyone, its own members included: nobody can use it, and no connected assistant, share link, portal, page or export works, until we lift the suspension. An owner who signs in, or a member who was already signed in, reaches only a notice that the Workspace is suspended, when it was suspended, and the reason we recorded (qualified as in Section 8.5); any other member who tries to sign in is told only that it has been suspended by Profusia and to contact us; anyone else sees only that the Workspace is not available. While a Workspace is suspended, the optional Google Drive sync, which copies documents into the Google account an owner connected, is paused too, until we lift the suspension. Suspending a Workspace deletes nothing in it, and a suspended Workspace is held rather than erased (Section 8.10), except that once the Terms are terminated it is erased as Section 8.10 describes, whether or not it is still suspended (only a hold under Section 8.9 delays that). Only we can lift a suspension, and lifting it puts everything back as it was. We tell the owner by email, as Section 8.5 describes.

8.8 No monitoring obligation, and how we investigate. We do not review Customer Content as a matter of course, and nothing in this AUP obliges us to monitor it or to act on any report. We do not automatically scan content for malware or illegal material; we act on reports — from anyone, including a browser, email provider or blocklist that flags a page — and on what we otherwise learn. When we investigate a report, we may open the reported content and look at the records connected with it — who published it and when, which links, sites, embeds and portals serve it, and the Workspace's audit trail — as far as the investigation needs. Acting on one report does not oblige us to act on any other, and not acting is not approval.

8.9 Preservation and disclosure. Where the law requires, or for an investigation, legal process or a legal claim, we may preserve content and the records connected with it — including beyond the retention and erasure periods in the Terms and the Privacy Policy, and after a deletion request — by holding the Workspace as Section 8.10 describes, or by keeping a copy of the records. We disclose them only as Section 16.13 of the Terms allows — for example a report the law requires to NCMEC, or what a court order compels — and we tell the Workspace owner as that Section describes.

8.10 Your content after a suspension or termination. A suspended Workspace is held, not erased, except after termination, as the end of this paragraph says. Suspending it deletes nothing, and while it is suspended — or while we must preserve it for an investigation or legal process under Section 8.9 — none of our erasures runs on it: not a deletion an owner asked for (Section 11.5(b) of the Terms), whether before or after the suspension or hold began; not the erasure of an unused Workspace under Section 4.13 of the Terms; and not the erasure of items emptied from its trash, which also cannot be erased at once. Nor can any person be erased from it. A hold for an investigation or legal process does not stop what the Workspace's own Users delete themselves while it stays open to them (Section 16.13 of the Terms); where that matters, we may keep a copy (Section 8.9). When the suspension or hold ends, normal retention resumes, with each of those erasures' waiting periods counted again from that day (Section 16.13 of the Terms). The one exception is termination: once the Terms are terminated, the Workspace is erased as the next paragraph describes, whether or not it is still suspended, and only a hold under Section 8.9 delays that; once such a hold ends, the erasure waits 30 days more. Records that expire by age under the Privacy Policy go on expiring meanwhile; where we need to preserve any of them under Section 8.9, we keep them, or a copy of them, before they expire.

While a Workspace is suspended, an owner may ask us at legal@profusia.ai for one export of the kind Section 11.5(d) of the Terms describes, and we will provide it unless that would be unlawful or would defeat the purpose of the suspension. If the Terms are terminated for a violation, an owner may ask us at support@profusia.ai or legal@profusia.ai, within 30 days after termination, for such an export. We provide it by a secure method we choose, or by restoring the Workspace for a short time so that an owner can use the product's own export (its links and pages work again for that time); because the product's own export includes documents we have taken down, we restore a Workspace for this only where it holds none of the material described in the next sentence. We will not provide material that is unlawful to hold or return (such as child sexual abuse material), material we have taken down on a valid legal notice, or anything a court or authority directs us to withhold. After that window, we will erase the Workspace as Section 11.5(c) of the Terms describes, whether or not it is still suspended, unless we preserve it under Section 8.9 or a request to look again under Section 8.5 is still open; until it is erased, it stays closed to everyone, as Section 8.7 describes.

8.11 Refunds. We do not refund fees for a period in which a Workspace was suspended, or for a term cut short by termination, because of a violation of this AUP, including under the 30-day money-back in the Refund Policy. This does not affect a refund that Paddle, as Merchant of Record, gives under its own buyer terms, or any right the law gives you that cannot be waived. It also does not apply where the violation was caused by someone who used your account or credentials without your authority, or by a single User or Recipient whose access you removed promptly once you knew. In those two cases a suspension is treated as one that is not because of you (Refund Policy, Section 6), and if we terminate, we refund the fees prepaid for the unused term.

8.12 No charge for a suspended period. If a Workspace we suspended under this AUP is still suspended on a renewal date, we will pause or cancel that renewal with Paddle so that you are not charged for a period you cannot use, unless an amount is also unpaid. That is a step a person at Profusia takes by hand, so a renewal can be charged before we take it; if a renewal is charged while the Workspace is still suspended under this AUP, we refund it, unless an amount was also unpaid (Refund Policy, Section 10). If we lift a suspension because it was a mistake, we will extend your paid period by the time you lost, or credit its value against your next bill or bills, or refund it where the Refund Policy says so.

8.13 Good-faith enforcement. Apart from what Sections 8.5, 8.10, 8.11 and 8.12 say we will do, we are not liable to you or to anyone else for action we take, or decline to take, in good faith under this AUP.

8.14 Disputes about enforcement. A dispute between the Customer and us about how we enforced this AUP is resolved under Section 15 of the Terms.

9. Reporting a violation

9.1 How to report. Write to legal@profusia.ai. There is no report button on shared pages, so email is the way to reach us. So that we can act quickly, include: the exact address on Profusia where you saw the problem (the share link, site page, embed or portal URL); what is wrong — and, if you say it is illegal, which law and why; your name and email address (you may report child sexual abuse material without giving them); and a statement that you believe in good faith that your report is accurate and complete. Where you have given us a way to reach you, we will confirm that we received your report and tell you what we decided, unless the law forbids it or telling you would put a person at risk or compromise an investigation.

9.2 Never send us the material itself. Send only its address — above all for anything you believe shows a child. You can also report child sexual abuse material directly to NCMEC, at report.cybertip.org or 1-800-843-5678.

9.3 Intimate images shared without consent. If you are the person shown in an intimate image or video published through Profusia without your consent — including one made or altered with AI — or you are authorized to act for that person, write to legal@profusia.ai with the subject "Removal request". Include: your physical or electronic signature; the address on Profusia where the image appears (the link, page or embed); a short statement that you believe in good faith it was published without consent, with any information that helps us confirm it; and how to contact you. Within 48 hours of receiving a valid request, we will take it down so that no link, page, embed or portal serves it (Section 8.6), and tell you when that is done. A takedown leaves the document in its Workspace, and its name still listed wherever a site lists it, so we will also ask the Workspace's owner to delete it — or, where you tell us that its name identifies you, to rename or delete it — and we may suspend the Workspace if that is not done promptly, or instead of asking. Where the law requires it, we will also make reasonable efforts, within the same time, to find and remove identical copies of it on the Service that we know of. We have no tool that searches the Service for copies of a file, so this means the copies you point us to and any we find among the records connected with the one you reported (Section 8.8): tell us every address where you have seen it.

9.4 Security and copyright. Security vulnerabilities go to security@profusia.ai (also named in /.well-known/security.txt), under the rules in Section 4.3. Copyright complaints follow Section 9A.

9.5 What happens to what you send. Reports reach our company mailbox, which is hosted by Google Workspace. We use a report to investigate and act on it. When we act, we tell the affected Workspace's owner that a report prompted it (Section 8.5), but we do not give them your name or contact details unless you agree, the law requires it, or your report is a copyright notice or counter-notice (Section 9A).

We respond to notices of claimed copyright infringement under the US Digital Millennium Copyright Act, 17 U.S.C. § 512. Our copyright agent is:

  • Copyright Agent, Evadaroo & Company, LLC
  • Address: 502 W 7th St, Ste 100, Erie, PA 16502, USA
  • Telephone: provided when our agent is registered with the US Copyright Office
  • Email: legal@profusia.ai, with the subject line "DMCA notice"

We have not yet registered this agent with the US Copyright Office, and until we do we do not claim the safe harbor in 17 U.S.C. § 512(c). We act on notices sent to this address as this Section describes regardless.

What a notice must include: (1) a physical or electronic signature of the copyright owner or of a person authorized to act for them; (2) identification of the copyrighted work claimed to be infringed, or a representative list if several works are involved; (3) identification of the material claimed to be infringing and its exact address on Profusia — the share link, site page, embed or portal URL — with enough detail for us to find it; (4) your name, postal address, telephone number and email address; (5) a statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent, or the law; and (6) a statement that the information in the notice is accurate and, under penalty of perjury, that you are authorized to act on behalf of the owner.

What we do with it. When a notice substantially meets these requirements, we act expeditiously to remove or disable access to the material, usually by taking the document down under Section 8.6, which stops every link, embed, site page and portal from serving it. Where that alone would leave the material being copied out of the Service — for example by the Workspace's Google Drive sync — we may take a further step under Section 8, up to suspending the Workspace. We send the Workspace owner a copy of the notice. That copy may include the sender's name and contact details; we may remove them where we think that is appropriate.

Counter-notice. If material you published was taken down and you believe that was because of a mistake or misidentification, you may send our agent a counter-notice that includes: (1) your physical or electronic signature; (2) identification of the material and the address where it appeared before it was taken down; (3) a statement under penalty of perjury that you have a good-faith belief the material was removed or disabled as a result of mistake or misidentification; and (4) your name, address and telephone number, and a statement that you consent to the jurisdiction of the federal district court for the judicial district in which your address is located (or, if your address is outside the United States, any judicial district in which we may be found), and that you will accept service of process from the person who sent the notice or their agent. We will send a copy of the counter-notice — including your name and contact details, as the law requires — to the person who sent the notice, and we will restore the material no less than 10 and no more than 14 business days after we receive the counter-notice, unless our agent first receives notice that the sender has filed an action seeking a court order to restrain the activity, or the material breaks this AUP or the law for another reason.

Misrepresentation. Under 17 U.S.C. § 512(f), anyone who knowingly and materially misrepresents that material is infringing, or that it was removed by mistake, may be liable for damages. If you are not sure whether something infringes, take advice before sending a notice.

Repeat infringers. We keep a record of each valid notice, and of the Workspace and, where we can tell, the User it concerned. In appropriate circumstances we end the access of repeat infringers — by suspending their Workspace or terminating the Terms for it, or by requiring the Workspace owner to remove the User — and we may do so after a single notice where the infringement is clear and deliberate.

Other rights. We may also act under Section 8 on a complaint that does not meet these requirements, or that concerns a trademark or another right.

10. Changes

We may update this AUP. We post each version here with its effective date and keep every earlier version, which we will send on request. For a material change we will email each Workspace owner at least 30 days before it takes effect. A change required by law, or needed to address a security risk, a new kind of abuse or another active harm, may take effect sooner, with notice as soon as practicable. A change that is not material takes effect when posted. Section 16.3 of the Terms applies, including the right to cancel before a material change takes effect and receive a refund of the fees prepaid for the unused term.

Evadaroo & Company, LLC, a Pennsylvania limited liability company trading as Profusia AI · 502 W 7th St, Ste 100, Erie, PA 16502 · USA · legal@profusia.ai

Back to profusia.ai Security & trust Privacy summary