Privacy Policy

1. Who we are and what this covers

SolutionGigs (“we”, “us”) operates the website solutiongigs.in, its free online tools, blog and courses, and the Solvi workspace app at solutiongigs.in/app (“Solvi” is the AI assistant inside that app). This policy explains what personal data we collect, why, how long we keep it, who we share it with, and the rights you have over it.

Our sister product BookMe (bookme.solutiongigs.in) has its own privacy policy covering scheduling and WhatsApp data.

2. Information we collect

2.1 Information you give us

• Files and content you submit to tools — audio, video, images, PDFs, resumes, and documents you upload for conversion, transcription, background removal, scanning, or OCR; and text you paste into tools such as the JSON/SQL formatters, regex tester, readability checker, meeting summarizer, and AI generators.
• Google account details (only if you sign in) — when you use “Sign in with Google” we receive and store your Google account ID, email address, full name, and profile picture URL. Signing in is optional and only needed to post comments, keep a profile, track course access, or manage a paid plan.
• Profile details — a display name you choose to set on your profile page.
• Comments — the text of any comment or reply you post on a blog article, along with the article it belongs to and the time you posted it. Comments are public.
• Waitlist and enquiry details — if you join a waitlist we store the email address and the plan you were interested in. If you email us for support, we keep that correspondence.
• Support enquiries and paid-work requests — if you submit a problem through /fix or an enquiry through /services, we store what you wrote, your name and email, the budget and deadline you selected, and an optional phone or WhatsApp number if you choose to give one, so we can scope the work and reply.
• Signed agreements — if you e-sign an engagement agreement, we store the signed terms, your name, your email, the signature timestamp and the IP address it was signed from. A signed agreement is a legal record and is kept unchanged.
• Questions, answers, job postings and developer profiles — whatever you choose to publish in those sections, together with the account that posted it. All of it is public by design.
• Tips — if you leave a voluntary tip, we store the name, email and optional message you typed into the tip form, so we can send a thank-you and match the receipt to it.
• Solvi workspace data (only if you use /app) — the messages you send to Solvi and its replies, audio you transcribe and the resulting transcripts, meeting notes and summaries, the tasks, reminders and meetings you ask Solvi to create, files you attach, and a small “memory” of preferences you tell Solvi to keep (for example your time zone or a default meeting length). All of it is private to your account and is used only to run your workspace. Voice transcription in the browser never sends audio to us; server-side transcription and every Solvi reply are processed by Groq (see section 5).
• Google Calendar data (only if you connect it) — inside Solvi you can optionally connect your Google Calendar. If you do, we receive the email address of the Google account you connected, a token that lets us act on your calendar, and — each time you open the calendar page — the title, time, location and meeting link of your events for the dates shown. Section 5.2 spells out exactly how this data is used, stored and never shared.
• Jira data (only if you connect it) — inside Solvi you can optionally connect your Atlassian Jira Cloud account. If you do, we receive and store your Atlassian account ID, the email address and display name on that account, the Jira site you chose, and a read-only token. To spot changes between checks we also keep a small snapshot of the issues assigned to you (key, title, status, priority, due date). Section 5.3 spells out exactly how this data is used, kept in step with Atlassian, and erased.
• Payment details — for every payment on this site (a subscription, an approved fix, a services invoice or a tip), processing is done by Razorpay. Your card number, CVV, UPI PIN, netbanking login and wallet credentials are entered inside Razorpay’s own checkout window and go directly to Razorpay. They never reach our servers and we never see them. We store only the payment ID, order ID, amount, currency, status, the email you gave for the receipt and — for subscriptions — a subscription ID.

2.2 Information collected automatically

• Server access logs — IP address, requested URL, referrer, user-agent, and timestamp, used for security, abuse prevention, and debugging.
• Analytics data — Google Analytics 4 records pages viewed, approximate location (country/city level), device and browser type, and how you arrived at the site.
• Advertising data — Google AdSense serves ads on some pages and may use cookies to measure and personalise them.
• Usage counters — if you are signed in, we count how many AI “gigs” you have used against your plan limit, and record the date you last visited.
• Browser storage — we store your sign-in token, your chosen theme (light/dark), and basic tool preferences in your browser’s local storage. These stay on your device.

2.3 What we do not collect

We never ask for or store your card numbers, your postal address, your date of birth, any government ID, or any special-category data (health, biometrics, religion, political views). We do not build advertising profiles from the content of your files. The one exception to the phone rule is the /services enquiry form, which has an optional phone or WhatsApp field — it is used only to call you back about that enquiry, and leaving it blank changes nothing.

3. How we use your information

• To run the tool you asked for — converting, transcribing, summarising, scanning, or formatting what you submitted.
• To authenticate you, keep you signed in, and show your profile and comment history.
• To publish the comments you choose to post.
• To grant and maintain access to paid courses and plans, and to enforce usage limits.
• To reply to support requests and legal or privacy enquiries.
• To keep the service secure, detect abuse, and fix errors.
• To understand aggregate traffic patterns and improve the site.
• To fund the free tools through advertising.

