Trust and safety
Policies and safety
The rules for using UFIConnect, how connected services work, and how to report a concern or manage your data.
Updated October 5, 2026 · UFIConnect, California, United States
Community guidelines
UFIConnect brings together public source content, member communities, professional connections and recruiting tools. Be accurate about your identity, respect others, and share only content you have permission to use.
- No threats, targeted harassment, hate directed at protected groups, scams, impersonation, or disclosure of another person’s private information.
- No child sexual abuse or exploitation, grooming, sextortion, or sexualized depictions of minors, including synthetic material.
- No non-consensual intimate imagery, sexual deepfakes, or tools and instructions intended to create or distribute them. This applies to uploaded content and AI features.
- Respect copyright, source attribution, consent and source safety labels. Do not evade a block, removal or account restriction.
- Recruiters must describe real opportunities accurately, respect applicants’ privacy, and follow applicable employment and discrimination rules.
Violations may lead to content removal, feature restrictions or account suspension. Serious harm can lead to termination without a warning.
Acceptable use
Use the service for lawful communication, discovery and work. Do not steal credentials, distribute malware, bypass access controls, overload systems, send spam, or collect personal information for surveillance or exploitation.
AI tools must not be used for abuse, non-consensual sexual content, deceptive impersonation or infringing material. Review generated output before sharing it. UFIConnect does not use Google APIs to create non-consensual intimate imagery.
A connected account, subscription or public source link does not grant permission to scrape a source, download restricted media, remove branding, resell data or circumvent that source’s restrictions.
Reports and appeals
Open the post, comment or profile menu and choose Report. Select the closest reason and describe the problem. For copyright requests, use the copyright process. If a report control is unavailable, email support@uficonnect.org with the UFIConnect link and original source link.
Submitted in-app reports are stored for operator review with the target, reason, details and status. Filing a report does not automatically remove content. Review may result in action, a request for more information, or no action. Source platforms control removal from their own services.
To appeal a restriction or follow up, contact support with the affected account, content link and the reason you believe the decision should change. Do not include passwords, access tokens or copies of illegal sexual material. For immediate danger, contact local emergency services.
Connected services, trademarks and attribution
UFIConnect is an independent service. Source names and logos identify where content comes from; they do not imply endorsement, partnership or ownership. Content belongs to its author or other rights holder. Open the source link for the original context, current engagement counts and any source-specific restrictions.
Connections are optional and depend on each provider’s availability and approval. Each provider has its own permissions, publishing capabilities, rate limits and content rules. A displayed like count is a source or UFIConnect count, as labelled; viewing it does not perform a like on that platform.
Read the permissions on the provider’s authorization screen. Disconnect in Connected Accounts or revoke access through the provider. Disconnecting stops future authorized access; it does not undo content you already published there. Details of storage and deletion are in the Privacy Policy.
YouTube features use YouTube API Services and the official embedded player. The YouTube Terms of Service and Google Privacy Policy apply. Google user data is used for the authorized visible features, subject to the Google API Services User Data Policy, including applicable Limited Use requirements. It is not used for advertising or training general-purpose AI models.
Developer and API access
The endpoints used by UFIConnect’s clients are part of the service. Their existence does not grant unrestricted third-party API access or a data redistribution licence. Contact support@uficonnect.org before building an integration.
Authorized integrations must use their own credentials, request only needed permissions, respect rate limits and revocation, protect user data, and preserve source attribution. Never bypass authentication, reuse another person’s tokens, probe other accounts, or present yourself as UFIConnect or a source platform.
Law-enforcement and other legal requests
Send legal or preservation requests to privacy@uficonnect.org. Identify the requesting authority, jurisdiction, legal basis, relevant account identifiers, requested records and date range, and provide official contact details and process documents.
Requests are subject to identity, authority and scope review. Disclosure requires an applicable legal basis; submitting a request does not provide direct access to accounts. Preservation requests concern records still held by UFIConnect and cannot recover deleted records or decrypt a local Vault without its passphrase. Applicable law may limit notice to an affected user.
This mailbox is not an emergency dispatch service. Contact emergency services for immediate threats to life or safety.
Data retention and deletion
Retention depends on the feature and storage location. The following describes the implemented lifecycle. Cleanup can be delayed during an outage; a cache refresh interval is not a promise that every stored copy has been deleted.
| Data | Lifecycle and controls |
|---|---|
| Account and member content | Kept to operate your account. Successful account deletion removes your account, authored posts and comments, account-linked messages and associated records from active application storage. Shared communities and other members’ content remain. |
| Connected credentials | Removed from the active connection when disconnected or when the account is deleted. Revoke the provider’s grant separately if needed. |
| Source snapshots and actions | Creator metrics snapshots expire from storage after one day; source action request and audit records after 30 days. Snapshots stop displaying after 15 minutes until refreshed. These records are pruned when cleanup runs. |
| Copyright concerns | Creator analytics concerns are pruned after 90 days. In-app safety reports and correspondence are separate records used to review concerns and resolve disputes; they do not share that automatic expiry. |
| Public feed cache | Live feed age limits are generally 8 or 20 days depending on source volume and type. Archived items have a configurable age limit, 30 days by default, and count limits. Source restrictions and removals can require earlier deletion. |
| Service counts | Aggregate daily page and performance counts cover 30 UTC calendar days. In-memory request and response-time counters reset when the process restarts. |
| Local Vault and downloads | Encrypted browser Vault data remains on that browser until you delete it or clear its storage. Account deletion does not remotely erase browser copies or exported files. Use Vault’s deletion controls and delete backups you no longer need. |
| Billing, hosting logs and backups | Payment providers and hosting services maintain separate records under their own retention settings and applicable obligations. Account deletion does not erase those records immediately. Contact privacy support for a request involving these copies. |
Use Settings → Account to export or delete account data, and Connected Accounts to disconnect a provider. Account deletion first stops recurring memberships; if this cannot finish, the app reports a failure so you can retry. Contact privacy@uficonnect.org for access, correction, deletion or retention questions. Required legal or dispute records may need separate review.
Security and incident reporting
Report suspected security issues privately to privacy@uficonnect.org. Include the affected page, time, impact and safe steps to reproduce with a test account. Do not send secrets, exploit another user’s account, or publish personal data.
For suspected account compromise, change your password and revoke sessions in Security settings. Disconnect affected external accounts and revoke access with those providers. Incident handling includes assessing the report, containing confirmed exposure, reviewing affected systems and providing notices when applicable law requires them. This does not guarantee a particular response time or that an incident can be fully reversed.
The local Vault encrypts private entries in your browser. Keep your passphrase and backups safe; support cannot recover a forgotten passphrase. Hardware device protection is described separately on the Vault device page.
Children and age requirements
UFIConnect is intended for people aged 13 and over, or 16 and over in the EU, EEA and UK, and any higher minimum required where they live. It is not directed to younger children. Do not misrepresent your age or use another person’s identity to register.
Report an underage account or a concern involving a child to support@uficonnect.org. See the Child Safety Standards for prohibited conduct and reporting options.
Advertising, sponsored content and tracking
Clearly identify paid endorsements, sponsorships and affiliate relationships in content you post. Do not disguise an advertisement as an independent recommendation or imply that UFIConnect or a source platform endorses a sponsor.
Optional Google Analytics measures general page categories after analytics consent. A separate Google Ads choice allows measurement of visits and ad click attribution on the public homepage for signed-out visitors. Accepting one does not accept the other. Google receives connection and device information and, for Ads, permitted ad click identifiers and attribution cookies. Ad personalization is disabled.
Manage analytics and advertising choices. Declining or withdrawing consent stops future collection by that optional integration. Global Privacy Control keeps both optional integrations off. Core service counts and security controls continue. The Privacy Policy describes cookies, local storage and providers.