This Privacy Policy describes how Troott Technologies ("Troott", "we", "us") processes personal data when you use Troott Studio as a minister or creator at app.troott.com.

Troott is the data controller for minister account data described here. Contact: hello@troott.com.

This policy applies to personal data we process when you register for Studio, complete verification, upload sermons, manage your ministry profile, invite team members, or use analytics and billing features.

It does not apply to listener app users — see Listener Privacy Policy. Listener personal data you see in aggregated analytics is described below; you do not receive raw listener PII through Studio dashboards.

Account: name, email, phone, profile media, login history, and role assignments.

Ministry profile: ministerial name, ministry name, logo, type, headquarters address, contact details, website, social links, and languages.

Content: uploaded audio, thumbnails, titles, descriptions, tags, series metadata, and publishing status.

Analytics: aggregated and per-sermon listener metrics made available to you in Studio dashboards.

Team: invite records, email addresses of collaborators, and permission assignments.

Billing: subscription status and payment metadata processed by Paystack.

To verify ministers, we collect government-issued identification images (such as national ID, driver's licence, or passport) and related verification metadata. As stated in Studio: "Your ID will be used to verify your personal information."

These documents are used solely to confirm identity and ministry eligibility, accessed by authorised administrators, and stored securely on AWS infrastructure. Verification records may be retained for fraud prevention, legal compliance, and dispute resolution even after account deactivation where required by law.

Uploaded sermons are processed for transcoding (including HLS delivery), storage, and streaming to listeners. We generate playback analytics (listen counts, session metadata) to provide Studio insights.

Shareable links may use time-limited tokens as configured in Studio. Published sermon media may remain available to listeners according to platform retention policies.

Studio dashboards show aggregated listener engagement with your content. You see metrics such as play counts and trends — not individual listener library contents, private playlists, or contact details unless a separate product feature explicitly provides them with appropriate consent.

We also use product analytics (PostHog, Sentry, Reo in production) to improve Studio; those tools may receive your user id and email for error diagnosis.

We use minister personal data to:

• Provide Studio features including upload, publish, analytics, team management, and billing.
• Verify identity and prevent impersonation or fraud.
• Deliver and improve sermon processing and listener distribution.
• Communicate about your account, verification, security, and service updates.
• Enforce our Terms of Use and comply with legal obligations.

Where UK or EEA law applies, we rely on contract (providing Studio), legitimate interests (security, fraud prevention, product improvement), consent (where required for marketing), and legal obligation.

Processing of government ID may involve special-category data; we rely on and restrict access to authorised personnel.

See Minister GDPR information.

We use subprocessors including:

• AWS — storage, CDN, and ID document storage.
• MongoDB / Redis — application data and caching.
• Paystack — payments and subscriptions.
• Email providers — MailerSend, Zeptomail, SMTP for transactional email.
• PostHog, Sentry, Reo — analytics and error monitoring in production Studio.

We do not sell minister personal data.

Published sermons: may remain available to listeners even if you deactivate your account, subject to takedown requests, platform policy, and legal requirements. Ministers may not move published sermons to bin without administrator involvement.

Verification documents: retained as needed for fraud prevention and compliance.

Account data: retained while active and for a reasonable period after deactivation.

We use access controls, encryption in transit, and role-based permissions (RBAC) to limit who can view verification documents and minister account data. Only authorised administrators access ID verification files.

No system is completely secure; we cannot guarantee absolute protection.

Minister data may be processed outside your country, including in the United States via AWS and US-based observability vendors. Where required, we use appropriate safeguards such as standard contractual clauses.

You have rights of access, rectification, erasure, restriction, objection, and portability subject to applicable law and limitations when retention is required for published content, legal claims, or verification records.

Email hello@troott.com or see GDPR information.

When you invite collaborators, we process their email addresses and role assignments. You are responsible for informing team members about how Troott processes data and for managing permissions appropriately.

We may update this Privacy Policy. Material changes will be communicated via Studio, email, or this page with an updated "Last updated" date.

Privacy questions: hello@troott.com.

Troott Technologies — troott.com · Studio: app.troott.com