Where GDPR applies, our legal bases are: performance of a contract (running the tools and paid plans), legitimate interests (security, abuse prevention, service improvement), consent (analytics and advertising cookies, waitlist emails), and legal obligation (tax and accounting records for payments).

4. Cookies, analytics and advertising

We set a small number of cookies and browser-storage items ourselves — these keep you signed in and remember your theme preference. We also use the following third-party services that set their own cookies:

• Google Analytics 4 — measures site traffic and page popularity. You can opt out with the Google Analytics Opt-out Browser Add-on.
• Google AdSense — serves the ads that keep the tools free. Google may use cookies to personalise ads. You can manage this at adssettings.google.com.
• Google Sign-In — only loaded when you choose to sign in.

You can block or delete cookies in your browser settings. The tools will continue to work, but you will be signed out and preferences will not be remembered.

5. Third parties we share data with

We do not sell your personal data. We share only what is necessary with the following processors:

Content you submit to an AI-powered tool (meeting summarizer, transcription, AI generators, SQL tutor, prompt tools) is sent to Groq for processing and is subject to Groq’s privacy policy, as are the messages you send to Solvi and the audio you transcribe on the server. We do not send your files to any AI provider unless you use one of those tools, and we never send your Google Calendar data to any AI provider. We may also disclose data if legally required to do so by a valid court order or law-enforcement request.

5.1 Payments in detail

Because this is the part people most want to be sure about, here it is in full. Every rupee and dollar this site takes — a paid plan, an approved fix, a services invoice or a voluntary tip — is processed by Razorpay Software Private Limited, an online payment gateway authorised in India. We are not a payment processor and we do not handle card data.

The Razorpay checkout script is loaded only at the moment you open a payment window, so simply reading an article never contacts them. If the window will not open, an ad blocker is almost always the cause.

5.2 Google user data and the Solvi app

The Solvi workspace at solutiongigs.in/app can optionally connect to your Google Calendar so that Solvi can show your day and book Google Meet calls on your own calendar. This section is our full disclosure for that connection. Connecting is a separate, explicit step — signing in with Google does not grant calendar access, and everything in Solvi works without it.

What we ask for

When you click “Connect Google Calendar”, Google asks you to grant these scopes:

• https://www.googleapis.com/auth/calendar.events — view and edit events on your calendars. Google labels this “See, edit, share, and permanently delete all the calendars you can access using Google Calendar”; in practice we only read events on your primary calendar and create or cancel the events you ask Solvi to create.
• openid and email — so we can show which Google account is connected.

How we use it

• Showing your calendar. When you open the calendar page in Solvi, we fetch the events on your primary calendar for the dates on screen and display their title, start and end time, location and meeting link alongside the tasks and meetings Solvi manages. This is a live read each time; we do not copy your events into our database.
• Booking meetings. When you ask Solvi to schedule a call, it creates one event on your primary calendar with the title, time, description and guest emails you gave it, with a Google Meet link attached. Google, not us, sends the invitations to your guests. If you cancel the meeting through Solvi, we delete that event.
• Nothing else. We do not read your other calendars, do not modify or delete events we did not create, do not read attendee lists of your existing events for any purpose other than display, and do not use calendar data to send you marketing.

What we store

• The refresh token Google issues, encrypted at rest with a key held only on our server, together with the connected account’s email address and the scopes granted. Short-lived access tokens are kept in memory only and are never written to disk.
• For each meeting Solvi books, the Google event ID and Meet link, so Solvi can show, join and cancel it later.
• We store no copy of your other calendar events.

Who can see it

Google Calendar data is shown only to you, inside your signed-in workspace. We do not share it with any third party, do not sell it, do not use it for advertising, do not send it to Groq or any other AI provider, and do not use it to develop, improve or train any model. Access by our staff is limited to what is needed to fix a problem you have reported to us, to comply with the law, or to investigate abuse.

SolutionGigs’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How to disconnect

• In Solvi, open the calendar page and click Disconnect Google. We revoke the token with Google and delete it from our database immediately. Meetings Solvi already booked stay on your calendar; you can remove them in Google Calendar.
• Or remove SolutionGigs at myaccount.google.com/permissions. The next time Solvi tries to use the connection, it will notice the revocation and mark the account as disconnected.
• Deleting your SolutionGigs account deletes the stored token along with everything else.

5.3 Jira data and the Solvi app

The Solvi workspace can optionally connect to your Atlassian Jira Cloud account so that Solvi can show the tickets assigned to you, rank the overdue, blocked and due-soon ones next to your tasks, and answer questions like “what’s on my plate?”. This is opt-in; nothing in Solvi requires Jira, and everything else works without it.

What we ask Atlassian for

When you click “Authorize”, Atlassian asks you to grant these scopes:

