arimi.ai.app Privacy Policy and Data Deletion

1. Operator and contact

arimi.ai.app is operated by the owner of the Instagram account @arimi.ai. For privacy questions or requests, send an Instagram message to that account. The account owner handles privacy-request messages manually.

This policy covers arimi.ai.app and the Google connection named arimi.ai Social Media Automation, used by the same account owner for the Instagram comment-reply automation. The website’s general business contact details in the shared footer are separate from the app’s privacy-request contact above.

2. What the service does

The automation reads comments on selected Instagram posts and reels through Meta’s official Instagram API and matches configured keywords. Depending on the delivery promised in that reel’s caption, it either publishes a relevant public reply or sends one private reply containing a link to the requested guide on this website.

With the operator’s Google authorization, it also reads prepared caption and reply text from the operator’s selected Social Media 2026 folder in Google Drive. It uses those files to match each reel with its intended keyword and reply. A file’s presence alone does not authorize publishing it: reply controls and campaign matching must also allow delivery.

Private guide delivery is optional and requires the operator to enable it. A qualifying keyword comment requesting delivery privately can receive one initial private reply through Meta’s official comment-reply feature, within its allowed time window. The automation does not send private follow-ups or read private conversations, like content, or follow accounts. Messages sent to @arimi.ai to make a privacy request are handled manually by the account owner, outside this automation.

3. Information processed

Posts and reels: media IDs, captions, links, and timestamps.
Comments and their authors: comment text, comment IDs, usernames, Instagram user IDs, and timestamps.
The connected account: its Instagram account ID and username.
Google Drive content source: selected folder and file IDs, names, file metadata and timestamps, prepared caption text, prepared public-reply text, and the published website guide URL for optional private delivery. Video metadata helps identify a post folder; this integration does not download video content.

The service stores reply records and operational logs containing relevant comment, media, and user IDs; usernames; proposed or sent reply text and guide links; public or private delivery mode; reply or message IDs; and timestamps.

The reply ledger does not separately store the original comment text. Comment text is processed to find keyword matches.

4. How information is used

Information is used to find keyword matches, deliver the public reply or private guide link requested by the reel’s caption, prevent duplicate replies, monitor operation, and investigate errors.

This information is not used for advertising or profiling. Data is not sold. Google Drive data is used only to provide this content-matching and reply service; it is not used to train AI models.

Google’s requested permission allows viewing and downloading Drive files. The configured reader is restricted to the selected source folder and its supported post files. It does not create, edit, delete, or change sharing permissions on Drive files, and it does not upload follower records to Drive. Prepared reply text may appear publicly under Instagram comments when the operator enables public sending; a configured website guide link may instead be sent privately when that is the promised delivery and private sending is enabled.

5. Storage and providers

Automation records are stored in a private, self-hosted system with restricted administrative access. Instagram and Google OAuth tokens are stored as encrypted n8n credentials. Selected Drive text and metadata are cached in the private system. Restricted local credential backups support administration and recovery; they are not public downloads.

Meta processes Instagram API requests, public replies, and optional private guide messages. Google processes Drive authorization and read requests. Telegram delivers operational alerts to the operator; these may contain relevant operational identifiers or source-folder names, but not access tokens. An email provider may deliver operational alerts if configured.

This website: this static policy page is hosted on Hostinger. Its shared layout loads fonts from Google Fonts, and the shared site script stores a language preference in the browser’s local storage under aiVisionLang. These website features are separate from the Instagram automation records described above.

6. Retention

Reply records and application event history currently have no automatic deletion deadline. They remain until manually deleted or the service is retired. Selected source text, metadata, and credential backups remain until updated or manually removed during administration; stopping the connection alone does not erase these stored copies.

Routine workflow execution history is configured for pruning after 14 days, subject to the pruning cycle and count limit. This setting does not apply a 14-day deletion deadline to the reply ledger or application event history.

Data deletion

7. Request deletion of your data

To request deletion of records associated with you in arimi.ai.app, contact the account owner manually through Instagram:

Open @arimi.ai on Instagram and send a message.
Use the words “Privacy request” or “طلب حذف البيانات”, say that the request concerns arimi.ai.app, and state your Instagram username.
If available, include the relevant reel or comment link. A post link and enough detail to identify the comment or reply can also help locate the records.

The account owner handles these requests manually and may verify that you control the Instagram account before processing your request. You will never be asked for your password or access tokens; do not send them.

Deletion requests concern records held by this automation. Deleting these records does not automatically delete content from Instagram or data held by Meta. New interactions may be processed afterward.

The operator can revoke the Google connection in their Google Account’s third-party connections settings and request removal of stored source data through the same contact route. Revocation prevents future authorized reads; it does not itself delete cached data or public Instagram replies.

You can use the same contact route for other privacy questions or to ask about your request’s status. If your request also concerns a public reply, identify that reply in your message.

Contact @arimi.ai on Instagram