Skip to content
Sign in
ARINE LEGAL

Privacy Policy

How Arine handles account, connected-platform, store, creative and billing data.

Last updated: September 20, 2026

Operator: Arine Ecosystem Pvt Ltd

Contact: arine.soem@gmail.com

1. Who we are and what this policy covers

Arine Ecosystem Pvt Ltd ("Arine", "we", "us") provides a platform that helps businesses research, plan, create, and manage advertising campaigns, including Meta campaigns, and connect their e-commerce stores. This policy applies to our public website, dashboard, integrations, and related services.

For account, billing, and website data, Arine generally acts as the data controller. For store, campaign, and customer data that a business connects to Arine, we generally act as a processor or service provider on that business's instructions.

2. Data we collect and why

DataWhy we collect it
Google sign-in name, email address, and account identifierTo create and secure your account, identify you, and provide support.
Meta ad account IDs; campaign, ad set, ad, budget, status, and performance dataTo let you select an ad account, plan campaigns, create and manage campaign objects, and show performance reporting.
Facebook Page and Instagram account names and IDsTo show eligible business identities and attach the identity you choose to a campaign.
Meta access tokens and granted permissionsTo make authorized Meta API requests on your behalf. Tokens are not used for any unrelated purpose.
Shopify or WooCommerce products, catalog details, and order dataTo understand your products, inform campaign planning and creatives, and measure commercial performance.
Brand details, prompts, chats, and images you upload or generateTo research competitors, create campaign plans and advertising assets, and maintain your project history.
Billing name, email, address, tax information, payment status, and PayU transaction referenceTo sell credits, process payments, prevent fraud, issue invoices, and maintain financial records. Arine does not store full card numbers, CVVs, or UPI PINs.
IP address, device/browser information, session and service logsTo operate, secure, troubleshoot, and improve the service.
Support messagesTo answer requests and resolve account or technical issues.

We do not sell personal information or Meta Platform Data. We do not share Meta data with advertisers or other parties for their own use. We do not use customer content, connected-store data, or Meta Platform Data to train our own general-purpose AI models.

3. Facebook and Meta integration

Arine connects to Meta through Meta Login and the Meta Marketing APIs. After you authorize the connection, Arine may receive the Meta ad account IDs available to you, campaign and performance data, Facebook Page and Instagram account names and IDs, access tokens, and the permissions you grant.

We use this Meta data only to display your eligible assets, prepare advertising plans, create or update campaigns on your instructions, and report campaign performance. Campaigns and other advertising objects created by Arine are created paused. You decide whether to activate them and control the budget and spend in Meta.

If the app requests pages_read_engagement, it uses that permission only to retrieve Page identity and engagement information needed to select the correct Page, prepare relevant campaign context, and report on connected Page performance. We do not publish Page content using that permission.

4. Service providers and connected platforms

The following providers may process data for us and only to provide their contracted service or act on your instructions:

  • Our application hosting and database providers — host the Arine website, application, database, and operational logs.
  • Cloudflare — stores and delivers uploaded or generated images and protects network traffic.
  • Apify — performs competitor and public-web research requested through the service.
  • Pollinations and OpenRouter — process prompts, relevant brand context, and images needed to generate campaign text or creative output.
  • PayU — processes payments and payment-related fraud checks.
  • Google — provides Google sign-in and returns your authorized name, email, and account identifier.
  • Meta — provides Facebook, Instagram, and advertising APIs when you connect your account.
  • Shopify and WooCommerce — provide store data when you connect a store.

These providers may process data in countries other than yours. Where required, we use contractual and other lawful safeguards for international transfers.

5. How long we keep data

  • Account and brand data: while your account is active and for up to 30 days after a verified deletion request.
  • Meta and store data: while the integration is connected or the related project remains in your account. Disconnecting Meta immediately revokes and deletes the stored Meta access token.
  • Uploaded images, generated images, and chats: until you delete them, close the account, or request deletion; deletion is completed within 30 days, including from active storage.
  • Security and application logs: normally up to 90 days, unless longer retention is required to investigate abuse or comply with law.
  • Invoices, transaction records, and tax records: up to 8 years, or the longer period required by applicable Indian tax, accounting, or legal rules.
  • Backups: deleted data may remain in encrypted, access-restricted backups for up to 90 days before being overwritten.

6. Your choices and rights