• read:jira-work — read issues, projects and boards you can already see in Jira.
• read:jira-user — read your own Jira profile (account ID, name, email) and resolve people named on issues.
• offline_access — a refresh token, so you do not have to re-authorise every hour.

We never ask for write access. Solvi cannot create, edit, transition, comment on or assign issues, and there is no setting that turns that on. If you connect with an API token instead of Authorize, we still only ever read.

What we store, and why

• Who you are on Jira — your Atlassian account ID, display name and email address, copied from your Jira profile when you connect. These let the app show “Connected as…”, keep your connection tied to the right person if your name or email changes, and let us tell Atlassian which accounts we hold data for (see below).
• The token that lets us read Jira on your behalf, encrypted at rest. Short-lived access tokens are kept in memory only.
• Your site — the Jira Cloud site (for example company.atlassian.net) and its ID.
• A snapshot of your assigned issues — key, title, status, priority, due date and last-updated time — refreshed every couple of minutes so Solvi can tell you what changed (a ticket assigned to you, one that became overdue). When one of your tickets changes, Solvi also reads its newest comment so it can tell you “Sarah commented on SCRUM-5” with the first line of what was said; that notification is kept with your other alerts, but issue descriptions, full comment threads and attachments are not stored.

When you ask Solvi about your tickets, it queries Jira live as you (Jira’s own permissions apply, so you only ever see what you could see in Jira) and shows the result to you alone. When Solvi writes a briefing for you (“start my day”, “what needs my attention”), the keys, titles and statuses of the issues it ranked are included in the prompt sent to Groq (section 5) so the wording matches your day; issue descriptions, comments and attachments are never read, and your Atlassian account ID, name and email are never sent to any AI provider. Jira data is never used for advertising, never sold, and never shared with other users.

Keeping in step with Atlassian

Because we store personal data from Atlassian, we take part in Atlassian’s personal data reporting programme: at least every 7 days (or as often as Atlassian instructs), we send Atlassian the list of account IDs we hold and when we last copied each profile. Atlassian tells us which of those accounts have been closed or updated. For a closed account we erase the account ID, name, email and token immediately; for an updated one we refresh our copy of the profile. This is how a deactivated employee, or a changed name, stops showing up in Solvi without anyone having to tell us.

How to disconnect

• In Solvi, open Integrations and click Disconnect Jira. We delete the token and your Atlassian account ID, name and email immediately.
• Or remove SolutionGigs at id.atlassian.com/manage-profile/apps. The next time Solvi tries to use the connection it will notice the revocation, mark the account as disconnected and erase the same fields.
• If your company’s Jira admin deactivates your Atlassian account, Atlassian’s reporting tells us within the cycle above and we erase your details.
• Deleting your SolutionGigs account deletes everything above along with the rest of your data.

6. How long we keep your data

7. Data security

All data in transit is encrypted using TLS 1.2/1.3 (HTTPS). Our servers are protected by firewall rules limiting access to necessary ports only. Uploaded files are stored in directories that are not publicly listable and are served only through unguessable job links. Sign-in sessions use signed JWT tokens. Google Calendar refresh tokens are encrypted at rest and decrypted only in memory to make a request on your behalf. Access to the production database is restricted to the site operator.

No system is perfectly secure. If a breach affects your personal data, we will notify affected users and any required regulator without undue delay.

8. Your rights and how to exercise them

Wherever you live, you can ask us to:

• Access — get a copy of the personal data we hold about you.
• Correct — fix anything inaccurate (you can change your display name yourself on your profile page).
• Delete — permanently erase your account and all associated data, including your comments.
• Object or restrict — ask us to stop a particular use of your data.
• Port — receive your data in a machine-readable format.
• Withdraw consent — for example, by disabling cookies, asking to be removed from a waitlist, or disconnecting Google Calendar from Solvi (see section 5.2).

To make any of these requests, email [email protected] from the email address associated with your account. We will verify your identity and respond within 30 days. There is no charge. If you are in the EU/UK you also have the right to complain to your local data protection authority.

9. International transfers

Our servers and the third-party services listed above are located outside India and the EU, including in the United States. Where personal data is transferred internationally, we rely on the providers’ own safeguards, such as Standard Contractual Clauses.

10. Children’s privacy

SolutionGigs is a general-purpose utility service and is not directed at children under 13. We do not knowingly collect information from children. If you believe a child has provided us with personal data, email us and we will delete it.

11. Changes to this policy

We may update this Privacy Policy from time to time. Changes will be reflected by updating the “last updated” date at the top of this page. Continued use of the service after changes constitutes acceptance of the updated policy.

12. Contact

SolutionGigs is operated by Mohammed Yaseen, Bengaluru, Karnataka, India. For any question about this Privacy Policy, or to make a data access or deletion request, contact us at [email protected]. We aim to reply within 3 working days and resolve requests within 30 days.