Service Providers and SDKs
This catalog identifies the principal providers and software development kits Likert uses, the data involved, and why the processing occurs. It supplements the Privacy Policy.
Provider catalog
| Service | Data and purpose | Role and retention | Privacy |
|---|---|---|---|
| Google and FirebaseFirebase Authentication, Firebase Analytics, Google Analytics | Data: Account identifiers, authentication events, consented analytics events, device/app information, and diagnostics Purpose: Authentication, account security, product analytics, and performance measurement | Role: Service provider or processor; independent controller where Google’s terms say so Retention: Likert applies its published schedule; Google-controlled retention follows configured settings and Google’s terms | Privacy information |
| Google AdMob and User Messaging PlatformAdMob, Google Mobile Ads, UMP | Data: Advertising identifiers when permitted, consent choices, device information, broad non-sensitive targeting signals, and ad delivery or interaction events Purpose: Advertising consent, sponsored-placement delivery, frequency control, fraud prevention, and measurement | Role: Advertising and measurement provider; legal role depends on the processing and applicable law Retention: Likert raw ad events: 45 days; Google-controlled data follows Google’s terms and configured controls | Privacy information |
| AppleSign in with Apple, App Store, StoreKit | Data: Sign-in identifiers, relay email where selected, transaction identifiers, subscription and entitlement status Purpose: Authentication, purchases, subscription management, restoration, and fraud prevention | Role: Independent platform provider and, for limited service operations, service provider Retention: Likert transaction records: 7 years; Apple-controlled retention follows Apple’s terms | Privacy information |
| Google PlayGoogle Sign-In and Google Play Billing | Data: Sign-in identifiers, transaction identifiers, subscription and entitlement status Purpose: Authentication, purchases, subscription management, restoration, and fraud prevention | Role: Independent platform provider and, for limited service operations, service provider Retention: Likert transaction records: 7 years; Google-controlled retention follows Google’s terms | Privacy information |
| Amazon Web ServicesInfrastructure, object storage (S3), and Rekognition DetectModerationLabels | Data: Hosted service data, uploaded images submitted for moderation, moderation labels, model version, and limited response metadata Purpose: Hosting, storage, delivery, security, and detection of potentially prohibited image content | Role: Service provider or processor Retention: Images follow the media schedule; moderation labels and evidence follow the moderation schedule; AWS transient processing follows the service configuration and contract | Privacy information |
| ExpoExpo Push Notification Service | Data: Push token, platform, notification payload, and delivery response Purpose: Deliver account, match, message, safety, and service notifications requested or permitted by the user | Role: Service provider or processor Retention: Push tokens remain while registered or until invalidated; delivery records follow operational-log retention | Privacy information |
| OpenAIResponses API (GPT-6 Luna) for staff moderation and support assistance, when enabled | Data: Selected report evidence, relevant private-message excerpts, profile text, support-ticket messages, staff notes, appeals, and up to three eligible images only when image assistance is separately enabled Purpose: Generate advisory summaries and suggested next steps for authorized staff; staff make final decisions | Role: Service provider or processor, subject to agreement and role review before activation Retention: Likert snapshots follow case or ticket retention. OpenAI API abuse monitoring follows the applicable project controls and terms; an image flagged as potential child sexual abuse material may be retained for manual safety review even with enhanced retention controls. Likert cannot promise immediate deletion of provider-held safety records. | Privacy information |
| Operational service providersHosting/CDN, database, telemetry, transactional email, support, and moderation tools selected by Likert | Data: Only the account, content, request, diagnostic, support, or security data needed for the contracted function Purpose: Operate, secure, monitor, support, and maintain Likert | Role: Service provider or processor under contract Retention: The shortest period required for the service and Likert’s published schedule; exact providers and controls are maintained in Likert’s internal vendor inventory | Privacy information |
Changes and questions
Providers may change as Likert’s services change. We aim to keep this catalog current as providers and processing purposes change. Email privacy@likert.dating with privacy questions.