1. Controller
ENJORE Srl is the controller for SportSocial.ai account management, contractual administration, service security and the processing described in this notice. Contact details are shown on this page.
2. Data we process
We may process identity/contact information; credentials and account-security data; workspace, plan and subscription information; access and diagnostic logs; locale/settings; Media Library assets; information submitted to generate graphics and Reels; support requests; usage metadata; and billing/payment-related information. When voice input is used, audio is sent for transcription and the SportSocial.ai application does not retain it as a file after transcription; technical and usage metadata may be retained.
3. Purposes and legal bases
Contract / pre-contractual steps: registration, email verification, authentication, service delivery, content generation, subscription management and support. Legal obligations: tax/accounting and authority requests. Legitimate interests: security, fraud/abuse prevention, diagnostics, service continuity and protection of ENJORE’s rights, balanced against user rights. Consent: only for optional non-technical cookies/tracking or other purposes where consent is required; consent may be withdrawn at any time.
4. Personal data in Customer Content
Where customers upload personal data about athletes, players, staff or others, the customer will normally be the controller and is responsible for a lawful basis. ENJORE processes those data on the customer’s behalf only as required to provide the service and according to the applicable processor role.
5. Recipients and providers
Authorised personnel and service providers may process data where necessary, including cloud hosting, payments, transactional email and AI providers when relevant features are used. The current architecture uses Google Cloud, Stripe for payments and tax calculation where enabled, the European Commission VIES service for EU VAT-number validation where requested, Twilio SendGrid and, for enabled AI functionality, OpenAI. IMG.LY Background Removal and Remotion currently run as components on our rendering infrastructure; local execution does not by itself send assets to an IMG.LY/Remotion cloud service.
6. International transfers
Some providers may process information outside the EEA. Where applicable, transfers are handled using adequacy decisions, Standard Contractual Clauses or other GDPR mechanisms according to the provider and actual configuration.
7. Retention
Account and service data are retained for the relationship and afterwards as needed for legal/accounting obligations, security and disputes. Administrative records are retained for statutory periods. User sessions normally last up to 14 days and admin sessions 12 hours. Verification, reset and login-PIN tokens have short configured expiries. Media/output remain until deleted or service termination, subject to operational backup cycles.
8. Required information
Information marked as required is necessary to enter into or perform the service contract. Failure to provide it may prevent use of the relevant features. Optional consent is not a condition for unrelated functionality.
9. Automated decisions
AI and automation features assist with content creation and structuring, but the configuration described here is not used to make solely automated decisions producing legal or similarly significant effects on the user under Article 22 GDPR.
10. Your rights
Where applicable, data subjects may request access, rectification, erasure, restriction, objection and portability, and withdraw consent without affecting prior lawful processing. Requests can be sent to the privacy contact below. Data subjects may also lodge a complaint with the Italian Data Protection Authority or another competent supervisory authority.
11. Security
We apply technical and organisational measures proportionate to risk, including tenant separation, authentication, access controls and infrastructure protections.
12. Updates
This notice may be updated when the service, providers or law change. The current version and update date are published here.