You may ask to access, correct, export, restrict, object to, or delete your personal information. You may also withdraw consent and disconnect Meta or a store at any time. Depending on where you live, you may have additional rights and may complain to your local data-protection authority.

Email arine.soem@gmail.com from your registered email address with the subject “Privacy Request.” We may verify your identity before acting and normally respond within 30 days. See our dedicated Data Deletion Instructions.

7. Legal bases, security, and children

We process data as needed to perform our contract with you, with your consent when you connect an account, to comply with law, and for legitimate interests such as security, support, and service improvement where those interests do not override your rights.

We use HTTPS in transit, encrypt access tokens at rest, and limit access to personnel and service providers who need it for their work. No system is completely secure, so we cannot promise absolute security.

The service is intended for businesses and people aged 18 or older. We do not knowingly collect personal information from children.

8. Changes and contact

We may update this policy as the service or law changes. We will post the revised policy here and change the “Last updated” date; material changes may also be communicated in the app or by email.

Questions or rights requests: Arine Ecosystem Pvt Ltd, arine.soem@gmail.com. We aim to respond within 30 days.

OCTOBER 29, 2026 VERIFICATION PACK

Proposed verification updates

Draft supplement · reconcile with production before publication

Google sign-in and read-only connections

The verification pack identifies the application as Arine. Google sign-in uses name, email and account information. The documented Analytics scope is https://www.googleapis.com/auth/analytics.readonly; Search Console uses https://www.googleapis.com/auth/webmasters.readonly.

Arine lists the properties and sites the signed-in user can access, allowing selection for the relevant brand. GA4 access reads aggregated sessions, users, engagement, ecommerce purchases, purchase revenue and funnel-event counts, together with property currency, time zone and web-stream URL. Search Console access reads aggregated clicks, impressions, click-through rate and average position, including date, query, page, country and device breakdowns.

These scopes are read-only. They do not authorize changes to Analytics properties, Search Console settings or Google Ads campaigns. The pack states that Arine reads no user-level or identifying Analytics data.

Use and sharing of Google data

The pack states that Google data is used for the brand’s own performance context and advertising planning, is deleted on disconnect, is not sold, is not used for serving advertising, and is not used to train AI models. Arine does not currently send Google data to AI. No future AI processing is represented as implemented.

Google data must not be read by people except in cases permitted by Google’s applicable user-data policy. The exact approved Limited Use statement and full storage, sharing and human-access wording must be supplied before this supplement can replace the live policy.

Meta permissions listed in the pack

This table records the review scope named in the verification document. Confirm it against the production application and remove any permission not actually requested before publication.

PermissionDocumented purpose
ads_readRead authorized ad-account, campaign and advertising performance information.
ads_managementCreate or update campaign objects on an authorized user’s instructions. Existing Terms state that created campaigns are paused.
business_managementAccess authorized business assets needed for the connected brand’s workflow.
pages_show_listList Pages the user can access so they can select the correct business identity.
pages_read_engagementRead Page identity and relevant engagement context; this permission does not authorize publishing Page content.
pages_manage_adsUse the selected Page identity in advertising workflows where authorized.
instagram_basicRead the connected Instagram identity where Instagram is enabled and this permission is requested.

The pack requires Meta Platform Data not to be sold or used for eligibility decisions or surveillance, and to be deleted on disconnection, request or when Meta requires it. Exact implementation and final policy language require review.

Workspaces, agencies and client authorization

Access must be authorized for the business and connected brand. The pack requires the replacement policy to address workspace access, agencies and client authorization. Brand-level access controls and retention behavior must be reconciled with the production application.

Providers, retention and security

The current policy above names PayU; the newer pack names Razorpay, Resend, Sentry and PostHog, and describes AWS hosting. These references conflict or require production confirmation. They must not be treated as a verified current provider list.

The pack’s proposed analytics-event retention is up to 12 months. Confirm PostHog settings before committing to that period. Existing retention periods above remain the source wording until replaced by an approved policy.

Before publication

  • Supply the approved replacement Privacy Policy, Terms and Data Deletion text, including Google’s exact Limited Use wording.
  • Confirm the Grievance Officer’s name and company postal address.
  • Verify hosting, payment and service providers, cookie inventory, permissions, retention and workspace-deletion behavior.
  • Set the updated policy date to the actual publication date.