SkaDate Platform Capabilities

Last reviewed: August 21, 2026 · Format: selectable, searchable, text-first product reference

How to use this document

This document is intentionally written as a detailed reference rather than a marketing presentation. The text is selectable, searchable, and structured so that it can be attached to ChatGPT or another language model when evaluating SkaDate, drafting requirements, preparing a product specification, comparing implementation options, or planning a custom dating product.

The document has two main parts:

1. User application capabilities: what members can see and do in the web, PWA, and mobile experiences.
2. Administration console capabilities: what administrators and moderators can configure, manage, analyze, and moderate.

Back to contents

Part I. User Application Capabilities

Product overview

SkaDate is a ready-to-customize technology foundation for launching a branded dating application, dating website, or interest-based social community. The platform can be adapted to a specific audience, geography, brand, matching concept, or business model.

A member can typically:

• create an account and complete a profile;
• upload and manage profile photographs;
• discover people using cards, lists, search filters, or compatibility rules;
• like profiles, create mutual matches, and start conversations;
• review received likes, sent likes, profile visitors, favorites, and compatible users;
• participate in a social feed, groups, events, and forums through the Community Hub Ultimate plugin;
• complete selfie, identity, or age verification when enabled;
• manage privacy preferences and notifications;
• purchase Premium Membership or individual paid actions;
• use a web application, install a PWA, or access native iOS and Android applications.

SkaDate is not limited to the conventional profile -> swipe -> message flow. A project can make community content, shared interests, events, groups, compatibility, or another custom interaction model the primary reason for members to return.

The exact visual design, navigation labels, profile fields, usage limits, premium benefits, and enabled functions are controlled by the project configuration and installed plugins.

Primary navigation

A mobile configuration can include five primary areas:

1. Messages: private conversations and conversation management.
2. Community Hub: feed, groups, events, forums, and community chats through the Community Hub Ultimate plugin.
3. Discover: member search, profile browsing, and card-based discovery.
4. My Interests: likes, matches, visitors, and related activity lists through the My Interests Premium plugin.
5. Profile: the member’s own profile, photographs, settings, verification, and account controls.

The operator can change the available sections, their names, and their order. A product can prioritize the Community Hub, events, compatibility, or structured search instead of making swipe cards the main entry point.

First launch, registration, and sign-in

Welcome screen

The first screen can present the project brand, value proposition, visual identity, and two primary actions:

• create a new account;
• sign in to an existing account.

The welcome screen can also provide links to the Terms of Use, Privacy Policy, and Cookies Policy.

Registration by phone number

A phone-based registration flow can work as follows:

1. The member selects a country and dialing code.
2. The member enters a phone number.
3. The application sends an SMS verification code.
4. The member enters the code.
5. The member completes the required profile fields.
6. The member uploads a profile photograph if required.

The application can detect that a number is already in use, allow a code to be resent, and direct the existing account holder to the sign-in flow.

Other sign-in methods

Depending on the configuration, the product can support:

• Google Sign-In;
• Sign in with Apple;
• email and password.

Password recovery

The member can request a verification code by email and set a new password after the code is confirmed.

Configurable onboarding rules

The operator can determine:

• whether phone or email verification is mandatory;
• which sign-in methods are available;
• the minimum password length;
• whether a profile photograph is mandatory;
• which questions are asked during registration;
• the order in which profile data is collected;
• whether a new account or profile content requires moderation before publication;
• whether registration is open, invitation-only, or manually approved.

Discover, member search, and dating cards

In a card-based discovery mode, the member reviews one profile at a time. A card can show:

• the main photograph;
• display name;
• age;
• city or region;
• distance from the member;
• verification or activity indicators when configured.

The card can be opened to view the complete profile.

Primary card actions

• Pass or Dislike: skip the current profile.
• Like: express interest in the profile.
• Super Like: make the expression of interest more prominent through the SuperLikes Premium plugin.
• Rewind: return to the most recently skipped profile through the Rewind Premium plugin.

If both members like each other, the application creates a mutual match and can immediately prompt them to start a conversation.

Usage limits

The Likes Limit Premium plugin can limit the number of likes or profile cards available during a defined period. After reaching the limit, a member can be offered one or more of the following options:

• wait until the allowance resets;
• purchase Premium Membership;
• purchase the required action using internal credits;
• continue with another available discovery or community feature.

When no more profiles are available

The application can explain why the result set is empty and suggest that the member:

• change filters;
• increase the search distance;
• broaden the age range;
• return after new members join.

The Tinder Mode for Desktop App Premium plugin can provide a comparable swipe-based experience in the desktop web product.

Search filters and discovery rules

Members can be allowed to configure:

• maximum distance;
• the gender or account type they want to see;
• minimum and maximum age;
• online-only results;
• profiles with photographs only;
• additional filters based on custom profile questions.

Filter values can be saved or reset. The available filters depend on the active discovery mode, profile design, user role, and project rules.

The platform can also use profile answers and weighted compatibility logic so discovery is not limited to simple demographic filters.

Member profile

Viewing another member’s profile

A complete profile can display:

• display name and age;
• city, region, and distance;
• profile photographs;
• gender or account type;
• desired partner age range;
• an About Me description;
• a description of the person the member wants to meet;
• height, family status, children, lifestyle, or other structured details;
• interests and responses to custom questions;
• verification status;
• compatibility information.

Available actions can include:

