AmraEk.com Terms & Conditions
English — version 2026-10-17-1
These Terms apply when you expressly accept this version after AmraEk identifies it as the current published agreement. A draft or preview copy is not an effective agreement, and visiting the website alone is not acceptance. Describing a feature does not make it available; the availability and eligibility conditions in this document continue to apply.
The privacy and data-retention provisions are part of this single document, with no separate general privacy agreement. Before agreeing, read the complete version linked from signup and make the unchecked “I agree” choice yourself. General acceptance does not replace a separate permission required for an optional import, location access, advertising tracking, a charge, guardian approval or another optional action.
Contents
- Service, scope and interpretation
- Acceptance, versions and changes
- Eligibility, age and family access
- Registration, provider login and account accuracy
- Credentials, sessions and recovery
- Identity review and verification labels
- Personal profiles and social relationships
- Content ownership and permission to operate the service
- Publishing, audiences, tags and sharing
- Photos, videos, editing and music
- Stories and Yearly Memories
- Optional Facebook archive migration
- Communication, calls and business conversations
- Community standards and prohibited conduct
- Reporting, moderation and appeals
- Pages, organizations and staff authority
- Page continuity, succession and recovery
- News, independent curation and institutional status
- Discovery, recommendations and automated assistance
- Advertising, boosts and educational house notices
- Advertising funding, measurement and campaign changes
- Wallets and source-separated balances
- Gifts, creator entitlements and withdrawals
- Commerce, accepted orders and receiving goods
- Commerce disputes, refunds and payment finality
- Marriage introductions and sensitive connections
- Third-party services, integrations and links
- Security, privileged access and lawful requests
- Account lifecycle, service changes and availability
- Responsibility, complaints and dispute handling
- Integrated privacy provisions
1. Service, scope and interpretation
AmraEk.com, referred to in these Terms as AmraEk, is the name used for this service. The service is operated from Bangladesh for people in Bangladesh. This intended audience does not establish an automatic citizenship or location-verification claim for an individual member. The correspondence address is Mission Road, Dinajpur, 5200, Bangladesh. Contact the service through the AmraEk Help Center.
These Terms cover personal accounts, protected family experiences, profiles, posts, photographs, videos, Stories, messages, Pages, news surfaces, advertising tools, internal balances, gifts, eligible commerce and other AmraEk features described here. Each feature is governed by these Terms only when it is actually offered to the person using it. A description is not a promise that an unavailable integration, disabled payment service, experimental tool or proposed product will become available on a particular date. The interface must identify important availability and eligibility conditions before a person relies on the feature.
“You” means the person using a personal account or, where the context requires, the organization that person is authorized to represent. It does not make a child responsible for an adult's business obligations or make an employee personally guarantee every obligation of an organization. “We,” “us” and “our” refer to those responsible for operating the AmraEk.com service described here. “Page” means an organizational or public-facing presence with separately controlled authority. A Page identity does not replace the authenticated person responsible for an action behind it.
“Content” includes text, media, comments, reactions, messages, descriptions and other material submitted to the service. “Public” describes the chosen audience within the operation of a feature; it does not mean that copyright, privacy or personality rights disappear. “Private” means access is restricted according to the applicable feature and this document. It does not promise that a recipient cannot capture what they can see, that a valid legal obligation cannot require disclosure, or that every category uses end-to-end encryption.
An order, advertisement or other transaction may have a feature-specific quote, receipt, scope, deadline or policy version. That record governs the amounts and particular transaction the parties deliberately confirmed. General Terms must not silently change an already funded order's fees, revive an expired permission, or convert a free action into a paid action. Where a feature notice and these Terms appear inconsistent, we must explain the inconsistency and honor mandatory rights and properly confirmed transaction commitments; we cannot use ambiguous drafting to impose a surprise charge.
Headings and examples help navigation. Examples are illustrative unless they reproduce an actual agreed price or receipt. A reasonable operational limit on requests, file size, review workload or retention is not a finding that a member acted improperly. We distinguish technical rejection, a pending review and a final enforcement decision so that members can understand what happened and what can be corrected. Applicable mandatory law takes precedence over a conflicting contractual provision.
2. Acceptance, versions and changes
The final agreement will be offered before ordinary signup is completed. The member must be able to open it without losing their entered information, read it using normal browser zoom and accessibility tools, and make an affirmative choice to agree. A preselected checkbox, an obscured link, continued scrolling or an unrelated button must not be treated as the required signup assent. If the current terms cannot be retrieved or the submitted version no longer matches the published version, the interface must explain the issue and obtain the correct acceptance before completing a new registration.
The acceptance record may include the account, document version, document digest, time and proportionate technical evidence needed to demonstrate the choice. A digest identifies the accepted document; it does not authorize changes to its contents. The record must not falsely indicate that a member read every word, agreed to an unavailable document, or consented to optional processing merely by accepting the general agreement. Members should be able to find the current version and identify the version governing an important transaction or account acceptance.
Some actions require a further, specific decision. Examples include selecting a file to import, allowing a browser to use the microphone, confirming a wallet deduction, choosing an advertisement's budget, accepting a Page appointment, or giving guardian consent where required. General acceptance does not supply those decisions in advance. A refusal of optional tracking or marketing must not be disguised as rejection of the whole service when the requested activity can be provided without it.
We may propose changes to address actual product changes, security needs, legal requirements or operating arrangements. Material changes must be communicated with a clear description of what changes, the intended effective date and any action the member needs to take. A new processing purpose, expanded disclosure or materially different financial commitment must not be retroactively justified by a broad reservation of rights. Where renewed agreement or another lawful choice is required, we must obtain it before applying that change to the affected activity.
Urgent changes needed to prevent immediate harm or satisfy a binding obligation may take effect sooner than an ordinary notice period allows, but their scope must be no broader than necessary. We should explain the change when doing so is lawful and safe. An emergency security restriction does not entitle us to rewrite completed purchases, seize user content, or erase the evidence a person needs to contest an error.
If you decline a material change, we must explain the resulting feature or account options, including any available export, cancellation and settlement process. Existing liabilities and valid records may still require resolution. Silence should not be represented as a fresh affirmative consent where such consent is required. A local-language explanation may assist understanding, but the service must not hide a material condition in a language or format the relevant flow does not reasonably make accessible.
3. Eligibility, age and family access
The product's minimum age is seven. Children below seven are not eligible for an AmraEk account or family profile. Ages seven through thirteen use a separate, protected guardian-supervised experience where that experience is available and lawfully offered. Ordinary personal signup is available from the fourteenth birthday, subject to the remaining registration requirements. These are product eligibility boundaries, not a statement that the same age of legal capacity or parental consent applies in every country.
We ask for age information neutrally. A person must not be encouraged to select an older date simply because a younger date makes a feature unavailable. An initial date declaration is not reviewed identity evidence. A public birthday, private registration declaration, guardian relationship and independently reviewed age finding serve different purposes and must not be treated as interchangeable. If inconsistent information creates uncertainty, higher-risk features may remain restricted while an appropriate correction or review is completed.
The family experience uses a guardian relationship that must be reviewed through the available process. An adult sharing a device, phone number, surname or network address with a child is not enough to establish that authority. A guardian must supply accurate information and any evidence specifically required for the relationship, make the applicable informed choices, and avoid submitting unrelated documents. Where the governing law requires verifiable parental consent or another specific authorization, the relevant process must satisfy that requirement before the covered activity begins.
A family profile is not an ordinary adult account with some buttons hidden. Its permitted features, credentials, visibility and communications are separately limited. An adult handing a browser to a child must use the protected handoff instead of leaving the adult's personal session available. A guardian's supervision does not entitle the guardian to bypass confidential child-support safeguards, impersonate an independent reviewer or turn a child profile into an advertising audience. A child should receive an understandable explanation of which notes or activities the guardian can see.
Turning fourteen makes a person eligible to apply for the ordinary personal experience; it does not automatically convert a family credential into an unrestricted account. Any independence or migration route must establish the person and obtain the required registration choices. A birthday greeting describes only features that are actually available and must not announce that a payment, calling or other integration has launched when it remains disabled.
Different activities retain separate age thresholds. Ordinary free social access, eligible Spending balance top-ups, conversations, available calls and giving gifts may be permitted from fourteen, while creator cash-out requires adulthood and its additional checks. Marriage-related services have their own adult eligibility and cannot be accessed by using the general social minimum. Advertising targeting remains prohibited for people below eighteen under the product policy, including when a mutable profile field or an adult's choice would otherwise suggest permission.
Age-appropriate house educational notices in a child context are addressed in the advertising section. That narrow possibility is not permission to profile children or release their information to advertisers. Market-specific legal requirements and the child's protections remain applicable. A feature that cannot meet the required protections must remain unavailable in the affected circumstances rather than inviting a child to waive them.
4. Registration, provider login and account accuracy
You must provide the information reasonably required to create and secure your account accurately. Do not create an account using another person's phone, identity document or provider identity without authority, and do not invent evidence to satisfy a requirement. A chosen display name need not reveal more private identity information than the service requires, but it must not fraudulently impersonate another person or organization. We may distinguish a public display name from information privately reviewed for identity or financial purposes.
Phone registration requires control of the number through the supported verification process. A one-time code demonstrates access to that channel at that time; it does not prove legal ownership of a SIM, a person's age, a family relationship or permanent residence. For phone-based signup, the verified number must not already be registered to another AmraEk account. A provider outage, delayed text or failed verification is not evidence that a person is dishonest, and support must not ask for a reusable password or a live one-time code in a public conversation.
Where Google or Facebook signup is enabled, the provider authenticates its identity according to its own process. Provider login may help prefill permitted details or link an identity, but it does not automatically complete every AmraEk requirement. First signup through a server-verified Google or Facebook flow can be completed without a phone number or SMS code; the applicable age screening, required account information, device and account-integrity checks, and acceptance of the current published Terms still apply. Linking must be deliberate and protected against account takeover. A matching email address alone must not silently merge two accounts or transfer an existing account to whoever presents that address through another channel.
Subsequent login through a properly linked provider may use that link subject to current account restrictions. You should maintain an available recovery method, especially if a provider account or phone number may be lost. Disconnecting a provider must explain whether another working sign-in route remains. We must not claim a provider is ready merely because its name or icon appears in a design; integration availability depends on actual configuration and the provider's requirements.
The service limits unverified registrations in a recognized browser context to four under the current product rule. This is a browser-recognition control, not a guarantee that a physical handset can never host another account. The second and later registrations in that context may have seventy-two hours from their own creation to submit the required complete identity evidence. Approved verification can free a slot; it does not authorize selling accounts or letting one verified adult front for unrelated identities.
A timely complete submission awaiting human review is different from a late, incomplete or rejected submission. Where the registration-assurance rule restricts outreach, the restriction concerns specified new friend requests and outgoing unaccepted personal message requests. It is not an automatic deletion policy and must not be described as cancelling established friendships or accepted conversations wholesale. Members must retain the appropriate paths to review their status, submit evidence, recover access, correct an error and sign out.
Self-service date-of-birth changes are limited to two in a server calendar month and six over the account lifetime. The interface must show the relevant remaining allowance and reset information. Repeating the same value must not spend an edit, while clearing and re-entering a date must not reset the limits. A rejected older-date request must not prematurely remove a recorded youth protection. Legitimate correction concerns should have a review route rather than forcing a person to create misleading replacement accounts.
5. Credentials, sessions and recovery
Choose a strong password if the account uses one, protect your phone and recovery channels, and avoid sharing a personal session with another person. AmraEk staff must not ask you to disclose your password, private passkey material or one-time verification code so that they can log in as you. A support representative can guide an approved recovery process without receiving the secret that grants your ordinary account access. Suspected compromise should be reported through the available security route promptly.
Saved-account features are a convenience for a browser you control. The current product limit is four saved sign-in identities, separately from the registration-assurance quota. Saving an account should be deliberate, and removing it from a device should retire the relevant saved access rather than delete the person's account. On a shared device, check the active identity before posting, sending a message, changing settings or confirming a payment. A Page actor and a personal account are different contexts even when displayed in the same application.
Sensitive operations may require recent authentication or a stronger verification step. Depending on the available method, a passkey can ask the device to perform user verification with a fingerprint, face unlock or device PIN. AmraEk should receive the cryptographic result, not a stored copy of the person's fingerprint or face. Device user verification must not be described as a guaranteed face-only check or as remote iris identification. If an optional secret phrase is offered, its purpose and protected handling must be explained without encouraging users to reveal it to support.
If a microphone is used for an optional phrase, the person must explicitly initiate that use. Audio must not be silently sent to a cloud speech service under a claim of local processing. A typed alternative should be provided when the supported design requires it or when speech capture is unavailable. Accessibility accommodations should protect account security without forcing a person to disclose unrelated medical information or bypassing the authentication safeguards for a privileged account.
Recovery seeks to restore the correct existing identity, not create a replacement identity with another person's authority. Evidence should be proportionate to the account and risk. We may pause sensitive changes while resolving a credible conflict, but we should explain the status and available next step where doing so is safe. A lost phone, failed login, inactive account or unaccepted invitation does not by itself establish that somebody else owns the account or its Pages.
When an account is switched, logged out, revoked or removed from a session, sensitive interface state and pending requests must not populate the next person's screen. A delayed response may describe work already accepted by the server; cancellation in a browser does not necessarily undo that work. Members should check a receipt or status before repeating an uncertain financial or publication request. The service must use appropriate transaction and retry controls so that a routine network retry is not treated as a new purchase.
We may revoke sessions reasonably suspected of compromise and notify the account through an appropriate available channel. Revocation should not disclose private session details to another household member or reveal whether a particular person's account exists to an unauthenticated caller. Neither secure design nor user care can guarantee that every device is free of malware; the response to a genuine incident should focus on containment, restoration and accurate explanation rather than blaming a user without evidence.
6. Identity review and verification labels
Some features require a human-reviewed identity or organizational-authority decision. The service must identify what is being checked, what evidence is needed, who may review it and what the resulting status means. Submitting a document, recording a video, paying an unrelated fee or completing phone verification is not the same as receiving approval. Review status must distinguish pending, approved, rejected, expired and resubmission-required states without implying a negative finding merely because a document reached its retention deadline.
Use only genuine documents and your own current capture where the process calls for live evidence. Do not submit another person's document, manipulated identity footage or an automated substitute for a required personal check. Conversely, the platform should not demand unrelated education, employment, family or residence records simply because they might be interesting. Evidence must be tied to the defined purpose and handled under the integrated privacy provisions, with private access and an appropriate retention rule.
A verification badge communicates the particular review it represents. It does not guarantee that every statement, sale, investment, relationship proposal or news report by that account is true. Identity approval is not a banking licence, professional qualification, background check, product-authenticity certificate or insurance policy. An organization may have a verified representative without being enlisted for the separate News program; a paid product, if ever offered, must not be sold as proof of trustworthiness or a right to higher organic reach.
Probashi verification, where offered, requires foreign phone-control evidence and reviewed live video matching an approved passport or national identity document under the applicable process. Phone control does not prove where someone lives or works. The badge must not expose private documents or turn them into location-sharing consent. A person may choose to disclose their location socially through separate controls, and a verification reviewer must not treat that optional choice as necessary proof when the policy does not require it.
Reviewers must be properly authorized, current in their role and independent of a conflict that makes their decision inappropriate. A person should not approve their own identity, guardian relationship, Page succession claim or financial dispute. Evidence access should be limited to the case and purpose requiring it, with attributable actions. Internal notes must not become a second uncontrolled repository of identity photographs, full document numbers or reusable credentials.
If a decision is adverse, we should give a meaningful reason and a correction or appeal route to the extent compatible with fraud prevention and third-party privacy. A useful explanation can identify an expired document, unclear capture, identity mismatch or unsupported evidence type without exposing detection details that would enable evasion. A member must not be required to agree that a machine is always correct before seeking human review.
Identity status can change if evidence expires, a previously approved identity is credibly disputed, or an account is compromised. Such a change may affect the feature that relied on it, but it must not create a fictional new financial debt or erase the record of a completed valid transaction. Relevant restrictions should be proportionate and separately explained. Before collecting raw identity evidence, we must state the applicable retention period and handling arrangements in the collection notice. An internal system setting does not replace that notice or justify indefinite retention.
7. Personal profiles and social relationships
You choose the profile information you publish through the available controls. Consider the audience before sharing contact details, family relationships, workplace information, religious views, precise whereabouts or other sensitive material. A field being available does not mean it is mandatory, accurate for every person or suitable for public disclosure. Where a field is needed privately for eligibility, the service should not expose it publicly merely because it has been collected.
Friend requests, follows, invitations and connections have different effects. Sending a request does not establish a friendship, and following someone does not give permission to enter their private messages or view their restricted posts. Receiving an invitation is not membership in a Page team. The interface should make the action and its current status understandable, including whether another person's acceptance is still needed. Do not use repeated requests to pressure someone who has declined or blocked contact.
Available acquaintance suggestions may use permitted information and choices described in the privacy provisions. A suggestion is not proof that two people know each other, have met, share a household or have endorsed one another. You must not infer a person's intimate relationship, religion, employment or identity from a recommendation. Optional contact-based discovery must not be disguised as an essential login step, and a member's address book must not become a public directory without an appropriate basis and notice.
Blocking, audience settings and messaging preferences apply according to the feature. A blocked person may still encounter material outside the service or through an independently authorized recipient, but that limitation does not justify weakening platform access checks. Users must not create replacement accounts, use a Page or recruit another person to evade a block or continue harassment. The service may investigate credible patterns of block evasion and restrict the abusive activity while considering mistaken-identity reports.
Profile privacy should remain in force when information appears through search, a direct link, a shared card or another internal feature. An opaque marriage-profile link, for example, does not make the underlying social profile public. A former Page staff member must not retain authority over a private personal profile merely because the two identities were once linked in a work context. Screenshots, notifications and previews should reveal only what the recipient is currently entitled to receive.
You are responsible for treating others' personal information with care. Do not publish private phone numbers, home addresses, identity documents, medical details or intimate material as retaliation, entertainment or pressure. A person publicly stating one fact about themselves does not authorize a complete dossier or uncontrolled republication of unrelated private information. Public-interest discussion may require context-sensitive assessment, but a claim of public interest is not a blanket exception for threats, stalking or identity theft.
AmraEk does not require a legitimate social graph to be destroyed because an account has been quiet. Inactivity and low engagement are not, by themselves, grounds to demand purchases, force invitations or automatically delete an ordinary account under the current policy. Abuse prevention, explicit deletion, security incidents and a lawful obligation are different matters and may require their own action. Members should still keep recovery information reasonably current so that dormant accounts can be accessed safely when needed.
8. Content ownership and permission to operate the service
You retain the rights you hold in your original content. Uploading material does not sell it to AmraEk, make the operator its author, or grant the owner a general right to exploit it outside the purposes described here. You must have the rights, permissions or other lawful basis necessary for your submission and its chosen use. Possessing a file, seeing it online, paying for a subscription or crediting its creator does not necessarily authorize republication, advertising use or adaptation.
To operate the service, you give AmraEk a nonexclusive permission to store, reproduce, transmit, display and technically process the submitted material for the audience and feature you choose. This includes creating suitable thumbnails, converting supported formats, delivering media efficiently, showing previews within permitted contexts, maintaining security and carrying out your sharing instructions. That permission is limited by the content's privacy controls, the applicable feature and necessary service operation; it is not a right to ignore a private audience.
Where a service provider processes content on our behalf, we may allow the processing necessary to provide that function under appropriate restrictions. This does not permit a provider to treat every private post as its own public advertising asset. We must distinguish service processing from a proposed separate commercial use. Using identifiable private content in an external promotional campaign, or allowing a third party to commercially license a member's work for unrelated purposes, requires an appropriate independent permission rather than reliance on this operational licence.
The licence continues for as long as reasonably necessary to provide the chosen feature and meet the retention obligations explained here. Removing material from active display ends ordinary prospective use for that display, subject to legitimate retained transaction, safety, legal and backup records. Copies that other authorized recipients independently made cannot always be recalled. A surviving record or another user's lawful copy does not authorize AmraEk to relaunch deleted content as fresh promotional material.
You must respect third-party copyright, trademarks, privacy and other rights. A quotation, criticism, parody, educational discussion or news report may have legal protection in its actual circumstances, but the platform cannot certify that every use falls within an exception. If you rely on an exception, keep the use proportionate to its purpose and consider the applicable jurisdiction. Do not remove attribution or rights information simply to conceal the source or make another creator's work appear to be yours.
For music and video, rights in a recording and in the underlying composition may be separate. A track licensed for listening is not necessarily licensed for synchronization with video or onward distribution. Any platform-provided library should identify the permitted uses and required attribution. A track's presence in an editor does not automatically authorize every advertiser, territory or external export. If a licence ends or a credible rights issue arises, we may need to restrict the relevant use while addressing lawful retained copies and available alternatives.
Feedback about the service may be used to improve it without creating an obligation to implement every suggestion. This does not transfer ownership of an unrelated confidential invention or turn a support attachment into public feedback. If you submit sensitive commercial material for a limited review, identify that purpose and use the appropriate private channel. We must not use a broad feedback provision to override a specific confidentiality commitment or a member's copyright in ordinary content.
9. Publishing, audiences, tags and sharing
Before publishing, choose the intended audience and review the content, attachments and active identity. A personal post, a Page post and a Story may have different controls and consequences. The final action must identify whether material will be public, restricted to a selected audience or kept private. Saving a draft or selecting a file does not authorize publication. A background upload can prepare media, but it must not silently convert a cancelled draft into a visible post.
Audience restrictions apply to the canonical item and relevant media delivery. A direct attachment address or copied internal identifier must not become a shortcut around current permission checks. When audience settings change, the service should apply the supported change consistently to later authorized access while explaining any unavoidable limits, such as copies a recipient already saved. Private content should not be inserted into public search, public previews or an advertising audience merely because a ranking system can technically inspect a database row.
Tagging mentions another person; it does not grant ownership of their identity or blanket publication consent. Available tag-review and timeline controls must determine whether a tag or tagged item appears in the relevant context. Rejecting a tag may remove that association without necessarily deleting the author's entire post. Where content itself violates privacy or safety rules, the affected person should use the reporting route as well, because tag removal alone may not address the underlying harm.
Sharing a permitted post should preserve attribution and the source's current audience boundaries. A built-in share is different from downloading and uploading someone else's media as a new work. If a source becomes unavailable, private or restricted, the service should not maintain a public copy through an ordinary share as though the source permission were unchanged. Members must not use quotes, cropped images or reposts to evade a lawful restriction or a person's clearly communicated refusal of abusive contact.
Comments, replies and reactions may be visible to the audience of the item on which they occur. A private account setting does not necessarily make a comment on a public Page private. The interface should explain important context when an action could reasonably be misunderstood. A reaction is not a verified factual endorsement, a promise to purchase or consent to be contacted commercially. Advertisers and other members must not manufacture those interpretations from an ordinary social interaction.
Editing must preserve any records the feature legitimately needs, including transaction evidence and business-message history. If a correction would materially change an advertised offer or funded order, the appropriate revised quote and fresh consent are required; editing a caption cannot rewrite the existing deal. A correction to an ordinary post should not falsely retain an earlier timestamp in a way that misleads readers about the change. We may preserve limited edit history for accountability where explained and justified.
Publication can fail because of connection loss, unsupported media, capacity limits or a safety check. A failure notice should distinguish an unsubmitted draft from material already accepted for processing. Keep your original files if you need an independent archive. AmraEk is a social platform, not a substitute for your sole backup of irreplaceable material. That advice does not remove our responsibility to handle committed content carefully, investigate credible loss reports or explain an actual incident accurately.
10. Photos, videos, editing and music
Upload only supported files you have authority to use. Media limits protect the service and other members from unsafe formats, excessive processing and unusable playback. The interface may specify file size, duration, dimensions, supported types or other relevant constraints before upload. A file extension or browser-reported duration is not conclusive evidence that a file meets those rules. The server may inspect the actual media, reject malformed content, or require a supported conversion without treating every rejection as misconduct.
For ordinary eligible personal and Page video, the current account-age allowance is up to thirty seconds before ninety days, up to sixty seconds from ninety through one hundred seventy-nine days, and up to two hundred forty seconds from one hundred eighty days. This is the age of the account, not the person's date of birth. The service should show the allowance that applies and the next eligibility point. Other operational limits may apply if clearly disclosed, but they must not silently replace the agreed account-age policy.
Authorized News publications follow a separate maximum of two hundred ten seconds under the institutional program. A self-selected Page category, a client-side field or a purchased badge cannot grant the News allowance. The server must confirm current authority and enlistment. A technical limit does not give permission to upload an infringing broadcast, private recording or harmful material, and a shorter video is not automatically eligible merely because it fits within the duration cap.
Available editing tools may allow trimming, filters, audio selection and control of original audio. Review the output before publishing, especially where cropping removes context or added sound changes the meaning of a scene. An edit must not falsely make a real person appear to say, endorse or do something in a materially deceptive way. Clearly identified parody, artistic expression and discussion require context-sensitive treatment, but must still respect privacy, consent and applicable safety rules.
When you add licensed music, follow the specific licence, attribution and scope shown for the track. Some uses may be restricted by territory, commercial purpose or type of distribution. You remain responsible for material you independently import into an editor. We must not describe a music collection as fully licensed without evidence covering the actual recording, composition and intended use. A platform permission does not override a separate restriction imposed by a destination to which you later export the video.
Processing may create alternative versions for playback, thumbnails and compatibility. We should preserve appropriate quality without promising that every device, network or source file will play identically. A low-resolution original cannot acquire genuine detail through a label claiming high definition. Accessibility features, including captions where available, should not intentionally alter a speaker's meaning. Machine-generated captions or translations should be reviewable where practical and must not be treated as authoritative transcripts in a dispute without checking the source.
Uploading a photograph of a child, identity document, accident, medical scene or intimate situation calls for particular care. The right to record an event does not always include the right to publish every identifiable person in it. Do not submit nonconsensual intimate imagery, exploitative child material or covert recordings used for abuse. Where reporting a serious matter requires evidence, use the restricted reporting process and disclose only what is needed rather than circulating the evidence publicly to attract attention.
11. Stories and Yearly Memories
Stories are intended as time-limited sharing. Under the ordinary feature, a newly published Story is visible for twenty-four hours unless removed sooner or restricted for another valid reason. Expiry from the Story surface is different from deletion of every operational record, a recipient's saved copy or a separately shared post. The interface must not imply that a Story is immune from screenshots, reports or the retention rules that apply to a relevant safety or legal case.
Choose the audience for each new Story. A prior audience choice may be offered as a convenience, but it must be understandable and changeable before publication. Sharing someone else's content into a Story must preserve the applicable rights and source restrictions. A Story reply is a separate communication governed by messaging permissions; viewing a Story does not invite unwanted private contact. Blocking and changed audience eligibility should be respected when the service evaluates access.
Viewer and reaction information is limited to the insights actually supported by the feature and applicable privacy controls. A displayed view should not imply that the person watched every second, understood the content or agreed with it. We should not fabricate viewers, reactions or completion counts to make an account seem popular. Where later insight or expiry-summary tools are unavailable, their appearance in a roadmap does not create a promise of a delivered private report.
Yearly Memories offers selected eligible material from the same month and day in earlier years. It may choose one of your own photographs for a year or an eligible own-post fallback rather than presenting a complete archive. There is no general ten-year cutoff in the intended selection rule. Absence of a result does not prove that no material existed that day, and the feature must not invent a historical event or backdate newly created content to fill a gap.
Imported material should use a supported original publication or upload date, not falsely describe the date of import as the date of the remembered event. Metadata can be incomplete or inaccurate, and a member should be able to understand that limitation. Memories does not certify that a camera timestamp, caption or account statement is historically correct. A remembered photograph may also contain people whose circumstances have changed; consider their privacy and the sensitivity of the event before sharing it again.
Opening Memories does not automatically publish a reminder or notification to other people. Sharing a memory is a deliberate new post or Story with a selected audience while retaining appropriate original-date context. The new item has its own current publication and expiry behavior. A private original must not become public merely because it was selected as a memory, and an expired or deleted source should not be revived through a cached suggestion that ignores current access restrictions.
The feature should avoid forcing a person to revisit distressing material. Where controls to dismiss, hide or manage memories are available, they should be discoverable and effective within their stated scope. A user who needs help removing harmful content should not have to republish it in a complaint. The service may preserve a limited report record under the privacy provisions while stopping ordinary redisplay, without turning that retention into a public memorial or an unwanted account activity signal.
12. Optional Facebook archive migration
The archive import is an optional migration convenience for your own exported material. Facebook login and an archive upload are different actions. Signing in with Facebook does not authorize AmraEk to collect your lifetime history, access every private record or import content automatically. You must deliberately obtain the supported archive through the source service, choose the file yourself and confirm the upload through your authenticated AmraEk account. Declining import does not prevent ordinary use of an otherwise eligible account.
The supported flow imports eligible text posts and embedded photographs from a supported JSON ZIP archive, subject to the displayed limits and processing rules. It is not a whole-profile migration. It does not automatically replace your AmraEk name, avatar, cover, date of birth, contact details or other profile fields, and it does not promise to reproduce every album, reaction, friend connection, comment, audience or source-platform feature. A source archive may contain categories that the importer intentionally ignores.
Videos are excluded from this flow and cannot be enabled by changing a client flag. When a source item includes a video, the importer should record that the video was skipped instead of presenting it as a generic processing failure. An explicit caption associated with a source post may remain as plain text, but the title of a video alone should not fabricate a new text post. The status should distinguish imported items, skipped videos, retained captions and actual errors so that members understand the outcome.
Imported eligible posts and photographs begin private. Original supported publication dates are preserved where available. Import does not make the platform responsible for establishing the truth of those dates, and it does not turn a private import into a public distribution licence. A later decision to publish imported material remains subject to current audience choices, rights, safety checks and content rules. Photographs in an archive may include other people or third-party works; export availability alone does not establish your permission to republish them.
For security, the importer may reject unsafe paths, unsupported files, malformed JSON, excessive expansion, suspicious archives or media that fails bounded decoding. It does not need to fetch external URLs or follow arbitrary archive references to complete the supported task. An archive referencing a remote photograph is not permission to access that location using another person's credentials. Password-protected or incompatible archives may need to be exported again in a supported format rather than asking the member to disclose a third-party password.
Limits on archive size, number of items, expanded bytes and concurrent jobs must be shown accurately when relevant. A queued job is not a completed import. You may inspect your own recent statuses, and another member must not be able to retrieve those statuses or archive locations by guessing an identifier. Processing can stop or partially succeed; the resulting counts should reflect committed work. An uncertain network response should lead to checking status before submitting the same file again.
Deduplication helps avoid importing the same source item or media repeatedly, but it is not a universal historical reconciliation service. Supported repair of an old private item must not silently add photographs to an already public item. Raw uploaded archives are removed after completion or terminal failure under the supported workflow, while successfully committed posts and photos follow their own lifecycle. Keep an independent copy of your source export if you need a complete personal archive or wish to verify what the importer did not support.
Optional profile review and Facebook friend suggestions — prepared, not activated
A separate optional Facebook data flow is prepared for a person who has deliberately linked their own Facebook identity. It remains unavailable until the required application setup and Meta permissions are approved and enabled. Ordinary Facebook login requests its basic profile and optional email permissions; an unavailable or declined email does not prevent login. Where the optional feature is available and you choose it, we may read the name, birthday, current city, hometown and app-using friend information that Facebook actually permits. Missing values and partial birth dates are not invented; a city or hometown is not a complete home address. You can review and choose the fields to retain privately, and separately choose whether to use the permitted name or current city on your AmraEk profile. This does not replace your age declaration, identity evidence or existing location-visibility choice.
Friend matching uses server-verified Facebook identifiers scoped to this same application and a provider-reported friendship, never name, photograph, email or birthday similarity. Facebook does not provide every Facebook friend: the relevant friends must also use and authorize the application. Discoverability is an explicit choice. The result is a suggestion list only. Login, preview, saving profile details and viewing that list send no friend request and create no friendship. You choose whether to send a normal AmraEk friend request; ordinary privacy, blocking, account eligibility, request limits and recipient acceptance still apply. A previous provider response cannot guarantee that a Facebook relationship has not changed since it was read.
Selected private profile details and temporary matching evidence are encrypted. Matching evidence is usable for five minutes and is then unavailable for suggestions; a bounded scheduled cleanup clears expired copies. Disabling this feature removes its retained profile copy and matching evidence and invalidates pending imports. It does not undo profile edits you deliberately copied, requests you deliberately sent or friendships accepted through the ordinary flow. These prepared features are not a claim of current public availability.
13. Communication, calls and business conversations
Personal messaging is governed by the participants' current contact permissions, blocking, account eligibility and the state of the conversation. A message request is not an accepted conversation, and a recipient may decline it or choose not to respond. Do not send threats, sexual harassment, scams, repetitive solicitation or attempts to pressure a recipient into leaving the platform. A sender's intention to be friendly does not override the recipient's clear refusal or an applicable contact restriction.
Message previews, notifications and attachment delivery should respect the context in which they appear. A shared-device notification can reveal information even when the full conversation requires login, so use the available preview and device settings carefully. The platform must not expose a private message through an unrelated profile, Page review or advertising report. Reporting a message authorizes the defined review process, not publication of the whole conversation to the reporter's followers.
The ordinary deletion and restricted-preservation policy for personal messages is stated in the integrated privacy section. A person should check whether an action affects their own view, both participants' permitted views or another supported state before confirming it. No interface should imply a recall guarantee where another participant may already possess a copy. The separate rules for business Page conversations below must be visible before a member relies on deletion behavior that those conversations do not offer.
Business Page conversation history is not user-deletable. Customers, Page owners and Page staff cannot delete a business message, remove it only from their own view, unsend it or delete the whole conversation through the ordinary Page inbox. The purpose is to preserve the record of business communications and relevant transactions. Editing, account cleanup or Page lifecycle actions must not be used as hidden ways to erase the original history. Statutory privacy requests and specific legally required restrictions remain subject to human review under the integrated privacy provisions.
A business inbox may be accessible to current Page staff with an explicit messaging permission. When contacting a business, do not assume that only one individual will read the message. The Page should manage its staff responsibly and avoid requesting identity documents or other sensitive data through an ordinary sales conversation unless necessary and appropriately protected. A staff member must not export customer conversations for an unrelated venture or retain access after the role has ended.
Available audio or video calling depends on account eligibility, device permission, network conditions and configured infrastructure. A call button does not guarantee that the other person is reachable or that a provider has been activated. We must not describe unsupported relay capacity, unlimited live calling or a disabled video provider as available. Calls are not an emergency service. If immediate assistance is needed, use the appropriate local emergency or trusted support channel rather than relying on an AmraEk call being answered.
A WhatsApp destination opens an external service under the member's control. Suggested starter text is not sent automatically on the member's behalf. A click on that destination is not proof that a message was sent, received or answered. AmraEk does not control the external service's deletion, storage or recipient practices. Likewise, a business-message retention rule inside AmraEk does not impose the same rule on a separate conversation conducted through another provider.
14. Community standards and prohibited conduct
AmraEk supports ordinary social expression, disagreement, creativity, business communication and discussion of matters of public interest. Members must use those opportunities without threatening others, exploiting children, stealing identities or manipulating the service. A disagreement, unpopular view, criticism of the operator or report of a product defect is not by itself abuse. Context matters, and enforcement should distinguish legitimate debate from targeted conduct that prevents others from participating safely.
Do not post or transmit credible threats, instructions intended to facilitate imminent violence, extortion, stalking, nonconsensual intimate imagery, sexual exploitation of children or material that recruits people into violent abuse. Do not organize harassment by directing others to attack a person, expose their private information or overwhelm their contact channels. Where content documents harm for reporting, education or public-interest discussion, use appropriate context and avoid unnecessary exposure of victims or graphic detail.
Do not impersonate another person, falsely represent institutional authority or create deceptive endorsements. Clearly identified parody or fictional characters must not be presented as an actual person privately communicating with members. A badge, Page name or generated portrait must not imply government, publisher, professional or platform approval that has not been granted. If a synthetic character or AI-assisted account is offered, its fictional or automated nature must be clear enough for an ordinary member to understand.
Do not use the service for fraud, phishing, malware distribution, credential theft, unauthorized access, money laundering or prohibited commerce. A message that asks for a password, one-time code, advance release fee or remote device access may be part of a scam even when it uses a familiar logo. Report suspicious conduct through the appropriate route. Members who discover a vulnerability should avoid accessing unrelated private records and use a responsible reporting channel rather than exploiting the issue to demonstrate impact at scale.
Do not manufacture engagement, buy deceptive followers, operate coordinated spam, or use repeated accounts to evade a restriction. An advertiser may deliberately create multiple eligible campaigns for the same post, but that does not authorize fake results, automated harassment or attempts to collect a budget refund through fabricated traffic. Technical experimentation must not overwhelm the service, bypass rate limits or consume another person's paid resources without authorization.
Do not collect personal information from the service in ways that defeat visibility choices or enable stalking, discrimination or unwanted bulk contact. Public access is not unlimited permission to scrape a person's social history into a sensitive profile. Do not infer protected or intimate characteristics for exploitative targeting from names, photographs, private interactions or group membership. Organizations using AmraEk must ensure their staff and contractors follow these restrictions when acting through the organization.
Content that promotes self-harm, dangerous challenges or serious health deception may require a protective response, especially when aimed at children or people in distress. Supportive discussion of lived experience should not be treated the same as encouragement to cause harm. The platform is not a medical provider and must not present automated suggestions as diagnosis or crisis care. Where a report indicates a serious immediate risk, human review should consider the least intrusive effective action and the lawful emergency-disclosure rules.
15. Reporting, moderation and appeals
Use the reporting tools to identify content or conduct you reasonably believe violates these Terms, another person's rights or applicable law. Provide enough context to help review the issue, but avoid uploading an entire identity archive or private conversation when a narrower excerpt is sufficient. A report must not be knowingly false or used to retaliate against criticism. Good-faith mistakes should be distinguished from deliberate abuse of the process.
We may use automated checks to prioritize or restrict suspected harmful activity, supported by human review where appropriate. A classifier's score is not a legal judgment or proof of intent. Important decisions should consider context, available evidence and the risk of error. The service must not describe a deterministic rule or untested model as a reliable fact-checking system, and staff should not accept a generated explanation as if it were evidence independent of the original material.
Responses may include a request for clarification, a warning, reduced availability of a specific item, removal, a contact restriction, a feature suspension or an account restriction. We should choose a response proportionate to the seriousness, repetition, immediacy and available evidence of the conduct. Where practical, address the offending action rather than unnecessarily disabling unrelated lawful activity. Severe or repeated abuse may justify stronger action even if each isolated event appears minor.
Affected members should receive a useful explanation of the decision and an available appeal route, unless disclosure would create a serious safety risk, expose another person's private information or violate a legal restriction. A notice can explain the rule and relevant content without revealing a reporter's identity or sensitive anti-abuse techniques. A vague reference to “security” should not be used indefinitely to avoid addressing a genuine mistaken-account or mistaken-content complaint.
An appeal should be reviewed with attention to the grounds raised, including mistaken identity, missing context, inaccurate translation, compromised accounts and procedural error. Where independence is required for a sensitive matter, the original decision maker should not be the sole reviewer of their own conduct. Restoring content or access after an error should correct the relevant status and records; it should not create a false history implying that the member admitted wrongdoing.
Moderators and administrators must have current, scoped authority. A platform role does not entitle every staff member to browse all private conversations, identity evidence or financial records. Report-related access should be limited to the material needed for the report and logged appropriately. Staff must not use review tools to investigate a personal acquaintance, retaliate against criticism or satisfy curiosity. An allegation involving staff requires a route that avoids assigning the case to the implicated person.
No review-time guarantee is made merely because a case is listed as pending. We should communicate material delays and preserve relevant evidence proportionately. A person seeking immediate protection should use available blocking and safety controls while review proceeds. Taking a protective step does not waive an appeal. For commerce and institutional decisions, the more specific notice, response and independent-review requirements in the relevant sections also apply.
16. Pages, organizations and staff authority
A Page has one current primary owner. Founder attribution records who originally created it; attribution alone does not preserve current authority after a valid transfer. The owner may delegate supported tasks to identified staff, including publishing, inbox work, Page maintenance, moderation and advertisement management. A broad role name is not an unlimited grant. Every protected action depends on the current Page, actual saved permissions and any applicable work-access conditions.
Only the current primary owner may exercise the reserved ownership powers exposed by the service, such as changing staff authority, nominating successors or making a supported ownership disposition. An administrator of one Page has no authority over another. Staff must use their own approved access rather than sharing the owner's personal password or token. Work credentials, where available, are limited to their stated Page tasks and do not unlock the owner's private messages, personal wallet or unrelated accounts.
An invitation must identify its Page and intended permissions. It does not grant authority until properly accepted, and it may expire or be revoked. A removed or demoted inviter cannot leave behind an unrestricted route to create new administrators. Members should review the actual permission choice before accepting work. Page owners remain responsible for choosing suitable staff and ending access when duties change; the platform must still enforce a revocation on protected requests rather than relying only on hidden interface buttons.
Work-hour or office-network restrictions must identify the relevant timezone and enforceable conditions. A network address is not proof of physical office presence or personal identity. Staff should not circumvent a legitimate work policy by using another person's credentials. Conversely, an employer must not describe Page work access as a right to inspect an employee's unrelated personal activity. Removal from a team ends the granted work authority without transferring the person's account or deleting the Page's preserved business records.
Pages must accurately describe the organization, project, community or independent discussion they represent. Do not imply official publisher, government, company or professional status without authority. A community Page can discuss an institution while clearly identifying its independence. Page creation and ordinary eligible organic content remain free under the current core policy; purchasing advertisements is optional distribution and does not buy ownership legitimacy, institutional enlistment or a guarantee of organic reach.
17. Page continuity, succession and recovery
A Page must not be transferred simply because its owner is inactive or temporarily cannot log in. Ordinary account recovery is the first route for forgotten credentials or lost devices. Where a supported succession process exists, the owner may nominate up to three eligible people in an order and each nominee must accept. Being the earliest invited staff member, sharing a surname or claiming to be a relative does not automatically create succession rights.
A succession claim requires the appropriate independent assessment of death or permanent account loss and the claimant's Page authority. A separate reviewer must approve the waiting stage. The ordinary approved waiting period is fourteen full days, measured as three hundred thirty-six hours. The owner and relevant participants receive the available private notice and a way to contest. A claim alone does not seize the Page, and a credible owner recovery or unresolved objection must be addressed before finalization.
Finalization rechecks current ownership, nominee acceptance, eligibility, review and elapsed time. Old staff grants, pending invitations and nominations are handled according to the supported transfer process rather than silently becoming the new owner's chosen team. A Page transfer moves Page authority only. It does not grant the former owner's personal login, personal conversations, wallet, identity evidence or unrelated Pages, and it does not silently transfer separate financial entitlements or regulated payment authority.
Where no suitable nominee exists, a recovery case can collect relevant evidence without promising automatic takeover. An appeal after transfer must be reviewed independently; a favorable finding is not itself an undocumented power to seize the Page back. Restoration requires the applicable authorized workflow. Personal-account deletion and memorialization must preserve Page-owned records according to their actual ownership and retention rules, while avoiding unnecessary continued display of a deleted person's private details.
18. News, independent curation and institutional status
OurNews is a distribution surface for currently verified and explicitly enlisted eligible news organizations in their approved country. Review concerns organizational identity, representative authority and enlistment; it is not a declaration that every story is true. Payment, popularity, a Page category or a verification badge alone does not establish News authorization. A change in organizational authority or country eligibility may require review before further institutional publication.
An authorized publication may appear as one canonical item across OurNews, ordinary Videos and Feed, subject to current audience, safety and technical rules. This avoids requiring duplicate uploads solely to reach those surfaces. Inclusion does not guarantee a particular ranking, audience size, political endorsement or revenue. Independent news organizations remain responsible for their reporting, corrections, rights and applicable professional obligations.
An independent curation Page must clearly identify its own role. A name such as “AmraEk reading circle” followed by a publisher's name should be accompanied by an explicit statement that it is independent discussion or summary and not the publisher's official account. A citation or link does not authorize copying a complete article, broadcast, photograph or logo. Summaries should distinguish the source's report from the curator's interpretation and link to the original where appropriate.
News discussion remains subject to privacy, threats, copyright and other applicable rules. Retraction or removal of harmful material is separate from deciding political viewpoints or guaranteeing factual truth. Members can report a rights or safety concern without requiring the platform to claim universal fact-checking authority. Unavailable external scraping, automated ingestion or retention arrangements must not be inferred from a News label. A new expiry or archive rule would require a clear notice and verified implementation before publishers rely on it.
19. Discovery, recommendations and automated assistance
Feeds and discovery features may arrange eligible content using permitted interactions, selected preferences, recency, language and other disclosed signals. Ranking is an estimate of relevance, not an entitlement to a fixed number of impressions. An account does not need to purchase advertisements merely to retain ordinary organic eligibility. We may adjust ranking to reduce spam and improve usefulness, while honoring audience restrictions and avoiding misleading claims that a payment purchases trust.
You may use available controls to hide an item, dismiss a suggestion or change preferences. The system should interpret those actions for their stated purpose, not treat every dismissal as evidence of secret interest. A recommendation does not establish a person's identity, relationship, intention or endorsement. Sensitive inferences must not be derived from private messages or identity evidence to create commercial audiences.
Automated assistance can help check media, identify likely spam, prioritize reports or suggest advertisement settings. It cannot authorize a charge, grant a staff role, verify a legal identity or expand a hard audience restriction without the required underlying process. An AI-generated answer may be inaccurate or incomplete. The service must distinguish a suggestion from an executed action and should let the member inspect consequential proposed changes before confirming them.
Free core membership does not include an unlimited general-purpose AI assistant or unlimited generation entitlement. Any optional paid or separately funded AI feature must state its actual availability, input handling and charge before use. Fictional AI characters, if introduced, must be clearly identified as fictional or automated. They must not impersonate a real person, pretend to be a human professional or manipulate a child into sharing secrets, spending money or abandoning trusted support.
20. Advertising, boosts and educational house notices
Paid advertising and boosts provide additional distribution for eligible content. Advertising must be recognizable as promotional material. An advertiser must have authority over the Page or content used, rights to the creative and a truthful basis for material claims. An approval means the advertisement passed the applicable platform review; it is not a certification that the product is genuine, effective, lawful in every location or suitable for every viewer.
Audience choices operate within privacy, consent, geographic, age, exclusion and content-safety boundaries. No person below eighteen may be targeted by advertising under the current product policy. Uncertain age is not permission to assume adulthood. Advertisers must not circumvent youth restrictions through misleading categories, proxy audiences, private identity data or a Page name intended to attract children. Sensitive traits, private conversations and identity documents must not become commercial targeting signals.
Where audience expansion is deliberately enabled, selected interests can guide discovery beyond an exact interest match. Expansion does not increase the confirmed total budget or override an explicit country, radius, exclusion, consent or youth restriction. The service must describe what the control actually does without claiming that an untested heuristic is equivalent to another platform's proprietary model or guarantees better results.
The owner may operate clearly labelled house promotions and, if the separately implemented billing exemption is available, receive distribution without an ordinary wallet debit. That changes who funds the placement; it does not remove review, eligibility or privacy rules. No free boost can authorize external provider spending that has not been approved, charge another member's balance or disguise the operator's own advertisement as an independent recommendation.
Age-appropriate educational house notices may be shown in an eligible child context, including a context for a ten-year-old, only when the applicable age-entry and guardian requirements are met. These notices must not involve behavioral profiling, cross-service tracking or disclosure of children's information to advertisers. They should be distinguishable from ordinary content and suitable for the child's understanding. Calling material educational does not excuse deceptive claims, harmful subjects, commercial pressure or a legal requirement that still applies in that market.
21. Advertising funding, measurement and campaign changes
Before confirming a campaign, the advertiser must see its total budget, funding source, schedule, objective and any actual reserve or service allocation that affects the amount available for delivery. A proposed optimization allocation is not permission to spend more than the confirmed total. Paid campaigns are prepaid under the current policy. Reserved funds, spent funds and unused funds are different states and must be represented accurately in the account's records.
A deliberate new campaign can reuse an eligible post with a different audience, objective, country or schedule. Each campaign retains its own identity and accounting. Replaying an identical funding request because a connection failed must not create another debit. Where a result is uncertain, the service should reconcile the original request before offering a fresh charge. Cancelling delivery does not necessarily undo delivery already provided, but unused value must receive the treatment described in the confirmed funding terms.
Schedules should use the target country's relevant timezone, with an explicit choice where the country has several timezones or the audience is worldwide. A saved schedule represents actual delivery instants. Changing a display preference must not move those instants. Daylight-saving transitions and repeated or nonexistent local times must be explained instead of guessed. Reporting and billing boundaries may differ and should be labelled when that distinction affects a report.
Metrics must describe observed events. A qualified video view uses three seconds of actual visible playback under the current measurement rule; seeking to a timestamp is not a second view. A click on WhatsApp is not a confirmed conversation, and a message goal is not a guaranteed sale. Estimates, attributed conversions and deduplicated outcomes should be distinguished where available. Slow acknowledgement must not justify fabricated watch time, while invalid or duplicated events may be excluded with a reasonable explanation.
An advertisement may be rejected, paused or restricted for a stated review reason. The advertiser should have an appropriate route to edit, resubmit or appeal. Approval, funding and delivery start are separate events; a review notice must not falsely imply all three occurred. We do not guarantee review time, profit, follower growth or a specific return on investment. A later edit that materially changes creative, destination or audience may require fresh review or confirmation without silently rewriting the original financial record.
22. Wallets and source-separated balances
AmraEk may offer separate balances for purchased spending value, promotional credit, earned gift entitlements and other specifically supported purposes. The interface displays purchased spending value as Spending balance and eligible earnings as Earned money, in Bangladeshi taka. They are not interchangeable merely because the interface displays them near one another. A balance must retain the source and restrictions that justify it. Purchased spending value is closed-loop platform spending credit, not a deposit account, investment, transferable cash substitute or a promise of direct cash-out.
A confirmed ৳1 of Spending balance provides ৳1 of supported platform spending value. The confirmation screen must show the actual credited amount, payable amount and supported provider before a top-up. Any applicable tax or provider charge must be explained rather than silently changing the credited value. A listed provider is not available until its production integration is actually enabled. No user should be invited to send money to an unverified personal destination to activate a disabled payment option.
Purchasing credit does not create creator earnings. Promotional value must not be represented as cash-backed earned value unless an actual funding rule supports that representation. There is no general user-to-user cash-transfer facility merely because one member can give a platform gift to another. Currency labels, denominations and converted displays should not conceal the source of the underlying entitlement or imply that every balance can fund every service.
Where a supported service consumes part of ৳1, the unconsumed fraction is retained in its source-linked frozen remainder rather than discarded. Restoring that remainder to a whole spendable ৳1 requires an explicit confirmation of the exact deficit from the permitted same-account wallet source. A recharge alone does not authorize that deduction. Restoration must not create earned value or make purchased value withdrawable. The interface should show spent value, frozen remainder and restoration cost distinctly.
Purchased spending value and creator earnings do not expire merely because an account is inactive under the current policy. Fraud review, a valid refund, chargeback or supported source correction may affect a particular balance and must be documented. An accounting restriction is not a licence to confiscate unrelated funds. Report duplicate charges, unauthorized transactions, failed services or platform errors promptly; applicable legal and provider refund rights remain available even when a general purchase is normally nonrefundable.
23. Gifts, creator entitlements and withdrawals
Eligible members may give the gifts actually offered by the service. A new Rose costs ৳2 and a new Medal costs ৳5 under the current product rule, without an additional new-gift fee. The recipient's Earned money entitlement is sixty percent of that gift's face price: ৳1.20 for the Rose and ৳3 for the Medal. The platform's gross allocation is forty percent. Provider costs must not silently reduce the stated entitlement or create unfunded value.
Forwarding a previously received gift is different from buying a new one. It moves the supported remaining entitlement and maturity, removes the sender's entitlement and does not apply the sixty-forty allocation again. The separately confirmed forwarding charge is ৳1 from Spending balance under the existing rule, with only the supported collateral or recharge alternatives. The confirmation must explain the actual source and outcome. A decorative gift image is not a new financial entitlement unless the underlying transaction establishes one.
Receiving an entitlement does not mean cash-out is currently available. The launch gate for real withdrawals remains separate from gift accrual and interface balances. Where cash-out is activated, the member must satisfy the applicable identity, adulthood, professional-mode, account-age, follower, maturity, review and funding conditions. The current policy includes adulthood, at least thirty days of account age and two hundred followers; qualified views are not an alternative to that follower condition. Monetization eligibility cannot simply be bought.
A withdrawal quote must show the eligible amount, verified destination, applicable disclosed fee or tax, and expected net result. The already allocated creator share must not suffer a second forty-percent deduction. A pending request, provider acknowledgement or successful HTTP response is not proof that the beneficiary has been credited. Unknown outcomes require reconciliation before retrying or releasing a hold. Settlement adjustments must remain linked to the original funding, refund or chargeback and be explained through an auditable record.
No guaranteed payment per view, general advertising revenue share or unlimited earnings opportunity arises from these Terms. Creators remain responsible for accurate tax information and obligations that actually apply to them, while the operator remains responsible for its own reporting and withholding duties. Actual payment channels and applicable requirements must be established before real withdrawals are offered. These Terms do not by themselves activate a withdrawal service or replace provider onboarding and lawful financial operation.
24. Commerce, accepted orders and receiving goods
Commerce features connect an eligible buyer and seller around a defined order. Unless a specific offer expressly identifies AmraEk as the seller, the merchant supplies the goods or services and is responsible for accurate descriptions, lawful supply, stock, condition and promised delivery. The platform's supported payment and dispute tools do not certify product authenticity or make every merchant statement an AmraEk guarantee.
Before funding, both parties must acknowledge the actual immutable quote: goods or delivery scope, protected principal, their own service fee, applicable policy version and receiving guidance. A delivery-only payment protects the funded delivery amount, not an unfunded goods price mentioned elsewhere. A changed order requires a new revision and the required fresh acknowledgements. Editing a chat or listing cannot revise a funded quote in place. Historical orders retain the terms they actually accepted.
Only fees disclosed in the current quote and separately authorized where required may be charged. These Terms do not introduce a new rate or revive a superseded pricing schedule. Legal and provider approval of the proposed protected-payment operation remains a launch condition, including the classification of any buyer fee. Calling a charge a service fee rather than escrow does not by itself resolve a legal restriction. No payment option should be treated as live until those requirements are satisfied.
Shipment evidence may include a safe tracking link or a private receipt. Submission is different from independent handover approval and verified delivery. A link alone does not prove that goods were sent, and the platform need not automatically fetch an arbitrary external address. Corrections should append to the record instead of erasing original evidence. Both parties should retain the actual order, messages and delivery records needed to explain a problem.
Receiving guidance may ask for a continuous original recording from the intact labelled parcel through opening and inspection, with courier-assisted opening where that service exists. For cosmetics, preserve the product's original seal while checking the outer delivery package. Missing video, refused inspection or a broken seal does not automatically defeat a valid complaint about wrong, expired or defective goods. Live or perishable goods need specific condition, packaging, timing, handling and arrival-evidence terms separately accepted by both parties before funding; a proposed condition is not consent.
25. Commerce disputes, refunds and payment finality
Report a problem through the order's supported route and describe the actual issue. A complaint can pause the relevant release while the case is assessed; it does not automatically prove either party's account. Parties may resolve a problem in their retained business conversation without an extra solution fee. The platform must distinguish negotiation, an evidence request, a formal merits decision and an actual refund or payout.
For the supported formal process, the respondent has five calendar days, or one hundred twenty hours, from recorded notice availability to provide a case response. The displayed server deadline governs; a retry must not restart it, and availability must not be falsely described as a read receipt. A meaningful response prevents treating the person as silent. After the deadline, nonresponse permits independent review of the available evidence, not automatic complainant victory or fictional consent to a new charge.
Any conditional solution fee requires the actual parties' matching authority, the applicable quote or case version, the disclosed basis and exact amount. It is not imposed merely because somebody filed a complaint. Eligible formal awards and audited waivers must be recorded accurately, without a second charge on retry. Unsupported partial outcomes must not be converted into a full winner decision simply to fit the software. A reviewer must be independent of the buyer, seller and conflicting operational roles.
Where applicable law or the supported mandatory-refund classification requires a full refund, principal and the buyer's applicable service fee must not be reduced by a solution charge. Seller failure, nondelivery and platform error must be assessed through the correct path rather than mislabeled as optional paid mediation. An internal seventy-two-hour inspection window does not extinguish statutory complaint rights. The absence of preferred evidence must be assessed alongside other reliable evidence instead of operating as an automatic waiver.
Refunds return through the actual supported original sources and retain links to the order and decision. An internal credit does not prove an external bank or mobile-financial-service transfer has completed. Merchant payables, personal earned balances and a proposed Page wallet remain distinct. A protected payment is not an unlimited insurance policy for off-platform transfers, unfunded promises or losses unrelated to the accepted scope, but those limits must not be used to deny a right that mandatory law preserves.
26. Marriage introductions and sensitive connections
Marriage-related features are optional and subject to adult eligibility, current identity and the additional conditions shown for the service. Ordinary social eligibility from fourteen does not permit access to marriage introductions. A registration may be managed by an authorized representative only where the feature supports that role and makes it clear. The representative must not invent the candidate's consent or imply that the managing account belongs personally to the candidate.
Interest, mutual acceptance, payment and contact sharing are separate decisions. Any applicable charge must be shown before confirmation; this agreement creates no new marriage-service price. A paid connection does not guarantee compatibility, marriage, continued communication or a favorable response. Declining or cancelling follows the supported release and refund rules, and a person must not be pressured to continue a relationship because money has been spent.
Accepted internal chat does not automatically reveal the other person's social identity or phone number. Sharing your own social-profile link is voluntary and directional. The other person must separately choose whether to share theirs. An opaque link remains restricted to the intended eligible recipient and the current connection, and opening it must still respect social-profile privacy and blocking. Forwarding the link does not authorize a third person to access the profile.
Treat photographs, religion, family details and relationship information with particular care. Do not harvest profiles, expose rejected applicants, publish private conversations or use a sensitive introduction as advertising data. Identity review can reduce some risks but is not a background check or guarantee of personal conduct. Arrange any offline meeting with appropriate care, and report coercion, financial scams or threats without needing to continue contact with the person concerned.
27. Third-party services, integrations and links
AmraEk can depend on external services for hosting, verification, payment, communications and other functions. Their actual availability and terms may affect a feature. We must distinguish a configured working integration from a planned provider, demonstration or disabled option. A provider's branding on a screen does not by itself mean that the provider has approved AmraEk's business model, guarantees a transaction or accepts responsibility for all user content.
When you deliberately leave AmraEk through a link, the destination may collect information under its own policies. Check the destination before providing credentials, identity evidence or payment details. A link in a member's post is not an operator endorsement. We may restrict malicious or deceptive links, but cannot promise that every destination is safe or unchanged after it was first shared. Report a suspicious redirect rather than entering additional information to investigate it yourself.
Connecting an optional integration authorizes only the stated scope. You can withdraw the connection through the supported process, subject to any limited records needed for prior actions or security. Removing a connection does not necessarily recall information you already sent to the external service. We must not use an integration's technical access to collect unrelated records, send messages on your behalf without instruction or continue background transfers after the relevant permission has ended.
If an external outage prevents a transaction, we should show the known state and avoid claiming completion without evidence. Members should not have to guess whether to pay again. Provider changes that materially affect privacy, price or service commitments need appropriate notice and choices. The existence of a third party does not eliminate AmraEk's responsibility for its own selection, instructions, access control and handling of information within its control.
28. Security, privileged access and lawful requests
The owner account may hold extensive administrative powers for operating the service, appointing authorized staff and reviewing serious security matters. Those powers are not ownership of every member's identity or private life. A privileged “Mighty ID” or similar label does not authorize impersonation, sending a message as another member, obtaining readable passwords, retrieving private authentication keys or bypassing the restrictions that protect private information.
Sensitive owner access must use the required stronger authentication, a recorded purpose, appropriate scope and an attributable audit. A security investigation should begin with the least intrusive information adequate for the task. Read-only review of necessary active records may be permitted through the controlled process; ordinary curiosity or an unrelated commercial purpose is not a security investigation. Staff generally use report-scoped access rather than a universal inbox browser. Restricted deleted-message preservation has its own narrower rule in the integrated privacy provisions.
The platform owner identity remains bound to the same underlying account, including during legitimate credential recovery. No first registrant becomes owner merely by arriving first, and no support reset can create a replacement owner or transfer platform control. The application provides no site-delete or platform-ownership-transfer control; legitimate administration, staff appointments and credential replacement preserve that owner binding. This is not a guarantee of perpetual hosting, domain renewal or immunity from an infrastructure-level deletion outside the application's control.
There is no direct law-enforcement portal granting access to members' information. Official requests require verification and human assessment through the published channel, with appropriate scope, minimization, transfer protection and audit. Emergency claims need prompt assessment but do not create unlimited standing access. Members' rights and applicable legal restrictions remain relevant. The detailed privacy provisions govern notice, preservation, disclosure and the treatment of requests from representatives or authorities.
29. Account lifecycle, service changes and availability
You may use the supported account settings and request processes to change information, deactivate where available or request closure. Before a consequential action, the interface should explain its effect on personal content, Pages, balances, business history and pending cases. The primary owner of a Page may need to arrange the Page's disposition or use the relevant recovery process before personal-account deletion can proceed. That requirement must protect actual continuity, not become an excuse for retaining unrelated personal information indefinitely.
Death and memorialization requests require appropriate review. A relative's request does not automatically grant the deceased person's login, private messages or wallet. Page succession and personal-record access are separate questions. We should handle such requests respectfully, collect only the necessary evidence and distinguish confirmed findings from allegations. Memorialization should not create fictional activity or allow another person to communicate under the deceased person's personal identity.
We may maintain, improve, limit or retire features for legitimate operational reasons. Where a change materially affects a paid entitlement or important user reliance, we should give reasonable notice and explain available settlement, export or replacement options, subject to urgent security or legal needs. A planned feature is not a vested entitlement, but an already confirmed purchase cannot be ignored merely because the product roadmap changes.
No online service can guarantee uninterrupted availability on every device or network. We should protect core functions through proportionate capacity and reliability measures, investigate material failures and communicate accurately about known outages. We must not claim support for millions of simultaneous users, perfect physical-device performance or unlimited storage without evidence. Cost limits may affect expensive optional work, but routine pressure to buy ads or invite friends must not be invented as a condition of ordinary free social access.
30. Responsibility, complaints and dispute handling
You are responsible for the actions you knowingly authorize, the rights you claim in submitted material and the accuracy of representations you make in a transaction. You are not automatically responsible for every action committed by an attacker after an account compromise regardless of circumstances. Report a credible compromise promptly and cooperate with a proportionate investigation. We must assess the evidence, our own controls and applicable law rather than imposing a conclusive presumption that every authenticated event expresses the member's wishes.
The operator is responsible for its own promises, handling of information, access decisions and supported transaction processes. We do not guarantee the truth of every member statement, success of every business or outcome of a personal relationship. These limits do not exclude liability that cannot lawfully be excluded, excuse fraud or intentional misuse by the operator, or remove mandatory consumer remedies. These Terms impose no arbitrary monetary cap or broad user indemnity.
Raise an ordinary service complaint through the published support route, identifying the account, item or transaction and the outcome sought. Provide relevant receipts or references without sending passwords or unrelated sensitive documents. A complaint about a staff member should be handled outside that person's control. The response should address the issue, identify any further evidence reasonably needed and explain available escalation rather than requiring the member to abandon criticism as a condition of assistance.
Applicable statutory complaint, regulator and court rights remain available. These Terms do not impose compulsory arbitration, waive collective remedies, choose an exclusive foreign court or select a governing law. Any later proposed arrangement must be reviewed for fairness and legality and clearly presented before acceptance. Attempting informal resolution must not be used to secretly shorten a mandatory limitation period or prevent urgent protective relief.
If a provision is invalid in a particular context, the remaining valid provisions may continue to operate to the extent they can do so fairly and lawfully. We must not replace an invalid restriction with a more burdensome undisclosed one. Failure to enforce a rule on one occasion does not authorize future abuse, but consistent, reasoned enforcement remains important. A legal change affecting the operating business must preserve applicable commitments and provide any required notice; it does not introduce an application-level platform-owner transfer or give another entity unrestricted new rights to private member data.
31. Integrated privacy provisions
The following provisions are part of these same Terms & Conditions. They explain how personal information is handled, the choices members have and the limits on administrative access. Read them together with the feature-specific sections above.
31.1 Scope, responsibility and meaningful choices
These privacy provisions cover personal information handled to operate AmraEk accounts, social features, messaging, Pages, permitted imports, customer support and related security. “Personal information” includes information that identifies you directly and information reasonably linked to your account or device. Replacing your name with an account identifier does not necessarily make information anonymous.
AmraEk.com is the service name used for the information-handling responsibilities described here. References to “we” mean those responsible for this service, not every Page, advertiser, business or linked service. A merchant, employer or other independent recipient may have its own responsibilities for information you deliberately send it. The recipient’s own notice does not replace our responsibility for the copy and processing under our control.
Required fields will be distinguished from optional ones when collected. Choosing not to provide information needed for a particular function may prevent that function from working; it will not automatically authorize unrelated collection. Acceptance of general Terms is not a substitute for a separate permission required for an optional use. We will explain material consequences before requesting such permission and provide a way to change the choice. Where applicable law provides stronger protection than these privacy provisions, that protection remains available.
31.2 Information you provide and information generated by use
Account information includes your chosen name and handle, contact details, language, profile information, declared birth date, registration assurances, account settings and records of linked sign-in methods. We use these to establish and administer your account, distinguish it from other accounts, apply appropriate age restrictions and communicate about account operations. Public profile fields and private registration evidence serve different purposes and will not be treated as interchangeable.
Content information includes posts, photographs, video, comments, reactions, Stories, messages and material you submit in a report or appeal. Associated records can include creation dates, audience choices, edits, publication state and relationships between content and its author. We process these records to deliver the action you request, enforce the selected audience, maintain conversations and investigate specific safety concerns.
Service records include sessions, recognized browsers, network addresses, request times, device and browser characteristics, error information, delivery events and security decisions. These help keep accounts available, detect misuse and diagnose faults. Collection must remain proportionate to those functions. A diagnostic system must not routinely capture passwords, complete private messages, identity documents or unrestricted copies of uploaded archives.
Information may also reach us from another person’s post, a report, a business transaction or a sign-in provider you select. That does not make every allegation true or every use permissible. We will distinguish reported claims, system observations and reviewed findings in decisions about your account.
31.3 Purposes and limits on reuse
We will use account and content information to provide requested features, maintain audience and access decisions, deliver notifications you enable, preserve the integrity of interactions and handle support. Security uses include investigating suspicious sessions, preventing duplicate or abusive submissions, protecting private media and documenting consequential administrative actions. Reliability uses include measuring failed uploads, playback errors and service capacity without unnecessarily retaining content itself.
We will use transaction and participation records to show accurate balances, receipts, permissions and dispute histories where those features operate. We will not infer permission for regulated financial services merely because you can take part in a social feature. Optional discovery, advertising and personalization uses are subject to the specific controls described in these privacy provisions.
A statement that information is useful to the business is not unlimited permission to keep or repurpose it. Before materially changing a purpose, we will assess compatibility, required notice and the permission or other legal justification needed in the relevant location. We will not silently transform identity evidence into an advertising dataset or preserved private messages into an AI training resource. Records kept for a legal hold remain limited to that hold. Truly anonymous statistics may be used to understand overall service performance; identifiable records and reversible pseudonyms remain subject to these privacy provisions.
31.4 Registration, provider sign-in and contact verification
When you select a supported external sign-in provider, we receive the information authorized through that provider’s login process. This may include a provider account identifier and approved basic profile information. Provider login does not grant unrestricted access to your lifetime posts, photographs, friends or private conversations. We will identify the permissions requested before you authorize them and use provider credentials only for the stated connection.
Phone verification uses your number and a limited verification result to confirm control of the number and apply registration safeguards. It does not establish every aspect of your legal identity, age or ownership of other accounts. A shared, changed or recycled number may require additional review. We will not expose your private phone number as a public directory entry merely because verification is required. Neither sign-in nor phone verification authorizes us to collect your address book or send unsolicited invitations to your contacts.
31.5 Passwords, passkeys and device verification
Your password is an authentication secret. The owner and staff must not be able to read or retrieve it. Password verification will use a protected one-way representation rather than a reversible password store. We will never ask you to send a password, one-time code, private authentication key or recovery secret through a public post, ordinary chat or a support conversation. Recovery establishes new authorized access; it is not a way for staff to discover the old password.
For supported passkeys, the service receives a public credential and the result of the authentication ceremony. A device may ask for a fingerprint, facial verification or a device PIN. Those local methods are controlled by the device and its authenticator. AmraEk will not describe them as server-side iris recognition or require the device to send raw fingerprints or facial templates. A successful device-verification result does not justify collecting additional biometric material.
An optional secret phrase, where offered, will be hashed, used alongside a passkey and not retained as readable voice content. Spoken entry requires an explicit choice and an on-device processing method; if that method is unavailable, typed entry will remain the alternative. Microphone audio must not be silently transferred to a cloud transcription provider. Security events may record that verification succeeded or failed, without recording the secret itself.
31.6 Identity evidence, reviewed age and verification decisions
Some permissions or safety reviews may require identity evidence, a fresh capture or a reviewed correction. The request will explain the purpose, accepted alternatives, necessary fields, intended retention and effect of refusing. Submit evidence only through the designated private process. We will not require documents to be posted publicly, sent to another member or handed to an individual moderator through their personal account.
Evidence can contain highly sensitive details about you and other people. Collection will be limited to what the stated decision needs. We will distinguish the original evidence, the reviewer’s conclusion and a public verification indicator. A public indicator must not disclose document numbers, private addresses, complete birth dates or the underlying image. A capture intended for human review will not be represented as certified biometric proof or a guarantee that fraud is impossible.
Access to evidence will be restricted to authorized reviewers assigned an appropriate purpose. The collection notice will state the evidence retention period and explain any separate retention of a minimal decision record. Retaining a verification outcome does not automatically justify keeping the full document forever. You may challenge an inaccurate finding or seek an appropriate correction. Changes to editable profile information will not, by themselves, erase a documented youth safeguard or override independently reviewed evidence.
31.7 Children, young people and family relationships
Age screening and feature eligibility will be explained before registration or access to an age-restricted function. We will not treat an adult’s ordinary acceptance of these Terms as verified parental authority for an unrelated child. Where a guardian route is offered, the process must establish the required relationship and permission without collecting more family information than necessary. A person who cannot use a feature because of age must not be encouraged to enter a false birth date.
Youth restrictions will operate separately from optional privacy choices. Personalized advertising, cross-service tracking and precise-location advertising will remain unavailable to accounts subject to the youth restriction. An uncertain or conflicting age record will not automatically be treated as proof of adulthood. A later profile edit must not reactivate permissions that require a fresh, valid decision.
A guardian relationship does not create an unrestricted staff or family surveillance account. Any supervisory access will be described to the affected users in language suitable for their age and limited to the permitted function. We will assess requests from guardians, young people and representatives with regard to applicable rights and safety, rather than automatically disclosing every private communication to anyone asserting parental status. Content intended for children and accounts operated by children require their own assessments; a children’s Page label alone does not establish lawful consent or a safe audience.
31.8 Audiences, discovery and information shared with others
Your selected audience determines who the service may show an item to, subject to safety restrictions, blocks and the rules of the relevant space. Public content may be viewed, copied, linked or indexed outside the people you expected to see it. Choosing a limited audience reduces authorized distribution through AmraEk; it cannot guarantee that a recipient will never take a screenshot, describe the content elsewhere or retain a copy on their own device.
Profile locking, exclusions, relationship settings and message permissions will be enforced when content is requested, not treated only as decorative labels. Discovery features may use permitted profile and relationship information to suggest accounts or content. A suggestion is not a friend request, a contact upload or an instruction to message anyone. Tagging another person does not give the author permission to disclose that person’s private contact information or bypass a review requirement.
A group or Page may have several authorized managers. Information sent to that space may be visible to the managers permitted to handle it, rather than only to the person whose name or photograph appears first. We will distinguish personal identity, Page identity and administrative access in the interface. Switching accounts must not leave private data from the previous account available through the next account’s screens or cached responses.
31.9 Optional imports of your own Facebook material
Imported items remain private until you deliberately choose to publish them with an audience. Where available and reliable, original dates are preserved as source dates rather than replaced with the import date. Private processing copies of the archive will be removed after completion or terminal failure under the operational cleanup process. Import does not delete the source account, change Facebook’s permissions or transfer another person’s copyright. You remain responsible for choosing material you are entitled to copy and share.
31.10 Content ownership, editing and ordinary deletion
Editing, hiding, withdrawing and deleting are different actions. Hiding an item from your view does not necessarily delete its source. Withdrawing a publication stops ordinary distribution but may leave a private original or necessary evidence. Deletion removes the item from the applicable customer-facing function and starts the relevant cleanup or restricted-retention process. The interface must describe which action you are taking.
Copies in active storage, generated media, caches and backups can follow different cleanup steps. We will take reasonable steps within our control to propagate the decision and prevent a later refresh or restoration from republishing deleted material. A recipient’s independently retained copy is outside those storage systems. The existence of an external copy does not excuse us from addressing the copies we control. Exceptions must be tied to a disclosed purpose, a justified retention rule or an applicable legal requirement.
31.11 Deleted personal messages and restricted legal preservation
Customer-deleted personal messages cannot be restored through customer accounts; subject to applicable law, AmraEk will preserve a restricted, encrypted copy for up to 365 days after deletion solely to respond to verified lawful requests, then purge it, except where an applicable mandatory legal hold requires specified records to remain longer. Deleting an account, migrating storage, rotating encryption keys or restoring a backup must not restart that clock. The preserved record will contain only the content and associated identifiers needed for the permitted preservation purpose. Where an attachment or linked item was never retained, this policy is not a promise to reconstruct it from another service.
Preservation is not a standing invitation for staff to read conversations. The preserved copy will be separate from ordinary conversations, account downloads and routine staff tools, with access limited to authorized human review of the verified lawful request. It will not be used for advertising, recommendations, AI training, personal curiosity or general monitoring. The full period will not be used automatically where a shorter period or earlier erasure is required. At expiry, the record will be removed from the preservation system unless a verified, documented hold applies to that particular material.
A mandatory hold must identify its applicable authority, scope, start and review conditions. “Possible future usefulness” is not enough. A hold covering specified messages does not authorize indefinite retention of every conversation associated with the account. When the hold ends, the ordinary retention rule will be applied without granting a new 365-day period.
Customer support cannot restore preserved messages to your inbox or use preservation as a recovery service. A report submitted before deletion may contain independently submitted evidence; that is a distinct record with its own disclosed purpose and retention, not permission to retrieve unrelated preserved messages. Requests invoking applicable information rights receive human assessment, including protection for other participants and any lawful restriction. A legally required access copy does not reinstate the conversation. It is not a promise to recover information already irreversibly erased.
31.12 Official requests, emergency claims and disclosures
An authority seeking private information must use the published official request channel and provide enough information to authenticate the requester, identify the relevant accounts or records and explain the claimed legal authority. An official-looking email address, badge image or urgent tone is insufficient by itself. We will independently verify material details where necessary and assess whether the request is valid for the operator and the information concerned.
An authorized human reviewer will assess scope, applicable procedure and any need for specialist legal advice. We may seek clarification, require an appropriate legal instrument, narrow an overbroad demand or challenge a request where warranted. Preservation and disclosure are separate decisions: keeping specified records temporarily does not by itself authorize releasing them. We will disclose only information responsive to the valid request, through a protected transfer process.
Claims of imminent danger will be escalated for prompt human evaluation. They do not create permanent direct access or excuse unrelated disclosures. We will record the basis for an emergency decision, what was shared, the recipient and the reviewing authority within AmraEk. An emergency assertion alone does not bypass the legal limits on access to preserved deleted messages. User notice will be considered and provided where appropriate and legally permitted, including after a temporary restriction on notice ends.
There will be no law-enforcement portal that permits unrestricted searches or live browsing of private accounts. An authority cannot obtain passwords, private authentication keys or a customer impersonation session through this process. AmraEk cannot provide information it does not possess or decrypt information for which it has no capability.
31.13 Owner, administrator, moderator and verification-review access
Administrative status is a responsibility, not ownership of customers’ private lives. The platform owner and staff will use their own attributable accounts with permissions appropriate to their duties. They must not sign in as a customer, borrow credentials, generate an ordinary customer session for covert observation or send a message that falsely appears to come from that customer. The same rule applies to privileged audit and user-verification review.
Moderation access to private material will be tied to a specific report, appeal or authorized safety case. A reviewer should receive the relevant item and sufficient context, not an unrestricted inbox. Requests for wider context require a recorded reason and appropriate approval. Routine service dashboards should use counts, status and limited metadata wherever those answer the operational question. A privileged owner security review may provide necessary read-only access after fresh security verification, with a recorded purpose and audit trail. That route must not become general browsing authority or bypass the distinct restrictions on preserved deleted messages.
Sensitive access will be logged with the staff identity, affected record, purpose and action. Staff must not copy evidence to personal devices or unofficial messaging channels. Permissions will be reviewed and removed when the role or assignment ends. A staff member’s ability to review identity evidence does not grant authority over balances, account recovery or private-message preservation.
Owner security checks protect privileged actions but do not turn all owner requests into valid privacy purposes. Free promotional placement, where separately offered, does not entitle the owner to secret audience information or remove youth, block, privacy or content-safety restrictions. Concerns about staff misuse may be raised through the privacy complaint process without giving that staff member unrestricted control of the complaint.
31.14 Business Page conversations and transaction records
Messages to a business Page serve a different recordkeeping function from ordinary personal conversations. Authorized Page team members may need access to enquiries, order instructions, delivery information and the business’s replies. The interface will make this recipient context clear. A customer should not assume that a Page message is a private conversation with a single named employee or that a change in the Page team deletes the business record.
Business Page conversations are intended to be persistent business records without an ordinary delete or unsend option. Closing a conversation or leaving the Page does not erase the record. That product rule does not create an exception to applicable privacy rights or authorize indefinite retention without a justified purpose. Requests for correction, restriction or erasure will be assessed separately, including any genuine need to retain transaction evidence or defend a claim.
Businesses must use information received through AmraEk for the disclosed transaction or communication purpose. A delivery address is not permission to publish the customer’s home location or add them to unrelated marketing lists. Page-team access must end when its authority ends. AmraEk may retain limited receipts, status changes and dispute evidence independently of the conversational view where necessary for platform accountability. The personal-message preservation period is not a universal deletion deadline for business, payment or legally required records.
31.15 Retention criteria, inactive accounts and backups
Each category of information will have a retention rule based on its purpose, sensitivity, operational need and applicable obligations. We will consider whether the purpose can be met with fewer fields, a shorter history or a minimal outcome record. A decision to keep an account available is different from a decision to keep every log or failed upload associated with it.
Ordinary inactivity alone will not be treated as a request to destroy a legitimate account and its social relationships. You may still request closure or exercise applicable data rights. We will not keep unnecessary identity evidence or temporary processing files simply because the account remains open. Records required to establish a dispute, a security event or a valid legal obligation may have a different lifecycle from the public profile.
Backups protect against accidental loss and service failure. They are not a secondary content library for staff, advertisers or customer recovery of deleted messages. Where individual removal cannot occur immediately in a backup, the affected information will be kept out of ordinary use and removed through the established backup lifecycle. A restoration must reapply deletion decisions and current access restrictions before information returns to service.
We will document applicable retention periods or meaningful decision criteria and explain material exceptions in responses to privacy requests. Encryption alone does not justify retaining data forever. Expired records must also be addressed in indexes, derivative files and vendor-held copies within our control.
31.16 Calls, photographs and device permissions
Starting an audio call requires the relevant device permission and connection information. Call setup may involve participant identifiers, connection signals, time, duration and failure status. These records support delivery, troubleshooting and abuse handling; they are distinct from a recording of the conversation. We will not routinely record call audio or activate a microphone in the background. Any recording feature requires its own clear notice, deliberate controls and an assessment of the permissions required for everyone involved.
Network connection methods can reveal technical information to communication participants or infrastructure providers. We will explain significant differences where a feature offers a choice; a general privacy setting cannot promise that every network intermediary sees nothing. Ending a call must stop that feature’s active microphone use, subject to the device’s own permission controls.
Photographs and other files can contain embedded information, including dates, device details or location. The upload and publication process will distinguish preservation of your private original from the version shown to an audience. We will not represent every published file as metadata-free without verifying that behavior. A selected photograph does not grant permission to browse the rest of your library. Camera, microphone and file access remain tied to the action you initiate.
31.17 Sensitive feature contexts and information about other people
Optional features such as job applications, family relationships or relationship introductions may involve information that deserves additional care. The collection screen will explain who receives it and which fields are needed. A résumé sent to an employer, for example, must not silently become a public profile attachment. Information entered for a private introduction must not automatically become an advertising interest or public discovery field.
You should include information about another person only where necessary and appropriate for the feature. Naming an emergency contact, family member or reference does not give that person an AmraEk account, authorize marketing to them or prove that they consented to every proposed use. We will provide a way to raise concerns about information submitted by someone else and assess correction or removal without unnecessarily revealing the complainant’s identity.
Where a feature asks for health, religion, ethnicity or similarly sensitive information, the purpose and legal requirements need particular attention. Such information must not be collected merely because a form could accommodate it. We will offer less intrusive alternatives where suitable and prevent a private response from being repurposed as a public badge, staff curiosity item or undisclosed commercial audience category.
31.18 Cookies, recognized browsers, location and notifications
We use necessary browser storage and similar mechanisms to maintain sessions, remember deliberate settings, protect requests and recognize permitted saved accounts. A recognized-browser limit is not a claim that we have permanently identified a physical device or every person who uses it. Clearing storage, shared computers and changes in browsers can affect recognition. We will not secretly add invasive fingerprinting simply to make a limit harder to evade.
Optional measurement or advertising technologies require their own explanation and any permission applicable to the user’s location and age. A setting for necessary session storage must not be described as consent to cross-service tracking. Where a browser or device supplies a legally recognized privacy preference, we will handle it as required for the relevant processing.
Precise location will be requested only for a disclosed feature and will not be inferred as permission from a general regional preference. Choosing a country, district or community does not authorize continuous location tracking. Approximate network-derived location may help security or regional service delivery, but it must not be represented as an exact observation of where you are.
Push notifications require device permission and an account subscription. You can stop future push delivery by changing the relevant settings or revoking permission. Notification previews may appear on a locked screen or shared device; the product will provide appropriate controls without treating a notification subscription as permission to reveal sensitive content unnecessarily.
31.19 Advertising, promotions and measurement
We will not use identity documents, authentication secrets, restricted deleted messages or private report evidence to select advertisements. An advertiser will not receive an individual’s private conversation merely because its campaign reached that person. Reporting should use suitable aggregation and avoid disclosing a small audience in a way that exposes a particular person’s sensitive activity.
Following an advertisement to an external destination can disclose information directly to that destination through your interaction. We will distinguish that transfer from AmraEk’s own measurement and explain any account-linked conversion tracking before enabling it. Linking an external data source must not bypass an account’s revoked permission or youth restriction.
Clearly labelled, age-appropriate house educational notices may be offered within an eligible child context, including an age-ten context where the applicable entry and guardian requirements are satisfied. Such notices must not use behavioral profiling, cross-service tracking or disclosure of children’s information to advertisers. Their educational label does not authorize ordinary personalized advertising. An owner-funded or free boost does not purchase access to every user. All promotions remain subject to audience eligibility, blocks, privacy choices and safety review. Free placement changes billing treatment, not the privacy rights of viewers. We will identify any legally regulated sale, sharing or targeted-advertising practice that actually applies and provide the required choices; a commercial label cannot be used to avoid that assessment.
31.20 Recommendations, automation and artificial intelligence
Automated tools may assist with spam detection, media checks, safety triage and service reliability. They can make mistakes. A restriction or verification result should distinguish automated signals from a reviewed finding, provide an appropriate explanation and offer review where required or supported. An ordinary ranking adjustment is different from a decision affecting identity, access or financial participation; more consequential uses require additional assessment.
Where an optional AI feature sends information to a provider, the feature notice will identify the relevant recipient category, purpose, input and retention treatment. Do not include another person’s confidential information unless you have authority and the feature supports that use. Private messages, identity evidence and restricted preservation records will not become general model-training material through acceptance of these Terms.
We will not describe an AI output as a confidential human professional relationship or guarantee that it is accurate. New automated processing with materially different consequences will require suitable notice and controls before activation.
31.21 Vendors, external recipients and international processing
Providers may process information on our behalf for hosting, storage, delivery, account verification, notifications, security or support. We will select providers appropriate to the information and require contractual protections addressing permitted purposes, confidentiality, access, retention, deletion and incident cooperation. A provider’s technical ability to receive data does not mean that every category should be sent to it. Access should be limited to what its assigned service needs.
Some recipients act independently, including a business you contact, a payment provider you deliberately use or a website you visit through a link. We will distinguish those relationships where relevant. You should review the recipient’s notice for its own processing, while retaining the ability to ask AmraEk about the information we disclose. Merely embedding or linking an external service does not make that service an AmraEk-controlled account.
Information may be processed in countries different from where you live. Before relevant processing begins, the published notice will identify the actual arrangements and applicable safeguards. We will not promise that all data remains in your country without supporting that promise. Where a transfer requires a particular legal mechanism, assessment or supplementary protection, it must be in place for that transfer. You may request information about the safeguards, subject to proportionate protection of confidential security or commercial details.
31.22 Security, encryption and incident response
We will use safeguards proportionate to the information, including access controls, protected transport, appropriate encryption at rest, separation of sensitive records and controlled management of encryption keys. The ability of authorized systems to decrypt information must be restricted and auditable. Encryption controlled by the service is not end-to-end encryption, and we will not describe it that way when the service can obtain plaintext.
Security also depends on software maintenance, safe handling of uploads, staff practices, recovery procedures and the protection of vendor access. We will investigate credible vulnerability reports and suspected unauthorized access. A report should contain enough detail to locate the issue without publishing someone else’s private information or requesting another person’s credentials.
If a security incident affects personal information, we will assess its nature, likely consequences and the people concerned, take appropriate containment and remediation steps, and make notifications required by applicable rules. Where we contact affected users, the communication will explain known facts, useful protective actions and the available support route. We will distinguish confirmed findings from matters still under investigation.
No service can guarantee that misuse, loss or interruption will never occur. That limitation does not remove our responsibility to protect information, investigate incidents and honor the commitments in these privacy provisions. Incident evidence itself must be kept private and limited to the response, accountability and justified follow-up purposes.
31.23 Your information rights and how to make a request
Depending on the law applying to the processing, you may have rights to access information, obtain a copy, correct inaccuracies, request erasure or restriction, object to particular uses, withdraw consent or receive qualifying data in a portable form. These rights can have conditions and exceptions. We will not tell you that accepting Terms waives them, or that an account must remain active before a privacy concern can be considered.
Use the AmraEk Help Center and select the privacy category to raise an information request. An AmraEk account or public email address is not required to submit a guest request; retain its private reference and access code to read replies. Explain the account or information concerned and the outcome you seek. Possession of a ticket code establishes access to that support conversation, not ownership of another account or authority to obtain or delete its information. We may ask for proportionate evidence to verify identity or authority, especially where disclosure could expose another person. We will use an existing authenticated route where suitable rather than automatically demanding a new identity document for every request.
We will explain the applicable process, acknowledge material clarification needs and respond within the period required by the governing privacy rules. If an extension, refusal or limitation applies, we will explain the reason and available review or complaint route, except where a lawful restriction prevents that explanation. We will not invent a universal deadline for every jurisdiction or charge a routine fee merely to discourage requests.
You do not need to create an AmraEk account to raise a concern about information concerning you. A non-member may identify a photograph, mention, imported item or other record using a link or a sufficiently clear description. We will seek only the additional information reasonably needed to locate the record and assess the request. We will not create a public profile for you as part of that process. Where a dispute concerns competing accounts of an event, we will preserve the distinction between correcting factual personal information and adjudicating the underlying disagreement.
An authorized representative may make a request where permitted, with appropriate proof of authority. Access copies may require redaction to protect other people, confidential security material or a valid exemption. The no-restore rule for deleted messages does not replace this legal assessment.
31.24 Contacts, complaints and changes
The Help Center is the service contact channel. The Mighty owner assigns and removes authorized support workers; a general administrator or moderator role alone does not grant access to support tickets. Replies are sent as the AmraEk Help Center. Screenshots and short diagnostic videos submitted with a ticket are private support evidence, accessible to its requester and currently authorized support staff. Avoid uploading passwords, one-time codes or unrelated private information. The interface explains upload limits and any team-readiness delay. The correspondence address is Mission Road, Dinajpur, 5200, Bangladesh.
You may raise a privacy complaint, challenge a response or report suspected staff misuse through that route. Where applicable, you may also complain to the competent regulator without first obtaining permission from AmraEk. Our response will identify relevant escalation information rather than claiming that one authority has exclusive jurisdiction over every user worldwide.
Material changes will be explained in a revised version of these Terms with its effective date. A new version will not silently legalize an undisclosed historical practice or retroactively create consent. Where new permission is required, we will request it before beginning the optional processing. Earlier versions will be retained for accountability. Privacy and data-retention disclosures remain within this single readable Terms document, accessible from signup and account controls, without a separate privacy agreement or duplicate retention notice. Permissions for optional actions remain specific to those actions and do not replace these provisions.