Data fiduciary / controller: Adrologic Pvt Ltd, 30/160, Sector 3, Pratap Nagar, Sanganer, Jaipur 302033, Rajasthan, India (CIN U62011RJ2023PTC088227) ("Adrologic", "we").
1. Scope and roles
1.1 This policy covers craivis.com, the CRAIVIS web app, the mobile app, the magic-link review pages (including agency-branded ones), the businesses' public pages (§1.4), the public demo, our e-mails and notifications, and our support channels.
1.2 Two roles.
- For your account data (members, sign-in, billing status, usage) Adrologic decides why and how it is processed: we are the data fiduciary under India's Digital Personal Data Protection Act, 2023 ("DPDP Act") and the controller under the GDPR where it applies.
- For personal data inside your content and operations (people in your photos, your approvers, your agency's clients, your WhatsApp contacts, the people who send an enquiry through your Brand's page, your website's content) you are the data fiduciary / controller and Adrologic is your data processor, under the Data Processing Addendum ("DPA"). This policy describes that processing for transparency; the DPA governs it.
1.3 Agencies' clients and approvers. If you approve content through a link sent by an agency, the agency is responsible for your data and we process it for the agency. The review page names the agency and says that CRAIVIS (Adrologic) is the processor.
1.4 People who contact a business through its page. Each business on CRAIVIS has a public page at craivis.com/@name with its links, its products and an enquiry form. If you send an enquiry there, the business is responsible for your details (your name, your phone number or e-mail, your message, the product you asked about, and the consent sentence you ticked, word for word) and we keep them for it as its processor. We keep a keyed hash of your IP address, never the address itself, to stop the form being flooded, and we count the page's views and taps per day without recording who you are and without setting a cookie. Ask the business to delete your enquiry, or write to contact@adrologic.com.
2. What we collect, and why
| Category | What exactly | Where it comes from | Why we process it | Basis (DPDP / GDPR) |
|---|---|---|---|---|
| Sign-in and account | E-mail address or mobile number, one-time codes (hashed, short-lived), passkey public keys, name, organisation name and type (direct / agency), role, language and theme preferences, device and browser information, IP address, sign-in times | You; your device | Create and secure your account; show the right brands and roles; fraud and abuse prevention | Consent at sign-up; performance of the contract (GDPR Art. 6(1)(b)); DPDP s.7(a) voluntary provision |
| Billing | Billing name and address, country, GSTIN (optional), currency, plan, subscription and mandate identifiers issued by Razorpay, invoice history, refund history | You; Razorpay | Charge you, issue GST-compliant invoices, apply regional prices (by billing address and card country, never IP), handle refunds and disputes, keep statutory accounting records | Contract; legal obligation (GST, Companies Act, RBI e-mandate rules) |
| Card and bank data | We never receive or store card numbers, CVV, UPI PINs or bank credentials. Razorpay collects them on its own pages. We receive a token, the last 4 digits and the card country | Razorpay | Show you which method is on file; regional pricing | Contract |
| Brand profile | Website URL, text and images fetched from your website when you paste it, logo, colours, fonts, products, prices, hours, city, category, tone, languages, prohibited words, religions served (optional, only if you enter it), disclosure setting, custom occasions | You; your public website; Google Places API (pre-fill) | Build the brand card, plan content, generate on-brand posts, schedule to your local calendar | Contract; consent for optional fields |
| Google Places pre-fill | Business name, category, city, hours, photos and the place ID | Google Places API | Speed up onboarding | Cached at most 30 days (place ID excepted); only facts you confirm are stored in the brand profile; Google photos are a 30-day preview and are not used in posts unless you upload or approve them |
| Uploaded media | Logos, product photos, past posts, any images or video you add | You | Use as brand assets and references in generation and templates; describe what each photo shows in a sentence, so posts made from it say what is in it | Contract; you are responsible for consent of people shown (DPA) |
| Connected channels | Platform account identifiers, usernames, page IDs, profile pictures, connection health, granted scopes; access tokens (held by the Aggregator during the launch bridge; later held by us as ciphertext only) | The platform, after you complete its OAuth consent screen | Publish approved content; refresh tokens; read insights | Consent (the platform's consent screen) and contract |
| Content and approvals | Drafts, captions, generated images and videos, edits, approve/reject decisions and reason chips, comments, "change something" requests, schedules, per-channel variants, provenance records (model, provider, prompt hash, licence, signer, reviewer, timestamp), C2PA manifests | You, your approvers, the Service | Make, improve and publish content; personalise your Brand Brain; keep the provenance record the law requires | Contract; legal obligation (India SGI rules) |
| Magic-link approvals | Approver's e-mail or phone, hashed link token, expiry, one-time code (optional), each decision with time, IP address and user agent | The brand owner or agency; the approver | Let approvers work without an account; prove who approved what | Contract (with the organisation); legitimate interest in an audit trail (GDPR); DPDP s.7 |
| Enquiries from a business's page (§1.4) | Name, phone number or e-mail, message, the product asked about, the consent sentence and when it was given, a keyed hash of the IP address | The person enquiring | Pass the enquiry to the business; stop abuse of the form | Consent (the ticked sentence), for the business as controller; we are its processor |
| Your own posts on connected accounts | The captions of your recent posts on the Instagram and Facebook accounts you connect (the newest 30 on each), with their dates and links; the summary written from them and your website ("What we know about you") | The platforms, through the connection you made | Write and keep current what we know about your business, so your posts start from it; you can read and rewrite it on the Brand screen | Contract; replaced on each read and deleted with the brand |
| Published-post analytics | External post IDs, reach, impressions, likes, comments counts, saves and similar aggregate metrics as each platform's API returns them (at +1 h, +24 h, +7 d) | The platforms | Show results; feed "what to do more of" into planning | Contract |
| Product usage | Events such as "approved post", "connected channel", screen views, timings (60-second-flow instrumentation), feature flags, crash and error reports | Your use of the product (PostHog, Sentry) | Measure activation and reliability, fix bugs, decide feature flags per organisation | Legitimate interest (GDPR); DPDP consent via the notice; in-app analytics is part of operating the Service and you can opt out of non-essential analytics in Settings |
| Notifications | Push tokens (Expo, Apple, Google), e-mail delivery status, notification preferences, quiet hours | Your device; Resend | Send "posts ready", "needs attention", "client approval needed", "first post live" | Contract; consent for push (OS-level) |
| Support | E-mails to contact@adrologic.com, WhatsApp Business chats with us, what you tell us | You | Help you; product research | Contract; legitimate interest |
| Staff access log | Which staff member viewed your account, when, for how long (max 1 hour), what they did | The Service | Accountability; you can see this log | Legitimate interest; security |
| Demo (no account) | The website URL you paste, IP address and a bot-protection token, the three draft posts | You | Show the product; rate-limit abuse | Legitimate interest; deleted after 7 days |
| WhatsApp add-on (when live) | Your WhatsApp Business Account identifiers, message templates, the phone numbers of your opted-in contacts, opt-in proof (source, timestamp), delivery and quality-rating webhooks, wallet balance | You; Meta | Send template messages you approve to contacts who opted in | We process contacts' data only as your processor (DPA); you must hold the opt-in |
| SEO add-on (when live) | Your website's crawl data, PageSpeed results and, if you connect it, read-only Google Search Console data (queries, pages, clicks) | Your site; Google | Score, issues, recommendations, monthly re-check | Contract; Google API Services User Data Policy, Limited Use (Section 6.4) |
| Consent records for likeness | Name of the person shown, who recorded consent, when, proof | You | Unblock generation of a real person's likeness; evidence | Legal obligation / legitimate interest |
| Audit and security logs | Plan-catalogue changes affecting you, role changes, deletion requests, brand transfers, webhook signatures, access logs | The Service | Security, dispute resolution, regulatory evidence | Legal obligation; legitimate interest |
2.1 What we never collect. Passwords or tokens typed by you (there is no such field), card numbers, government ID numbers, precise geolocation, contacts from your phone, data from platforms you have not connected, and data scraped from any platform we publish to.
2.2 Sensitive data. We do not ask for sensitive personal data. If you enter "religions served" or similar in your brand profile, or upload photos that reveal such things, you do so voluntarily and can remove it at any time.
3. Where your data goes
3.1 Our sub-processors. We use vendors to run the Service. The full list, with what each receives, where it is located and when it starts, is Annex C of the DPA and is kept current at craivis.com/legal/subprocessors. In summary, as of 2026-09-17:
| Function | Vendor | Location | What it sees |
|---|---|---|---|
| Database (all account, brand and content records) | Our own server, hosted by Contabo (Contabo GmbH, Germany) | India | Everything in Section 2, tokens as ciphertext only |
| Web hosting and functions | Our own server, hosted by Contabo (Contabo GmbH, Germany) | India | Requests, rendered stills, session data in transit |
| Media storage, image variants, CDN, bot protection, backups | Cloudflare (R2, Images, Turnstile) | Global, Asia-Pacific jurisdiction hint | Media files, backup files, IP addresses for bot checks |
| Durable workflows (generate, wait for approval, publish at the minute) | Inngest | United States | Post, brand and job identifiers and step state; never tokens |
| Video rendering worker | Our own server, hosted by Contabo (Contabo GmbH, Germany) | India | Media during rendering |
| Publishing aggregator (launch bridge) | Upload-Post | Confirmed at contracting | Your platform tokens, account identifiers, media URLs, captions, AI flag |
| Media generation | fal.ai; WaveSpeed (from Week 6) | United States (fal.ai); WaveSpeed region | Prompts containing brand facts, reference images you approve, generated media |
| Language models | Anthropic; Google (Gemini); DeepSeek (draft-tier planning only, conditional on its terms passing our vendor-terms filter; not before Week 6) | United States (Anthropic, Google); DeepSeek region | Website text, brand facts, captions, plans, moderation inputs (DeepSeek: brand facts in planning prompts only) |
| Google APIs | Google (Places, PageSpeed, Search Console, Vertex AI for Cinematic reels when enabled, Play, FCM) | United States / global | Per API: place lookups, site URLs, Search Console data, push tokens |
| Payments | Razorpay | India | Billing identity, amounts, mandates; card data stays with Razorpay |
| Transactional e-mail | Resend | United States | E-mail address, message content (codes, links, digests) |
| Product analytics and feature flags | PostHog | EU cloud | Pseudonymous user and organisation IDs, events |
| Error monitoring | Sentry | European Union | Error traces, user ID; IP addresses scrubbed; never tokens |
| Push notifications | Expo; Apple; Google | United States / global | Push tokens, notification text (for example "7 posts ready for {brand}") |
| Occasion data feed | Calendarific | — | Receives no personal data (we query dates) |
| Status page | Instatus or BetterStack | — | E-mail of status subscribers only |
| Internal alerts | Slack or WhatsApp (founder alerts on publish failures) | — | Post ID and brand name only |
| LLM tracing (from month 4) | Langfuse | Germany | Prompts and outputs, brand facts |
| Rate limiting (from Week 6 if needed) | Upstash | Region chosen at setup | Identifiers and counters only |
3.2 The platforms you publish to. When you approve a post we send the content, caption, media URL, schedule and the AI-disclosure flag to the platform (Meta for Instagram, Facebook and Threads; LinkedIn; X; Bluesky; Google for Business Profile). The platform then processes it under its privacy policy as an independent controller. We read back the analytics the platform's API returns.
3.3 Agencies and approvers. If an agency manages your brand (with your grant, or because the agency created the brand for you as its client), the agency's members see your brand's data. Approvers see only the posts sent to them.
3.4 Adrologic services. If you press "Request a fix" in the SEO add-on, your name, e-mail, website and the report go to Adrologic's services team as a lead. That is a separate service under separate terms.
3.5 Legal and safety. We disclose data when the law requires (for example to the Data Protection Board of India, to a court, or under a lawful order), to enforce our Terms, to investigate abuse, or to protect people. We tell you unless the law forbids it.
3.6 Business transfer. If Adrologic transfers the CRAIVIS business, your data may transfer with it under this policy; we will notify you.
3.7 We do not sell personal data, we do not share it for cross-context advertising, and we do not run advertising trackers.
4. International transfers
4.1 Adrologic is in India, and so are the servers that hold your account, your brands and your content: we run them ourselves, on infrastructure rented from Contabo, in India. Several vendors we use for generation, publishing, e-mail and payments are in the United States or Germany, with any other vendor location shown per vendor in Section 3.1 and the DPA, Annex C. Some data therefore still leaves India, but the system of record does not.
4.2 DPDP Act. Transfers outside India are permitted except to countries the Central Government restricts by notification. As of the effective date no such restriction affects the countries above. We will move or stop a transfer if a restriction is notified.
4.3 GDPR / UK GDPR. We do not market to or offer residency in the EU or UK in the first 12 months. If we process data of people in the EU or UK (for example an approver in London for an Indian brand), transfers to India and the United States rely on Standard Contractual Clauses (and the UK Addendum) with our sub-processors, as described in the DPA, Annex D.
5. How long we keep it
The single retention table is on the Data Deletion page and is summarised here.
| Data | Kept for | Then |
|---|---|---|
| Account, brand, content, Brand Brain, approvals | While the organisation is active, plus 30 days readable after cancellation | Deleted within 30 days of the deletion clock starting (target 7 days); backups expire within 30 further days |
| Channel tokens | Until you disconnect, revoke on the platform, or the account is deleted | Revoked and deleted immediately; the Aggregator profile is deleted via its API |
| Published-post analytics | With the post | Deleted with the brand |
| Magic-link approval logs (who, when, IP, user agent) | Life of the brand | Deleted with the brand |
| Enquiries from a business's page | Until the business deletes them, or the brand is deleted | Deleted |
| A business page's daily view and tap counts (no visitor data) | Life of the brand | Deleted with the brand |
| Invoices, ledger, refund and mandate records | 8 years from the end of the financial year (Companies Act, 2013 and GST record-keeping) | Deleted |
| Provenance records and C2PA manifests | Life of the asset (they travel with it) | Deleted with the asset |
| Audit rows for brand transfers | Permanently (identifiers only) | — |
| Deletion-request record (confirmation code, status) | 1 year after completion | Deleted |
| Consent records for likeness | Life of the related assets plus 1 year | Deleted |
| Demo runs (no account) | 7 days | Deleted |
| Support e-mails and chats | 2 years | Deleted |
| Error and analytics events | Sentry 90 days; PostHog 1 year | Expire |
| Inactive accounts | No sign-in and no subscription for 12 months | We e-mail you at least 48 hours before erasure, then erase |
6. Platform- and vendor-specific disclosures
6.1 Meta (Instagram, Facebook, Threads, WhatsApp). We receive data from Meta only through Meta's APIs after you grant permission, use it only to provide the Service to you, do not sell it, and delete it as described on the Data Deletion page, including through Meta's Data Deletion Callback when you remove the app in your Facebook or Instagram settings. Meta's Platform Terms allow Meta to audit our handling of platform data; we cooperate. Until our own Meta app is approved, the consent screen shows our white-labelled Aggregator app name and the Aggregator holds the token under its own Meta approvals.
6.2 LinkedIn. Member tokens expire after 60 days and cannot be refreshed; we store no analytics because the member API returns none.
6.3 X. We label the connected account as automated as X's rules require and send only the content you approve.
6.4 Google. CRAIVIS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Search Console data is used only to produce your SEO report and insights, is never used for advertising, and is never transferred except as necessary to provide the feature, for security, or with your consent. Google Places data is cached for at most 30 days (place ID excepted). When YouTube publishing is offered (v2) this policy will add the disclosures the YouTube API Services Terms require.
6.5 Apple and Google Play. The app's privacy "nutrition label" and Play Data safety form are filled from Section 2 of this policy. You can delete your account from inside the app.
7. Cookies and similar technologies
| Cookie / storage | Purpose | Type | Lifetime | Consent |
|---|---|---|---|---|
| Session (Better Auth) | Keep you signed in; CSRF protection | Strictly necessary | Session / up to 30 days | Not required |
| Theme, language, last tab | Remember your preferences | Functional | 1 year | Not required |
| White-label host | Show the agency's branding on its domain | Strictly necessary | Session | Not required |
| Cloudflare Turnstile | Tell humans from bots on the demo and sign-up | Strictly necessary | Short-lived | Not required |
| PostHog (marketing site) | Understand which pages and demos work | Analytics | Up to 1 year | Asked on first visit; off until you accept |
| PostHog (inside the app) | Product analytics, feature flags per organisation | Analytics / functional | Up to 1 year | Part of the Service; non-essential analytics can be switched off in Settings → Privacy |
| Razorpay checkout | Payment session | Strictly necessary (set by Razorpay on its pages) | Per Razorpay | Razorpay's policy |
We do not use advertising cookies or third-party ad pixels. The magic-link pages set only the strictly necessary cookies; a business's public page sets none. You can clear cookies in your browser; strictly necessary ones are set again when you sign in.
8. Your rights
8.1 Under the DPDP Act (India) you can: obtain a summary of the personal data we process about you and how; correct, complete or update it; erase it (subject to retention the law requires); withdraw consent as easily as you gave it; nominate a person to exercise your rights if you die or become incapacitated; and have your grievance heard. Use Settings → Privacy in the product, or write to contact@adrologic.com.
8.2 Under the GDPR / UK GDPR (if it applies to you) you can also: access, rectify, erase, restrict, port, and object to processing based on legitimate interests; and complain to your supervisory authority. We extend the rights in 8.1-8.2 to everyone, whatever their country.
8.3 Withdrawing consent. Withdrawal stops future processing that relied on the consent; it does not undo past processing, and where the data is needed to run your account (for example your sign-in e-mail) withdrawal means closing the account.
8.4 How fast. We acknowledge within 2 business days and answer within 30 days. If the DPDP Rules or your local law set a shorter period, that period applies.
8.5 Verification. We verify requests through your signed-in session or a one-time code to the e-mail or phone on the account. For requests about data we process for an organisation (for example an approver's data), we will refer you to that organisation and help it respond.
8.6 Nominee. You can name a nominee in Settings → Privacy.
9. Security
We use row-level security in the database so one customer's queries can never return another's rows; tokens stored as ciphertext with envelope encryption, decrypted only at publish time and never logged; passkeys and one-time codes instead of passwords; multi-factor authentication for staff and agency owners; signed webhooks; an append-only audit log; secrets in a vault; staff access limited to one-hour logged sessions; encrypted backups (nightly to Cloudflare R2, plus the database's point-in-time recovery); automated cross-tenant tests in our deployment pipeline; and error and uptime monitoring. No system is perfectly secure. If a breach affects your data we follow our breach runbook: we notify you without delay and the Data Protection Board of India within 72 hours as the DPDP Rules require, and any other regulator the law requires.
10. Children
The Service is for businesses and people aged 18 or over. We do not knowingly collect personal data from anyone under 18. If you believe a child has given us data, write to contact@adrologic.com and we will delete it.
11. Automated decisions and AI
We use AI to generate content and to run safety checks; these do not make legal or similarly significant decisions about you. Content is published only after a human approval, or, in Autopilot, after a 24-hour window in which you can veto and with every safety gate still running. The AI Transparency page explains what is AI-generated, how it is labelled and which providers we use. We do not use your data to train general-purpose AI models.
12. Marketing communications
We send service e-mails (codes, links, digests, "needs attention") because they are part of the Service; you control their cadence in Settings. We send product news only if you opt in, and every such e-mail has an unsubscribe link. We never show your brand or results in our marketing without your written consent.
13. Changes
We will post changes here with a new version and date, keep prior versions at craivis.com/legal/privacy/history, and give 30 days' notice by e-mail and in-product for material changes. Changes that follow from a platform or legal requirement may take effect sooner.
14. Contact and grievance
Grievance Officer: Yash Khandelwal, Adrologic Pvt Ltd, 30/160, Sector 3, Pratap Nagar, Sanganer, Jaipur 302033, Rajasthan, e-mail contact@adrologic.com. Support: contact@adrologic.com. If you are not satisfied with our response you may complain to the Data Protection Board of India (the procedure and portal are described on the Board's website) or, where the GDPR applies, to your supervisory authority.