• like or remove a like;
• send a Super Like;
• send a private message;
• add the member to Favorites;
• block the member;
• report the profile or an individual photograph.

Editing the member’s own profile

The member can be allowed to change:

• email address;
• display name;
• gender or account type;
• discovery preferences;
• location;
• date of birth;
• desired partner age range;
• About Me and Looking For text;
• structured profile details;
• answers to project-specific questions.

Custom profile fields

The operator can adapt the profile to the product concept. Additional questions can cover:

• lifestyle and habits;
• interests and hobbies;
• values;
• occupation or education;
• relationship goals;
• family plans;
• important compatibility criteria;
• any domain-specific attributes required by a niche community.

Answers can be displayed in the profile, used as search filters, and incorporated into compatibility calculations.

Photographs and media

Members can:

• upload multiple photographs;
• take a new photograph with the device camera;
• choose an image from the device library;
• set or replace the main profile photograph;
• delete individual photographs;
• open another member’s gallery;
• report an inappropriate image.

Photographs can require manual premoderation or automated review. The application can show a pending approval status, remove rejected content, and prompt the member to upload a replacement.

Selfie verification requires a clear main photograph in which the member’s face can be recognized.

Likes, matches, and My Interests

The My Interests Premium plugin can provide a single area for related dating activity.

Like

A Like expresses interest in another member and adds the profile to the relevant activity list.

Mutual Match

When two members like each other, the platform creates a mutual match. The application can then prompt either or both members to begin a conversation.

Super Like

The SuperLikes Premium plugin makes an expression of interest more visible than an ordinary Like. A project can provide a limited number of free Super Likes, include additional Super Likes in Premium Membership, or sell them for internal credits.

Liked Me

The Liked Me Premium plugin shows members who have already liked the current member. Names and photographs can be blurred or hidden until the member purchases a subscription.

Likes Given

The member can review profiles they previously liked. List items can show the date of the Like and the other member’s most recent activity.

Combined My Interests lists

Depending on the configuration, My Interests can combine:

• Liked Me;
• Likes Given;
• Mutual Matches;
• Compatible Matches;
• My Guests or Viewed Me;
• Bookmarks or Favorites.

The operator controls which lists are enabled and the order in which they appear.

Profile visitors, favorites, and compatibility

Guests and Viewed Me

The Viewed Me Premium plugin allows a member to see who opened their profile and when the visit occurred. The list can be blurred and fully revealed after the member upgrades.

Favorites

Members can save interesting profiles, open them again later, and remove them from Favorites.

Compatible Users

A separate list can show members selected by the project’s compatibility rules.

Matchmaking preferences

Members can be allowed to specify:

• distance from a selected city;
• desired answers from a potential partner;
• the importance of each criterion.

For each criterion, a member can select a preferred value or indicate that the criterion is not important. The available parameters depend on the profile structure and matching model.

Private messaging

Conversation list

The messaging interface can include:

• active conversations;
• archived conversations;
• new matches who can be contacted;
• unread indicators;
• conversation search or filtering.

If the member has no matches or conversations, the application can explain how to discover someone and begin communicating.

Conversation capabilities

In a private conversation, a member can:

• send and receive text messages;
• send photographs;
• view system messages about relevant actions;
• retry a message after a delivery error;
• delete an individual message;
• open the other member’s profile.

Conversation management

A conversation can be:

• marked as read or unread;
• archived;
• restored from the archive;
• deleted.

Inactive conversations can be moved to the archive automatically after a period defined by the operator. Restoring archived conversations can be included in Premium Membership.

Messaging without a mutual match

The operator can allow Premium members to start a conversation without a prior mutual match. The ability of the recipient to reply and any additional limits are controlled by the project configuration.

Community Hub

The Community Hub Ultimate plugin adds a complete interest-based community layer to the dating experience. It can combine four primary areas:

1. For You: a personalized content feed.
2. Groups: communities organized around shared interests.
3. Events: online or in-person activities.
4. Forum: structured topic-based discussions.

For You feed

Members can:

• read the general feed and posts from groups;
• create text posts;
• attach photographs;
• like posts;
• add comments;
• delete their own posts and comments;
• report content;
• open author profiles;
• see activity related to groups and events.

The operator can require an approved profile photograph or completed selfie verification before a member can publish content.

Groups

Members can:

• browse popular groups;
• see groups they have joined;
• create a new group;
• join an open group;
• request access to a private group;
• receive invitations;
• view a group’s feed, events, and member list;
• leave a group.

When creating a group, a member can be allowed to set:

• group name;
• cover image;
• description;
• visibility;
• invitation requirements;
• whether members may invite other people.

New groups and membership requests can be sent to moderation.

Events

Events inside native applications and the PWA are also supported by the Events for PWA and Native Apps Premium plugin.

Members can:

• browse general and group-specific events;
• review upcoming and recent events;
• search for events;
• open events on a map;
• see the date, location, description, organizer, and attendee list;
• mark themselves as Going or Interested;
• invite other members;
• create an event;
• add an image and ticket information.

New events can require moderator approval.

Forum

The forum can include:

• a forum home page;
• recent topics;
• categories;
• search;
• topic and reply pages;
• attachments;
• subscriptions to updates.

Members can create topics, reply, attach allowed files, subscribe to discussions, and report content. Moderators can approve, delete, lock, pin, and move topics.

Group and event chats

Groups and events can include a dedicated real-time chat with text messages and photographs. Availability is controlled by the project configuration.

