English privacy policy
1. Sard and Focus Trading
Sard (SARD / سرد) is a social and live-audio service operated by Focus Trading. This policy explains how we handle information when you use the app, its associated services and this privacy page.
Sard is intended for users aged 18 and above. For privacy questions or requests concerning your information, contact info@sared.online.
2. Information we process
- Account and profile: your name, username, email address, password hash, gender and date of birth, plus any profile photo, biography, nationality, education, interests or information about how you found Sard that you provide. Public-profile responses do not include your email address or date of birth.
- Content and social activity: posts, blogs, comments, replies, uploaded media, reactions, reposts, follows, blocks and notifications, together with account identifiers and activity times.
- Chat and audio rooms: chat identifiers, messages and attachments processed through Agora Chat, room membership and roles, and audio transmitted through Agora. When a room is recorded, participants’ audio may be included in the recording and made available for playback to users allowed to access it.
- Membership and purchases: premium-request reasons, contact preferences, an optional phone number, consent records and review history. If you use store-subscription features, the backend also processes transaction identifiers, receipts or purchase-verification data, the store platform, plan and entitlement dates.
- Safety and support: reports, moderation decisions, account restrictions, information you send to support, and authentication sessions and verification codes used to secure your account.
- Technical information: IP addresses, request paths, response codes and times in server logs; connection and device information needed by communication services; and crash reports processed by Google Firebase Crashlytics. Crash reports can include error messages, stack traces, installation identifiers, device model, operating-system and app versions, and crash times.
- Data on your device: sign-in credentials or tokens in platform-protected storage, app preferences, cached profile and room information, images, chat history and downloaded media. These support sign-in, display, messaging and playback.
3. How information is used and shared
We use information to create and verify accounts, sign users in, display profiles and content, deliver messages, run audio rooms and recordings, process membership requests, verify purchases, provide notifications and support, prevent abuse, investigate reports, diagnose crashes and maintain the service.
Other users can see the profile information, content and room activity made available to them by the relevant feature and its access controls. Room participants can hear audio you publish. Recipients may save or copy shared content, messages or recordings; account deletion does not automatically remove copies held independently by other users.
Recording can start automatically in configured rooms. Minimizing the app does not necessarily stop audio participation or recording. Mute your microphone or leave the room to stop contributing audio; this does not remove audio already recorded. Room hosts must provide recording notice and obtain any consent required by applicable law.
Authorized administrators access information needed for membership review, support, security and moderation. We use the service providers described below to operate these features. Information may also be disclosed when necessary to respond to a binding legal requirement or protect users and the service from abuse.
4. Service providers and processing locations
- Hostinger and its configured Titan email service: hosting of our production backend and handling of business/support email.
- Amazon Web Services S3: storage of room recordings and files used in recording processing.
- Agora: real-time audio, chat identities, messaging and cloud recording. Its services also process connection, device and diagnostic information to deliver and troubleshoot communication. See the Agora privacy policy.
- Brevo: transactional email, such as verification codes, account notices and membership-request alerts.
- Google Firebase Crashlytics: crash reporting and technical diagnostics in the production app. See Firebase’s privacy information.
- Google Fonts: the mobile app may download fonts when they are not already available locally. Such requests disclose network information, including your IP address, to the font-delivery service. This privacy webpage embeds its fonts and does not request them from Google.
- Google Play or Apple: purchase verification and store-subscription management when you use the corresponding store features.
Providers may process information in countries other than your own. Processing locations and provider-held records depend on the service and its configuration. Contact us if you need information about the processing or deletion of data associated with your account.
5. Retention and account deletion
Account information and content are stored to provide the service while your account is active. Deleting an item normally removes it from ordinary app access first; it does not mean that every database record, backup or provider copy is immediately erased. The following describes our current cleanup behavior.
| Data or process | What happens |
|---|---|
| Confirmed account deletion | Access is disabled and Sard sign-in sessions are revoked. The account becomes eligible for permanent cleanup 30 days after confirmation. A daily job processes eligible accounts. Unresolved live rooms, recordings, failed provider operations or processing backlogs can delay completion; 30 days is not a maximum deadline for erasing every copy. |
| Owned content and media | Account cleanup removes owned posts, blogs and rooms and queues associated local images and recording files for removal. Failed media cleanup is retried separately. Files still referenced by other content can remain. Cleanup also requests deletion of the associated Agora user account. Recordings owned by someone else may still contain audio you contributed. |
| Sign-in records | Expired customer-session records and their associated token hashes are removed by a daily job, or when the account is permanently removed. Revoking a session prevents its use but does not immediately erase its stored record. |
| Administrator sign-in audits | Scheduled cleanup removes administrator authentication-audit records older than 90 days. This period does not apply to moderation-case records or all other audit categories. |
| Routine database and upload backups | Completed routine backups normally expire approximately 15–16 days after the backup is created, depending on the next successful daily cleanup. This period is not counted from your deletion request and does not cover manual backups or older S3 object versions. |
| Server logs | The system journal has a 7-day age limit. Forwarded system logs keep 4 weekly archives, and web-server logs keep 14 daily archives. Archive counts are not a fixed maximum age: empty logs, failed rotation or outages can extend the time a record remains. |
| Firebase crash reports | Google states that Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. This is the provider’s cleanup process, not a promise that deleting your Sard account immediately removes all diagnostic records. See Firebase’s retention information. |
Information that can remain after deletion
- Comments on other users’ content: the link to your account is removed and attribution changes to “Deleted User”, but comment text can remain. Its wording may still identify you. You can remove eligible comments before deleting your account or contact us about specific retained text.
- Purchase, moderation and support records: some transaction identifiers, receipts and former account identifiers can remain after the account link is removed. Moderation cases, reports and support correspondence can also remain outside the account-cleanup process. These categories do not currently have a uniform automatic expiry or a guaranteed maximum retention period; they require separate review and removal. Such records are not necessarily anonymous.
- Manual backups and older recording versions: manual operational backups are outside routine backup expiry. S3 file deletion can leave older versions behind a deletion marker. These copies are not covered by the 30-day account-cleanup schedule or the routine backup period; a fixed maximum retention period is not currently established for them.
- Provider and device copies: chat history, provider logs, store records and device caches have separate lifecycles. Deleting your account does not automatically remove every recipient’s chat history or copies downloaded to another device. Uninstalling the app or clearing its storage is not a substitute for requesting server-side account deletion.
To ask about retained information or request review of a specific item, contact info@sared.online. We may need to verify ownership and assess any security, dispute or legal obligations relevant to your request.
6. Your choices and requests
You can edit supported profile fields, remove eligible content, manage follows and blocks, and use the account-deletion option in the app’s settings. The deletion flow sends a six-digit verification code to your account email, valid for 10 minutes, and requires confirmation. Confirmed deletion cannot be undone through the app. Account deactivation and reactivation are separate features.
You can contact info@sared.online to request access to, correction of, or removal of information associated with you, or to raise a privacy concern. Identify the account and information involved, but never send a password, sign-in token or verification code. Your request may require an identity check. Any rights and exceptions provided by applicable law remain unaffected by this policy.
Deleting your Sard account does not itself cancel a subscription billed by an app store. Use the relevant store’s subscription-management controls if applicable.
7. Security, permissions and device storage
We use HTTPS for the production API and this page, password hashing, authenticated access and restricted administrative access. No system can guarantee absolute security. Protect your device and credentials, and contact us if you suspect unauthorized account access.
The app uses microphone access to publish audio in rooms, camera access when capturing media, and system media selection to attach files you choose. Notification permissions control device alerts; storage permissions may be used for supported downloads on older Android versions. You can manage permissions in your device settings, although denying a permission can prevent the corresponding feature from working. A room recording may retain your published voice; consider this before speaking in a recorded room.
App preferences, cached media and chat data may remain on your device. Device settings and app controls can remove local data, but saved files, system backups and copies on other devices may remain separately.
This privacy webpage contains no analytics scripts, tracking cookies or submission forms. Its logo and fonts are embedded. The hosting server still records access information such as IP address, request path, time and response status.
If you believe a person under 18 has provided personal information to Sard, contact us so that we can review the account or content involved.
8. Contact and updates
Sard / Focus Trading
Privacy and support: info@sared.online
We may update this policy when our service or data-handling practices change. The latest version will appear on this page with its updated date. Please review it periodically.