Premium Membership in the user application

The project operator can sell a project-specific Premium Membership to end users. The Smart Paywall Ultimate plugin can present an upgrade offer when a member attempts to use a paid capability. Subscription duration, pricing, benefits, renewal rules, and store products are configured for the individual application.

Premium benefits can include:

• No Hidden Likes through the Liked Me Premium plugin;
• Message Anyone without a prior mutual match;
• Unlimited Likes through the Likes Limit Premium plugin;
• Incognito Mode through the Incognito Mode Premium plugin;
• Restore Archived Chats;
• Rewind through the Rewind Premium plugin;
• additional Super Likes through the SuperLikes Premium plugin;
• removal of advertising;
• expanded support or community privileges if they are part of the business model.

Incognito Mode

In Incognito Mode, a profile can be visible only to selected categories of members. For example, it can be limited to people the member has already liked, matched with, or saved. The exact visibility rule is configurable.

Subscription management

A subscription can renew automatically. Payment, cancellation, restoration, and renewal behavior depends on the app store or payment mechanism used by the project.

Other monetization models

Internal credits

Members can purchase credit packages and spend credits on individual actions such as Rewind, Super Like, virtual gifts, or other paid capabilities.

Advertising

The application can integrate mobile advertising networks and web advertising placements. The EPOM Ad Integration Premium plugin can display a native advertisement as a card inside the matching flow and provide advertisers with a self-service campaign portal.

The operator controls ad frequency and can disable advertising for Premium roles.

Combined model

The operator can combine:

• subscriptions;
• internal credits;
• advertising;
• paid messaging;
• Like limits;
• Super Likes;
• Rewind;
• paid access to Liked Me;
• virtual gifts;
• other project-specific paid actions.

Selfie and liveness verification

The Selfie/Liveness Verification Ultimate plugin helps confirm that an account is controlled by a real person and that a live person, rather than a photograph, video, or mask, is in front of the camera. The result can be compared with the main profile photograph and used in access rules.

Member flow

1. The member opens Selfie Verification.
2. The application explains the purpose of verification and requests camera access.
3. The member positions their face in the indicated area and follows the on-screen guidance.
4. The system checks for a live person in front of the camera.
5. The captured image is compared with the main profile photograph.
6. A verified badge can be added to the profile after a successful result.

Possible results

• verification successful;
• no face detected;
• insufficient similarity to the profile photograph;
• no suitable profile photograph available;
• unsuitable lighting or face position;
• maximum number of attempts exceeded;
• camera unavailable or permission denied.

Verification status can be displayed in profiles and used as a condition for access to selected community or communication features.

Safety and moderation visible to members

Reports

A member can report:

• a profile;
• a photograph;
• a post;
• a comment;
• a forum topic or reply.

Report categories can include spam, offensive behavior, and illegal content.

Blocking

A member can block another member. Blocking stops or limits subsequent interaction according to project rules.

Profile and photograph moderation

Profile fields and images can remain pending until approved. Members can see the relevant status and replace rejected material. The Text Moderation Premium plugin routes changes to free-text profile fields into a moderation queue. The AI Image Moderation Ultimate plugin can automatically detect inappropriate or low-quality photographs before publication.

Community moderation

Groups, events, posts, comments, and forum content can be subject to:

• approval before publication;
• removal after publication;
• report processing;
• restrictions for unverified members;
• dedicated moderator tools.

Automated protection

The IPQualityScore Fraud Prevention Premium plugin helps identify bots, scammers, VPNs, proxies, Tor connections, disposable email addresses, and virtual VoIP numbers. The Didit Identity and Age Verification Ultimate plugin adds identity document, age, and biometric liveness verification.

Notifications

Email notifications

Members can be allowed to enable or disable email notifications for:

• new messages;
• new mutual matches;
• new Likes.

Push notifications

The application can send push notifications for:

• new matches;
• private messages;
• Likes;
• new forum topics;
• group or event activity;
• other important product events.

Community Hub notifications

Members can receive notifications about:

• group invitations;
• event invitations;
• approved membership requests;
• activity inside groups, events, feeds, or forum discussions.

PWA and installation on a mobile device

The web application can be used directly in a mobile browser or installed on the home screen as a Progressive Web App.

On iPhone, installation can be completed through Share -> Add to Home Screen. The PWA then launches in a separate application-style window and can use push notifications when the member grants permission.

The PWA provides an additional distribution channel that does not depend on an app store. A project can also provide separate native applications for iOS and Android.

Account settings and support

The Settings area can include:

• Privacy Policy;
• Terms of Use;
• email notification preferences;
• push notification preferences;
• Incognito Mode;
• Selfie Verification;
• Contact Us;
• password change;
• sign out.

Password change

The member enters the current password, a new password, and confirmation of the new password.

Contacting support

An integrated support form can include:

• sender address;
• department selection;
• subject;
• message body.

The request is sent to the operator’s support team. The FreeScout Integration Ultimate plugin can connect the form to a dedicated help desk workspace.

Data and policy screens

The product can include screens for personal data, consent, privacy policies, legal notices, and third-party services. The exact set depends on the applicable law, permissions, and project configuration.

Analytics and operational integrations

These capabilities are mostly invisible to ordinary members but help the operator understand and improve the application.

A project can include:

• Mixpanel for product analytics – Ultimate plugin;
• Firebase for authentication, analytics, and push notifications;
• Firebase In-App Messaging for contextual messages inside mobile applications – Ultimate plugin;
• Adapty for subscription, paywall, and monetization management – Ultimate plugin;
• AppsFlyer for paid traffic attribution, OneLink campaigns, and marketing fraud protection – Ultimate plugin;
• Conversion Tracking for Meta and Google Ads for registration, purchase, and subscription events – Ultimate plugin;
• SkaDate to Sendy Integration for welcome, follow-up, drip, and reactivation email sequences – Ultimate plugin;
• EPOM Ad Integration for native advertising – Premium plugin;
• FreeScout Integration for customer support – Ultimate plugin;
• AI Image Moderation and IPQualityScore Fraud Prevention for automated moderation and risk checking;
• custom profile questions and operational tools for groups, events, feed content, and forums.

The operator can analyze registration steps, profile views, Likes, matches, messages, purchases, subscription conversion, and retention, then improve onboarding, paywalls, notifications, and core product flows.

Product flexibility and customization

Core product scenarios

Common platform scenarios include:

• registration and sign-in;
• profiles and photographs;
• member search and discovery;
• Likes and mutual matches;
• private messaging;
• account settings and notifications;
• monetization;
• administration and moderation.

Optional capabilities

Depending on the selected package and modules, a project can add:

• Liked Me – Premium plugin;
• Rewind – Premium plugin;
• SuperLikes – Premium plugin;
• Incognito Mode – Premium plugin;
• My Interests – Premium plugin;
• Selfie/Liveness Verification – Ultimate plugin;
• Community Hub – Ultimate plugin;
• advanced analytics;
• cross-platform subscription management;
• customer support integration;
• advertising, automated moderation, and antifraud tools.

Adaptation to a specific concept

The project operator can change:

• brand, colors, images, and interface copy;
• onboarding structure;
• profile questions and sections;
• compatibility and matching rules;
• primary screen order;
• access rules for each function;
• plans, limits, and paid actions;
• topics and permissions for groups, events, and forums;
• moderation rules and community policy;
• unique custom functions and interaction models.

This makes SkaDate suitable for a general dating application or a product organized around a specific interest, value system, profession, lifestyle, local community, or another social interaction model.

Feature availability note

This part describes the combined capabilities demonstrated in the reviewed mobile SkaDate configuration. An individual capability may belong to the platform core, an optional plugin, an integration, or a custom project setting.

Before implementation, the project team should define the required capability set, confirm module compatibility, and specify which functions are available to all members, which require a paid role, and which are limited to administrators or moderators.

Back to contents

Part II. Administration Console Capabilities

The SkaDate administration console is designed to manage the dating business, member database, monetization, content, mobile applications, integrations, and moderation workflows. It is not only a technical settings area. It is the operational workspace through which the project team manages the product every day.

An administrator can receive full access to project configuration. A moderator can receive only the permissions required for a specific role, such as approving photographs and profile changes without access to finance, SMTP credentials, payment settings, cloud keys, or plugin management.

The exact set of sections depends on installed plugins and the permissions assigned to the current staff member.

Main dashboard

The main dashboard combines important project indicators and shortcuts.

Financial statistics

An administrator can review:

• number of transactions;
• total payment amount;
• statistics for today, yesterday, the last 7 or 30 days, and the last year;
• a direct link to the complete transaction history.

Member statistics

The dashboard can show:

• number of registrations;
• number of application sign-ins;
• change over a selected period;
• a direct link to the member list.

Content statistics

The administrator can select a content type and review volume over time. Statistics can include:

• members;
• comments;
• photograph comments;
• photographs;
• Community Hub posts and comments;
• events;
• forum topics;
• groups;
• changes to profile questions.

Dashboard components can be configured and rearranged around the team’s operational priorities.

Member management

Member list and search

An administrator can:

• browse the complete member database;
• search by name, email address, or internal User ID;
• see registration date, account status, and last activity;
• review new and recently active members;
• open a dedicated list of suspended accounts;
• invite new members;
• select multiple accounts for a bulk operation;
• use additional lists created by installed modules;
• export advanced search results when the appropriate module is installed.

Administrative member profile

The administrative view of a member can include:

• internal User ID and username;
• display name, age, gender or account type, and discovery preferences;
• email address and verified phone number;
• registration date and last activity;
• registration IP address;
• location;
• answers to all profile questions;
• photographs and moderation status;
• selfie verification status;
• a link to the member’s profile in Mixpanel when the Ultimate analytics plugin is enabled.

Because this area contains personal information, access should be limited to staff members who require it for their work.

Administrative account actions

Depending on staff permissions, the console can allow an operator to:

• change the member’s role;
• assign or change membership;
• mark the profile as featured;
• suspend the account;
• apply a shadow ban;
• restore an allowed account status;
• delete the account;
• open the member’s photographs;
• review reports submitted against the member;
• review reports submitted by the member;
• open the member’s conversation review area.

A shadow ban can restrict the visibility and interactions of a suspicious account without displaying an ordinary public suspension notice.

Administrators, moderators, and access separation

Adding a moderator

An administrator can appoint a new moderator using the email address of an existing member account.

Permission matrix

Permissions can be assigned independently for different areas of the product, including:

• photographs;
• members;
• administrative settings;
• Paid Membership;
• swipe and discovery functions;
• Liked Me;
• SuperLikes;
• Rewind;
• Incognito Mode;
• profile question moderation;
• events;
• forum;
• groups;
• newsfeed.

This allows the operator to create separate operational roles, for example a photograph reviewer, a community moderator, a member safety specialist, or a subscription manager.

Practical separation of responsibilities

Typical access separation can work as follows:

• System settings and plugins: full administrator access; normally unavailable to moderators.
• Members: administrators can manage search, roles, memberships, suspension, and deletion; moderators receive only approved actions.
• Content approval queue: administrators configure policy and can process content; moderators approve or reject material.
• Community Hub: administrators configure and moderate; moderators can receive access to posts, groups, events, and forums.
• Finance: normally limited to administrators or authorized finance staff.
• SMTP, app store keys, cloud keys, and API credentials: limited to trusted technical administrators.

An administrator can revoke moderator status or change the permission set without changing the employee’s ordinary member role.

End-user roles and permissions

In addition to staff roles, the console can define roles for end users, such as Free, Premium, VIP, or internal service segments.

An administrator can:

• create a role;
• rename a role;
• select the default role;
• see the number of members in each role;
• show or hide a role label on avatars;
• delete an unused role;
• assign a role to an individual member.

Granular role permissions

For each role, the administrator can independently allow or deny:

• viewing and uploading photographs;
• commenting on photographs;
• searching for members and viewing profiles;
• posting on a profile wall;
• reading messages;
• beginning or continuing a conversation;
• removal of advertising;
• sending virtual gifts;
• placement in the Hot List;
• unlimited swipes;
• hiding AdMob banners;
• restoring archived conversations;
• removal of a card limit;
• beginning a conversation without the normal restriction;
• viewing Liked Me;
• using SuperLikes;
• using Rewind;
• hiding a profile through Incognito Mode;
• creating, viewing, and commenting on events;
• creating topics and replying in the forum;
• creating groups and publishing in them;
• publishing and commenting in the newsfeed.

Roles therefore work both as an access-control mechanism and as the foundation for paid plans.

Profile question builder

The administrator can adapt the profile structure to the concept of the application.

Sections and questions

The console can be used to:

• add profile sections;
• change section order;
• add, edit, and reorder questions;
• assign a question to selected account types;
• define allowed answers;
• hide unnecessary fields;
• use separate questions about the member and the member’s desired partner.

Supported field types

The builder can support:

• short text;
• extended text;
• password;
• date;
• date with automatic age calculation;
• numeric or value range;
• single choice;
• single choice displayed as radio buttons;
• multiple choice;
• an optimized single-choice control for frequently used values.

Account types

Questions can be displayed to different account types. Onboarding and profile design can therefore vary by gender, professional role, community category, or another segmentation model defined by the operator.

Matchmaking and compatibility

The administrator can determine which answers participate in compatibility calculations.

The console can be used to:

• create match questions;
• connect a question about the member with a question about the desired partner;
• include gender, age, location, and custom fields;
• assign weights to individual criteria;
• change compatibility calculation rules;
• choose how frequently new match recommendations are sent by email.

New match emails can be sent daily, every few days, weekly, or disabled.

Registration, privacy, and project access

General project settings

An administrator can change:

• website or application name;
• system email address;
• tagline;
• product description;
• date and time format;
• time zone;
• primary currency;
• relative or absolute display of time.

Registration settings

The console can configure:

• CAPTCHA on registration;
• mandatory email confirmation;
• display name or username behavior;
• whether avatar upload is shown, hidden, or required during onboarding;
• mandatory acceptance of the Terms of Use;
• manual approval of new members;
• open registration or invitation-only access.

Guest access

The project can be:

• accessible to guests;
• completely closed to unregistered visitors;
• protected by a shared access password before sign-in or registration.

Restricted usernames

The administrator can maintain a list of restricted names so members cannot register system names, offensive names, misleading names, or protected brand names.

Photograph, media, and attachment settings

An administrator can define:

• standard and large avatar dimensions;
• maximum profile photograph size;
• default avatar image;
• maximum upload size;
• allowed attachment extensions;
• trusted domains for embedded videos and iframes;
• whether rich media is allowed in posts and comments;
• whether user-supplied HTML is allowed.

Disabling user HTML and limiting approved embedded sources can reduce the risk of unsafe content.

Premoderation

The administrator selects which types of material must be approved before publication.

Premoderation can be enabled independently for:

• new members;
• profile photographs;
• ordinary photographs;
• photograph comments;
• profile questions and free-text answers;
• events;
• groups;
• forum content.

For Approve queue

A moderator can see how many items are waiting and can:

• open the author’s profile;
• inspect a new photograph or changed profile answer;
• approve an individual item;
• reject or remove the item;
• select multiple records;
• perform bulk approval or removal.

The Text Moderation Premium plugin adds a review queue for changes to free-text fields. The AI Image Moderation Ultimate plugin can automatically reject unsuitable images before they appear in the application.

AI Photo Moderation

The AI Image Moderation Ultimate plugin gives administrators a dedicated policy screen for automatically reviewing images before they appear in the application. The plugin can block an upload when the configured moderation criteria are detected and can apply different policies to member profile photographs and Community Hub or forum content.

AWS service configuration

The administrator connects the plugin to the configured AWS service using an access key, secret key, and region. These credentials are sensitive infrastructure data. They should be available only to trusted technical administrators and should never be copied into product documentation, screenshots, support conversations, or ordinary moderator accounts.

User photo moderation

User photo moderation can be enabled or disabled independently. The administrator can set an individual sensitivity level from 0 to 100 for each category:

• Nudity: Graphic Nudity, Sexual Activity, and Adult Toys.
• Suggestive: Swimwear/Underwear, Partial Nudity, and Sexual Situations.
• Violence: Violence or Gore, Weapon, and Self Injury.
• Disturbing: Corpses, Hanging, and Explosions.

Images that match the active policy can be blocked during upload. Additional controls allow the administrator to:

• reject images containing readable text, text overlays, or watermarks;
• automatically approve a main profile photograph when it contains exactly one detected face and passes every other moderation check;
• require at least one detectable human face and reject images without a recognizable face.

Automatic approval can reduce the manual moderation queue for valid avatars, while the face requirement helps prevent logos, objects, landscapes, and other non-profile images from being used where a human profile photograph is required.

Community Hub and forum moderation

Community Hub and forum image moderation can be enabled or disabled separately from user photo moderation. It applies to photographs uploaded to Community Hub posts, groups, events, and forum attachments. Because this scope has an independent policy, a project can use stricter or different rules for public community content than for member profile photographs.

The administrator can configure an individual sensitivity level from 0 to 100 for each category:

• Exposed genitalia: Exposed Male Genitalia, Exposed Female Genitalia, and Exposed Buttocks or Anus.
• Sexual activity: Explicit Sexual Activity, Bondage or Restraints, and Sex Toys.
• Nudity: Graphic Nudity, Sexual Activity, and Adult Toys.
• Suggestive: Swimwear/Underwear, Partial Nudity, and Sexual Situations.
• Violence: Violence or Gore, Weapon, and Self Injury.
• Disturbing: Corpses, Hanging, and Explosions.

A separate option can reject Community Hub and forum images that contain readable text, text overlays, or watermarks.

Operational effect

AI Photo Moderation can stop disallowed images before publication, reduce repetitive manual review, and keep profile-photo rules separate from public community-content rules. Administrators should test sensitivity settings against representative content from the target market and retain a manual review or appeal process for uncertain or incorrectly rejected uploads.

Reports, blocks, and extended moderation

Flagged Content

Reports can be separated into profile and photograph queues. For each record, a moderator can see:

• the reported object;
• content author;
• member who submitted the report;
• report reason;
• creation time.

The moderator can dismiss an incorrect flag or remove violating material. Categories can include spam, offensive content, and illegal content.

Conversation review

With the required permission, a moderator can open a member’s conversations, separate initiated and received conversations, and search the list. This can support investigations into spam, fraud, harassment, or unwanted communication.

Access to private messages should be strictly controlled by internal policy, the Terms of Service, and applicable law.

Actions after an investigation

Depending on permissions, staff can:

• dismiss an incorrect report;
• suspend the account;
• apply a shadow ban;
• change the role or membership;
• remove violating material;
• delete the account.

Fraud checks and risk prevention

The IPQualityScore Fraud Prevention Premium plugin can evaluate registrations and sign-ins before suspicious accounts enter the community.

Depending on configuration, the integration can:

• detect VPN, proxy, and Tor connections that may conceal a member’s real location;
• calculate a real-time fraud score for an IP address or device fingerprint;
• identify known malicious addresses, automated bot activity, and high-risk traffic;
• check email addresses for disposable, compromised, or otherwise risky signals;
• evaluate phone numbers, including virtual VoIP numbers;
• automatically allow, flag, or block activity according to the operator’s risk rules.

Authorized staff can combine these technical signals with profile quality, reports, conversations, Likes, matches, and other behavior when investigating an account. Risk scores should support an operational decision rather than replace contextual review.

Community Hub moderation

The Community Hub Ultimate plugin includes a dedicated moderation console.

Posts

For a post, the moderator can see:

• author;
• text or a direct link to the post;
• context type;
• related group or event;
• publication date.

The post can be opened, the author’s profile can be reviewed, and the material can be deleted.

Comments

For a comment, the console can display the author, text, context type, related post, and publication date. The moderator can open the original post and delete the comment.

Events

The event table can show title, organizer, related group, start date, and available actions. An event can be opened or removed.

Groups

For a group, the console can show title, owner, member count, and creation date. The moderator can open or remove the group.

Forum

The console can list topics, categories, author of the latest reply, and activity date. The moderator can open or remove a topic.

Community Hub configuration

The administrator can determine who can see the Community Hub:

• nobody;
• administrators and moderators only during preparation;
• all members.

Newsfeed configuration

The administrator can configure:

• status updates;
• Likes;
• comments;
• number of comments expanded by default;
• activity items for registration, profile changes, and avatar changes;
• photographs, gifts, events, forum topics, and groups in the feed.

Changes to enabled activity types may apply only to new feed events.

Group page layout

The administrator can assemble a group page by drag and drop using:

• group information;
• members;
• join, leave, and invite controls;
• map;
• wall or newsfeed;
• RSS;
• custom HTML.

The forum can be connected to groups as an additional discussion model.

Forum configuration

The administrator can determine whether attachments are allowed in forum topics and replies.

Event configuration

The Events for PWA and Native Apps Premium plugin adds events to mobile applications and the PWA. Permissions to create, view, and comment on events can be assigned by user role.

Membership, paywalls, and paid permissions

The administrator can create a custom end-user subscription model.

Membership levels

The console can be used to:

• connect a membership level to a user role;
• create multiple subscription levels;
• define different plans for different account types;
• set duration in days or months;
• set price and currency;
• enable recurring payments;
• specify a Custom ID that maps the plan to an app store product;
• list members by membership;
• assign membership manually in the member profile;
• configure an email reminder before membership expires.

Benefit and entitlement selection

The administrator selects which actions appear on the subscription page and belong to a paid level. Benefits can include:

• viewing photographs and profiles;
• sending messages;
• removal of advertising;
• virtual gifts;
• Unlimited Swipes;
• restoration of archived conversations;
• removal of the daily card limit;
• messaging without a prior match;
• Liked Me;
• SuperLikes;
• Rewind;
• Incognito Mode;
• expanded permissions in events, groups, forums, and newsfeed.

The Smart Paywall Ultimate plugin can present the relevant subscription benefit when a member attempts to access a Premium function.

Finance and transactions

The Finance section contains a payment journal. A transaction can display:

• Transaction ID;
• payment gateway;
• related plugin or product;
• plan description;
• amount;
• currency;
• member;
• transaction time;
• platform or renewal type when provided by the store.

The table supports pagination, and the summary can show total amounts by currency. Financial reporting helps connect subscription sales with the relevant store, platform, and plan.

Advertising management

Website banners

An administrator can:

• create advertising banners;
• review and edit the banner list;
• assign banners globally or to selected sections;
• choose Content or Sidebar positions;
• use different placements for Messages, Membership, Photos, Events, Forum, and Groups;
• apply geographic restrictions if supported by the advertising module.

AdMob in mobile applications

For iOS and Android, the administrator can specify an Ad Unit ID, enable or disable advertising, and select pages where banners are permitted.

EPOM cards in discovery

The EPOM Ad Integration Premium plugin can display advertisement cards inside the matching flow. The administrator can enable the integration and define how many member profiles appear before an advertisement.

Premium roles can be exempted from banners and other advertising placements.

Mobile application and PWA settings

Discovery mode

The administrator can select:

• Tinder Mode together with ordinary Browse Users;
• Tinder Mode only;
• Browse Users only.

The Tinder Mode for Desktop App Premium plugin provides the swipe flow in the desktop web application.

Cards and limits

The console can configure:

• number of available cards during 24 hours;
• number of profiles loaded in one request;
• removal of limits for selected roles;
• behavior of the Likes Limit Premium plugin.

Additional application settings

An administrator can:

• enable in-app review prompts;
• provide App Store and Google Play links;
• automatically direct mobile visitors to the PWA;
• enable push notifications;
• enable or disable advertising;
• control Community Hub visibility;
• enable screenshot and screen-recording protection;
• receive supported events about screen-capture attempts.

Branding

For the application start screen, an administrator can upload:

• logo;
• background image;
• preferred logo width.

Security keys

The console can upload an existing key pair or generate a new pair for protected communication between the mobile application and the server. This screen should be limited to trusted administrators.

In-app purchases for iOS and Android

The administrator can enable mobile monetization and configure:

• application package name;
• membership actions displayed in mobile applications;
• Android service account and private key;
• data required to validate iOS purchases;
• store test mode;
• webhook URL for Google Play;
• webhook URL for the App Store.

These settings allow the server to validate purchases, receive store notifications, process renewals, and synchronize the member’s access level.

Payment credentials and store secrets are highly sensitive and should not be available to ordinary moderators.

The Adapty Ultimate plugin adds cross-platform subscription, paywall, and monetization analytics management.

Selfie and liveness verification settings

The Selfie/Liveness Verification Ultimate plugin has a dedicated configuration screen.

An administrator can:

• enable or disable the capability;
• connect the required AWS services;
• select the cloud region and service storage;
• limit failed attempts during 24 hours;
• configure the Liveness Confidence Threshold;
• configure the Face Similarity Threshold;
• enable automatic removal of suspension after successful verification;
• define a separate threshold for automatic unsuspension.

Higher thresholds make the check stricter but can increase rejection of real members because of lighting, camera angle, or photograph quality.

Cloud service secrets should never be included in documentation, logs, screenshots, or moderator access.

Themes, branding, and visual appearance

Themes

An administrator can:

• review available themes;
• activate a theme;
• upload a new theme;
• use a separate theme for the administration dashboard.

Visual customization

The interface can be used to change:

• page background color;
• home page background;
• header image;
• home page logo;
• internal logo;
• administration console logo;
• footer color;
• colors for text, headings, links, and menus.

CSS and graphics

The console can display the active theme CSS, allow custom styles to be added, and provide a section for graphic assets.

Menus, pages, and layout

Menu management

The administrator can see pages created by the core platform, plugins, or the project owner. A drag-and-drop interface can be used to:

• reorder Main Menu items;
• reorder Bottom Menu items;
• hide a page without deleting it;
• add a menu item;
• display an item to everyone, guests only, or signed-in members only.

User Profile layout

The profile page can be assembled from blocks such as:

• About Me;
• photographs;
• Profile Details;
• Compatibility;
• groups;
• events;
• newsfeed;
• membership;
• gifts;
• Selfie Verification;
• Risk Checks;
• wall, RSS, or custom HTML.

Important blocks can be frozen so an end user cannot move or hide them.

User Dashboard layout

The end-user dashboard can be assembled from:

• My Matches;
• Newsfeed;
• Quick Links;
• Quick Search;
• Recently Viewed Me;
• Hot List;
• Bookmarks;
• Membership;
• Welcome block;
• Moderator Panel;
• custom HTML or RSS.

The administrator decides whether members can personalize widget placement without changing the overall page structure.

Maintenance page and splash screen

The administrator can temporarily place the project into maintenance mode and display a custom HTML message. Administrator access can remain available through a dedicated sign-in page.

A splash screen shown before the application can:

• present a warning or age restriction;
• ask the visitor to confirm consent before entering;
• define the Enter button text;
• redirect a visitor who declines to a specified URL.

Languages and localization

The console contains a language string editor for the core platform and every installed plugin.

An administrator can:

• switch between languages;
• search by visible text or internal key;
• filter strings by section or plugin;
• edit translations directly in the interface;
• identify missing translations;
• enable or disable languages;
• change language order;
• select the default language;
• upload a language pack in XML or ZIP format;
• export and back up localization.

This allows the project to localize standard interface text and the text provided by Premium and Ultimate modules.

Email, SMTP, and mass mailing

SMTP settings

An administrator can configure:

• use of an external SMTP server;
• host name and port;
• username and password;
• secure connection type;
• connection testing before sending.

SMTP credentials are sensitive infrastructure information and should be available only to trusted administrators.

Mass mailing

The built-in mailing tool can:

• send email to active members;
• select recipients by user role;
• use text or HTML format;
• define subject and message body;
• personalize the message with member name, email, project name, and project URL variables;
• include an unsubscribe URL.

The SkaDate to Sendy Integration Ultimate plugin adds member synchronization, welcome sequences, follow-up messages, drip campaigns, and reactivation campaigns.

Contact Us and customer support

An administrator can create multiple support departments and define for each department:

• name visible to members;
• recipient email address;
• sender address used in outgoing notifications.

The FreeScout Integration Ultimate plugin sends Contact Us requests to a help desk. The support team can process tickets centrally, assign them to staff, and keep support history outside an ordinary mailbox.

SEO, sitemap, and social sharing

SEO for individual page types

For different page types, an administrator can define:

• title;
• meta description;
• meta keywords;
• permission or prohibition of search indexing.

Settings can differ for core pages, member profiles, photographs, events, forums, and groups. The interface can show recommended title and description lengths.

Sitemap

The console can:

• update the sitemap daily, weekly, or monthly;
• include or exclude core pages;
• add member pages, photographs, events, forums, and groups.

Open Graph and social metadata

Social metadata can be generated from SEO settings. Depending on the page, the platform can use the project logo, member photograph, event image, group image, video, or album image. A separate high-quality image can be uploaded for shared posts.

Additional code

The administrator can add custom code in the document head or before the closing body tag for analytics and other integrations, and can upload a favicon.

Analytics

The Mixpanel Ultimate plugin connects product behavior with the relevant member. The administrative member profile can link directly to the person’s Mixpanel profile for event, journey, activity, and engagement analysis.

The administrator can also connect:

• Google Analytics;
• AppsFlyer – Ultimate plugin;
• Conversion Tracking for Meta and Google Ads – Ultimate plugin;
• Adapty for subscription analytics – Ultimate plugin.

Registration, profile view, Like, match, message, purchase, and subscription events can be used for funnel, retention, and monetization analysis.

Plugin management

The administration console can display:

• active plugins;
• installed but inactive plugins;
• plugins available for installation;
• name and purpose of each module.

Depending on plugin status, an administrator can:

• open Settings;
• activate;
• deactivate;
• update;
• remove;
• add a license;
• upload a new plugin package.

The modular architecture allows a project to add billing gateways, Community Hub, verification, analytics, moderation, monetization, and other capabilities without combining every feature into one monolithic configuration.

Deactivating or removing a system plugin can disrupt the application. Such operations should be performed only by a technical administrator after backup and dependency review.

Moderator capabilities

With the appropriate permissions, a moderator can:

• process the photograph approval queue;
• review profile changes;
• evaluate reports against profiles and photographs;
• open related member profiles;
• review conversations as part of an authorized investigation;
• suspend or restrict violating members;
• work with the fraud dashboard;
• remove violating posts and comments;
• moderate groups, events, and forums;
• access the Community Hub before it is opened to all members.

A moderator normally does not need access to:

• financial transactions;
• SMTP credentials;
• API or cloud keys;
• app store configuration;
• plugin installation or removal;
• global project configuration.

Availability and security note

This part describes the combined capabilities found in the reviewed SkaDate administration configuration. Individual screens can belong to the core platform, standard plugins, Premium plugins, Ultimate plugins, third-party integrations, or custom project modifications.

The administration console contains personal member data and sensitive infrastructure settings. Production operation should include:

• minimum necessary permissions for each employee;
• separation of administrator and moderator roles;
• no transfer of secret keys through documents, screenshots, or ordinary chats;
• restricted access to SMTP, billing, app store, and cloud settings;
• prompt revocation of access for former employees;
• documented internal procedures for report processing and conversation review;
• a verified backup before plugin updates, deactivation, or removal.

Back to contents

Conclusion

SkaDate provides a configurable user-facing dating and community application together with an operational administration console. The platform can support conventional dating flows, compatibility-based discovery, social community features, multiple monetization models, identity and content protection, product analytics, lifecycle marketing, and granular staff access.

The platform should be evaluated as a modular foundation. The final product configuration is defined by the selected license, active Premium and Ultimate plugins, third-party services, role and membership rules, design configuration, and any custom development required for the target market.

For additional information, visit SkaDate, review the plugin catalog, or request a project consultation.