DevSphere Voice Affiliate Program Terms

DEVSPHERE VOICE AFFILIATE PROGRAM TERMS

Effective Date: October 7, 2026

Version: 2026-10-v1

These DevSphere Voice Affiliate Program Terms ("Affiliate Terms," "Terms," or "Agreement") govern participation in the DevSphere Voice Affiliate Program ("Affiliate Program" or "Program").

The Program is operated by DevSphere Technologies PVT LTD, doing business through the DevSphere Voice brand ("DevSphere," "DevSphere Voice," "we," "us," or "our").

Business mailing address:

DevSphere Technologies PVT LTD

30 N Gould St, Ste R

Sheridan, WY 82801

United States

Email: [email protected]

Website: https://devspherevoice.com

By applying for, accessing, or participating in the Affiliate Program, you ("Affiliate," "you," or "your") agree to these Terms, the DevSphere Voice Privacy Policy, the then-current Affiliate Commission Schedule when commission functionality is active, and other Program policies expressly incorporated by reference.

1. THE AFFILIATE PROGRAM

The Affiliate Program allows approved Affiliates to promote DevSphere Voice using unique referral links and referral codes and to receive credit for qualifying referrals under the Program rules.

Participation in the Program does not make you an employee, representative, franchisee, partner, joint venturer, fiduciary, legal agent, or authorized sales representative of DevSphere.

You may not enter into agreements on behalf of DevSphere, collect money on behalf of DevSphere, bind DevSphere to an obligation, make commitments for DevSphere, or represent that you have authority to do so.

Your relationship with DevSphere is that of an independent participant in the Affiliate Program.

2. ELIGIBILITY AND LEGAL CAPACITY

DevSphere does not impose a specific Program minimum age.

However, you may participate only if you have the legal capacity under the laws applicable to you to enter into and comply with this Agreement.

If applicable law requires the authorization, consent, supervision, or participation of a parent, guardian, business owner, representative, or other legally responsible person, you are responsible for obtaining that authorization before applying or participating.

You must provide accurate, current, and complete information in your application and Affiliate account.

3. BUSINESS AND ORGANIZATION APPLICANTS

If you apply or participate on behalf of a corporation, company, partnership, agency, organization, or other legal entity, you represent and warrant that you are authorized to bind that entity to these Terms.

In that case, references to "Affiliate," "you," and "your" include both you and the entity on whose behalf you participate.

4. EXISTING CUSTOMERS AND CONFLICTING ACCOUNT TYPES

Existing DevSphere customers and users of DevSphere customer accounts are not eligible to enroll in the Affiliate Program unless DevSphere expressly approves an exception in writing.

An applicant whose email address, verified identity, organization membership, customer account, pending customer invitation, administrative account, staff account, or other restricted DevSphere identity conflicts with an existing DevSphere record may be prevented from creating or activating an Affiliate account.

Customer referral functionality may be governed separately from the Affiliate Program.

An Affiliate who validly joins the Program before later becoming a DevSphere customer may continue to hold an Affiliate account unless DevSphere determines otherwise. The Affiliate's own purchases remain subject to the self-referral restrictions in these Terms.

If an Affiliate identity later conflicts with a DevSphere staff or administrative identity, DevSphere may restrict or suspend Affiliate workspace access to preserve account and security separation.

5. APPLICATION AND APPROVAL

Submitting an Affiliate application does not guarantee acceptance.

Applications may remain in Pending status while DevSphere verifies the applicant's email address, Terms acceptance, account eligibility, and other Program requirements.

DevSphere reviews Affiliate applications before activation.

An Affiliate may not use active referral tools until:

(a) the email address has been confirmed;

(b) the current Affiliate Terms have been accepted;

(c) the application has been approved; and

(d) the Affiliate account is Active.

DevSphere may approve or reject applications in its reasonable discretion, subject to applicable law.

DevSphere is not required to disclose confidential review criteria or internal risk assessments.

Under the current Program policy, rejection is final unless DevSphere expressly authorizes reapplication.

6. ACCOUNT STATUS

Affiliate accounts may have statuses including:

Pending;

Active;

Suspended; or

Rejected.

Only an Active Affiliate who has accepted the current required Terms may create new valid Affiliate attribution.

Historical referral, Terms, status, audit, and conversion evidence may be retained after a status change where permitted or required by law.

7. ACCOUNT SECURITY

You are responsible for maintaining the confidentiality and security of your Affiliate account credentials.

You must promptly notify DevSphere if you know or reasonably suspect that your Affiliate account has been accessed without authorization.

You may not sell, rent, transfer, lend, sublicense, or share your Affiliate account or authentication credentials without DevSphere's written permission.

You are responsible for activity conducted through your Affiliate account to the extent permitted by applicable law.

8. ACCEPTANCE OF AFFILIATE TERMS

You must accept the current published version of these Terms before participating in the Program.

DevSphere may maintain durable evidence of acceptance, including:

the Terms version;

the Terms title;

a document fingerprint or SHA-256 hash;

the acceptance date and time;

the associated account identity; and

the acceptance source.

Previous Terms acceptance records may remain preserved as historical evidence.

If DevSphere publishes a new version and requires reacceptance, referral links, referral counts, or other Affiliate tools may be temporarily unavailable until you accept the new version.

9. REFERRAL CODE AND REFERRAL URL

Approved Affiliates receive a server-generated referral code and corresponding referral URL.

Referral codes are not derived from internal database identifiers and are intended to be publicly shareable.

Your referral code normally remains stable unless DevSphere determines that it must be disabled, replaced, or retired for security, legal, fraud-prevention, technical, or Program reasons.

You may share your referral URL only through lawful methods consistent with these Terms.

You may not manipulate a referral URL in a way designed to falsify attribution, impersonate another Affiliate, bypass Program rules, or misrepresent the destination.

10. FORWARDED REFERRAL LINKS

Referral links are public and may be forwarded by recipients.

A prospective customer who receives and validly uses a forwarded Affiliate referral link may still be attributed to the Affiliate who owns that link, subject to all other Program eligibility and attribution requirements.

11. REFERRAL TRACKING

DevSphere uses first-party referral tracking.

The Program may place a random opaque browser token to recognize a browser that has interacted with valid Affiliate referral links.

The browser token itself does not contain the Affiliate's identity or referral code.

Only a protected representation of that token may be stored server-side.

The Affiliate attribution system does not use IP-address-based identity, user-agent identity, or device fingerprinting as the method for identifying one Affiliate referral browser.

Normal security, infrastructure, fraud-prevention, and website logs may still be processed independently in accordance with DevSphere's Privacy Policy and applicable law.

Referral and conversion eligibility is determined from DevSphere's server-side Program records. Browser data alone is not authoritative.

12. COOKIE AND BROWSER LIMITATIONS

A browser may remain recognized for an extended period through a first-party referral token.

The recognition lifetime is separate from the commission attribution window.

If a visitor clears cookies, changes browsers or devices, uses private browsing, deletes site storage, or otherwise removes the referral token, the Program may treat that browser context as new.

DevSphere is not required to use invasive fingerprinting or similar technology to reconnect deleted browser identities.

13. LAST VALID CLICK ATTRIBUTION

Unless the current Affiliate Commission Schedule expressly provides otherwise, the Program uses a last valid click attribution model.

The most recent valid Affiliate referral click becomes the active Affiliate context for a qualifying action.

A later valid Affiliate click replaces an earlier valid Affiliate context.

An invalid interaction does not replace a valid context.

Examples of interactions that do not establish a new valid Affiliate context include:

malformed referral codes;

unknown referral codes;

links belonging to Pending Affiliates;

links belonging to Suspended Affiliates;

links belonging to Rejected Affiliates;

links belonging to Affiliates who have not accepted required current Terms;

automated link previews;

bots;

crawlers;

scanners;

browser prefetch activity; and

other interactions DevSphere reasonably determines are not genuine valid referral clicks.

14. THIRTY-DAY ATTRIBUTION WINDOW

The standard Affiliate attribution window is 30 days from the browser's most recent valid Affiliate click.

Each new valid Affiliate click renews the 30-day attribution window.

If the most recent valid click is more than 30 days old when the qualifying action occurs, no Affiliate attribution is created for that action unless the then-current Commission Schedule expressly provides otherwise.

The Program does not fall back to an older Affiliate merely because the most recent Affiliate later becomes ineligible.

A fresh valid click after an expired window may begin a new 30-day attribution window.

15. DISTINCT VISITORS AND REPEATED CLICKS

Where the same recognized browser repeatedly visits the same Affiliate's link, the Affiliate dashboard may count that browser as one distinct visitor while separately recording repeated click activity.

For example, if the same recognized browser clicks Affiliate A, then Affiliate B, then Affiliate A again, the Program may record:

one distinct visitor for Affiliate A;

one distinct visitor for Affiliate B; and

Affiliate A as the active context after the final valid click.

A different browser or a browser whose referral identity can no longer be recognized may be counted as another visitor.

16. SERVER-SIDE ATTRIBUTION IS AUTHORITATIVE

Referral attribution shown by DevSphere's validated server records controls for Program purposes.

An Affiliate ID, referral code, commission claim, or attribution value supplied manually through browser forms, query parameters, client-side code, or other unverified sources does not override server-side Program records.

DevSphere may preserve immutable evidence identifying the referral visit and qualifying click that resulted in an attribution.

17. REFERRAL STAGES

DevSphere may record Affiliate referral activity at different stages, including:

link visit;

demo request;

demo booking;

checkout initiation;

qualified checkout;

verified customer conversion; or

other Program stages introduced in the future.

A referral-stage record does not necessarily mean that a commission has been earned.

18. QUALIFYING REFERRALS

A referral may become eligible for commission only when it satisfies all requirements in:

these Terms;

the applicable Affiliate Commission Schedule;

the server-side attribution rules;

the payment and conversion requirements; and

any other Program criteria applicable at the time.

A click, visitor, lead, demo request, demo booking, checkout, or payment attempt does not by itself guarantee a commission.

19. EXISTING CUSTOMERS

A referral involving an existing DevSphere customer is generally not eligible as a new-customer Affiliate referral.

DevSphere may treat a person or organization as an existing customer where the referral identity matches or is already associated with:

an existing DevSphere organization;

an organization member;

an organization contact;

a customer account; or

other qualifying customer evidence.

The validated server-side record controls this determination.

20. EXISTING ORGANIZATIONS

An organization that existed before the qualifying Affiliate referral interaction may be treated as an existing organization and may be ineligible for a new-customer Affiliate commission.

DevSphere may use server-side organization creation and referral timestamps to determine eligibility.

21. SELF-REFERRALS

Self-referrals are prohibited and are not eligible for commission.

A referral may be treated as a self-referral if the referred customer email or verified account identity matches the Affiliate's email or verified identity.

You must not attempt to circumvent this restriction through:

alternate email addresses;

nominees;

controlled businesses;

intermediaries;

family-member arrangements;

fabricated customer identities;

accounts created primarily to obtain Affiliate commission; or

other arrangements whose primary purpose is to obtain a commission for your own purchase or controlled transaction.

DevSphere may investigate suspected self-referral circumvention.

22. ADMIN-CREATED CUSTOMERS

Customers created independently by DevSphere administrators without qualifying Affiliate referral evidence are not attributed to an Affiliate merely because the customer or Affiliate later claims an Affiliate relationship.

Validated Program attribution evidence controls.

23. AFFILIATE ATTRIBUTION AND SALES-CLOSER ATTRIBUTION

Affiliate attribution and DevSphere sales-closer attribution are separate systems.

A qualifying transaction may contain legitimate Affiliate attribution and legitimate closer attribution at the same time.

Neither form of attribution automatically cancels or overwrites the other.

Internal compensation for a sales closer is separate from Affiliate commission.

24. AFFILIATE COMMISSION SCHEDULE

Commercial Affiliate values are governed by the then-current DevSphere Voice Affiliate Commission Schedule ("Commission Schedule").

The Commission Schedule is incorporated into these Terms by reference.

When commission functionality is activated, the Commission Schedule will be made available through one or more official DevSphere surfaces, which may include:

the public Affiliate Program page;

the Affiliate dashboard;

Program documentation; or

another official DevSphere Program notice.

The initial intended public commission tier structure is:

Tier 1 — 12%

Tier 2 — 10%

Tier 3 — 7%

The current published Commission Schedule controls where it differs from an earlier schedule.

25. TIER QUALIFICATION

Commission tier qualification criteria may be defined and updated in the current Commission Schedule.

Criteria may include legitimate Program factors such as referral quality, verified conversion performance, Program participation, compliance history, or other published requirements.

DevSphere will not use unpublished retroactive criteria to reduce a commission that had already become earned and payable under the applicable schedule.

An Affiliate's current tier and applicable percentage may be displayed in the Affiliate dashboard once commission functionality is enabled.

26. ADMIN-CONFIGURABLE PROGRAM VALUES

DevSphere may configure and publish Program values including:

tier names;

commission percentages;

tier qualification descriptions;

Commission Activation Date;

effective date;

validation period;

payout cycle;

minimum payout threshold;

supported payout methods; and

other commercial Program settings.

Changes apply prospectively from the effective date stated in the applicable Commission Schedule unless applicable law requires otherwise.

Historical schedules may be retained for audit, reconciliation, and dispute purposes.

27. COMMISSION ACTIVATION DATE

Commission eligibility begins on the Commission Activation Date displayed in the then-current Commission Schedule.

Before a Commission Activation Date has been published, the Program may record referral clicks, visitors, leads, demo requests, bookings, checkouts, customer conversions, and other attribution activity for testing, analytics, operational validation, and historical evidence.

Such pre-activation activity does not create a payable commission unless DevSphere expressly states otherwise in the applicable Commission Schedule.

No Affiliate becomes entitled to retroactive commission merely because referral or attribution activity was recorded before commission functionality or the applicable Commission Schedule became active.

28. COMMISSIONABLE REVENUE

Unless the applicable Commission Schedule expressly states otherwise, commission applies only to the first eligible subscription payment successfully collected from a qualifying newly referred customer.

Commissionable revenue excludes:

setup fees;

implementation fees;

onboarding fees;

add-ons;

optional integrations;

usage packs;

voice usage charges;

SMS usage charges;

usage overages;

taxes;

government fees;

non-subscription charges;

credits;

promotional credits;

refunded amounts;

charged-back amounts;

disputed amounts;

fraudulent payments;

failed payments;

test transactions; and

other amounts specifically excluded by the applicable Commission Schedule.

Where a discount or coupon applies, commission may be calculated on the eligible net subscription amount actually collected rather than the undiscounted list price.

29. FIRST ELIGIBLE SUBSCRIPTION PAYMENT ONLY

Under the initial Program model, Affiliate commission applies to the first eligible subscription payment only.

Subsequent recurring subscription renewals do not generate additional Affiliate commission unless the applicable Commission Schedule expressly states otherwise.

30. WHEN A COMMISSION BECOMES ELIGIBLE

A commission is not earned merely because a visitor:

clicks a referral link;

submits a form;

books a demo;

begins checkout;

enters payment information; or

appears as referral activity in the Affiliate dashboard.

Commission eligibility requires a qualifying, successfully collected payment and verified attribution under the applicable Program rules.

31. COMMISSION VALIDATION PERIOD

Unless the current Commission Schedule states otherwise, an otherwise qualifying commission remains pending for 30 days after the applicable eligible subscription payment is successfully collected.

During this validation period, DevSphere may verify:

payment status;

Affiliate attribution;

customer eligibility;

refunds;

payment reversals;

chargebacks;

disputes;

fraud;

duplicate activity;

self-referrals;

existing-customer status;

Program compliance; and

other conditions affecting commission eligibility.

A pending commission does not become payable until the applicable validation period has completed and the commission remains eligible.

32. REFUNDS, CHARGEBACKS, DISPUTES, AND REVERSALS

If a qualifying customer payment is later:

refunded;

reversed;

charged back;

successfully disputed;

found fraudulent;

cancelled under circumstances that invalidate eligibility; or

otherwise returned,

the related Affiliate commission may be cancelled or reversed.

If the commission has already been paid, DevSphere may offset the reversed commission against future Affiliate payouts where permitted by applicable law.

If no future amounts are available for offset, DevSphere may request repayment of an improperly paid or subsequently reversed commission.

DevSphere will not intentionally reverse a valid commission solely because a customer later chooses not to renew after the qualifying first payment has become final, unless the original payment or attribution itself becomes ineligible.

33. PAYOUT CYCLE

Subject to commission activation, validation, applicable payout thresholds, payment-provider processing, tax/compliance requirements, and these Terms, Affiliate payouts are intended to be processed on the Program's 15th / 30th payout cycle.

This generally means eligible payouts may be processed on or around the 15th and 30th of each month.

If an applicable date does not exist in that month or falls on a weekend, bank holiday, provider outage, non-processing day, or other impractical settlement date, DevSphere may process the payout on the nearest practical business day.

A processing date is not a guarantee that funds will arrive in every financial account on that exact date.

34. MINIMUM PAYOUT THRESHOLD

Any minimum payout threshold will be stated in the current Commission Schedule.

If no threshold is published, these Terms do not create a separate guaranteed threshold.

Amounts below an applicable threshold may roll forward until the threshold is satisfied, subject to applicable law and Program rules.

35. PAYOUT METHODS

Approved payout methods may include:

bank transfer; and

supported cryptocurrency payout methods,

when such methods are enabled by DevSphere.

Available payout methods may vary by:

country;

payment provider;

currency;

compliance requirements;

Affiliate status; and

Program configuration.

You must provide complete and accurate payout information.

DevSphere is not responsible for losses caused by materially incorrect payout information supplied by you.

Provider, network, intermediary-bank, blockchain, currency-conversion, or similar fees may apply where disclosed.

36. PAYOUT INFORMATION SECURITY

DevSphere may require additional verification when payout information is created or changed.

Changes to:

bank account information;

cryptocurrency addresses;

wallet addresses;

payout provider accounts;

beneficiary names;

account ownership information; or

other sensitive payout details

may trigger a temporary security hold before payment is released.

DevSphere may delay a payout where it reasonably suspects:

account compromise;

unauthorized access;

fraud;

suspicious payout changes; or

other material security concerns.

This protection is intended to reduce the risk of Affiliate funds being redirected through account takeover or fraud.

37. COMMISSION AND PAYOUT DISPUTES

You should review Affiliate dashboard and payout information promptly.

An Affiliate must notify DevSphere of a suspected referral, attribution, commission, or payout discrepancy within 60 days after the relevant transaction, commission entry, or payout information becomes available in the Affiliate dashboard or Program statement.

DevSphere will use reasonable available records to investigate timely disputes.

DevSphere may decline late requests where records can no longer reasonably be investigated, subject to any non-waivable rights under applicable law.

38. TAXES

Affiliates are responsible for determining and satisfying taxes, duties, reporting requirements, and other fiscal obligations applicable to Affiliate income.

DevSphere may request tax or identification documentation reasonably required for payment or legal compliance.

DevSphere may withhold amounts where required by applicable law.

Nothing in the Program creates an employee tax or benefits relationship between the Affiliate and DevSphere.

39. AFFILIATE DISCLOSURE REQUIREMENT

When promoting or endorsing DevSphere Voice, you must clearly and conspicuously disclose your Affiliate or compensated relationship wherever applicable law requires such disclosure.

The disclosure should be easy for an ordinary viewer, reader, listener, or customer to notice and understand.

It should appear sufficiently close to the applicable recommendation, endorsement, or referral link when required.

Acceptable disclosure wording may include:

"I may earn a commission if you purchase through my DevSphere Voice referral link."

Using only unclear wording such as "affiliate link," "partner," or another term that does not reasonably explain the financial relationship may not be sufficient in every context.

You are responsible for complying with advertising and endorsement laws applicable to your audience and marketing channel.

40. TRUTHFUL MARKETING

All Affiliate marketing must be truthful, accurate, and not misleading.

You may describe DevSphere Voice only using claims reasonably supported by:

the official DevSphere Voice website;

approved Program materials;

published documentation;

current product information; or

other materials expressly authorized by DevSphere.

You may not invent, exaggerate, guarantee, or misrepresent:

features;

integrations;

pricing;

availability;

performance;

legal or regulatory compliance;

revenue;

cost savings;

conversion rates;

lead volume;

customer outcomes; or

other product or commercial claims.

You may not claim that DevSphere Voice guarantees revenue, sales, leads, profits, savings, or any particular business result.

41. PROHIBITED MARKETING CONDUCT

You may not engage in:

spam;

fraudulent promotion;

false advertising;

deceptive advertising;

cookie stuffing;

forced attribution;

artificial traffic;

click manipulation;

bot activity;

fabricated referrals;

fake leads;

fake reviews;

misleading testimonials;

phishing;

malware;

hidden redirects;

hidden frames;

unauthorized scripts;

false scarcity;

identity impersonation; or

other deceptive or unlawful practices.

You may not knowingly submit false customer information or encourage another person to do so.

42. NO SUB-AFFILIATE OR DOWNSTREAM NETWORK WITHOUT APPROVAL

You may not create, operate, recruit for, or manage a:

sub-affiliate network;

multi-level referral arrangement;

downstream Affiliate network;

commission-sharing network;

reseller chain; or

similar third-party distribution system

using the DevSphere Affiliate Program without DevSphere's prior written authorization.

Your referral code is issued to you and may not be commercially sublicensed or redistributed as part of an unauthorized Affiliate network.

43. EMAIL MARKETING

If you promote DevSphere Voice by email, you must comply with applicable commercial-email laws.

Where U.S. CAN-SPAM requirements apply, among other applicable requirements, you must not use materially false sender information or deceptive subject lines and must comply with applicable commercial-message identification, postal-address, and opt-out requirements.

You may not use unlawfully obtained or harvested mailing lists.

You are responsible for your own mailing lists, consent practices, suppression lists, and campaigns.

44. SOCIAL MEDIA AND INFLUENCER MARKETING

You may promote DevSphere Voice through lawful social-media channels, websites, video, newsletters, podcasts, communities, or other permitted media.

You must comply with the applicable platform's rules.

Any material connection to DevSphere, including Affiliate compensation, must be disclosed where applicable.

Reviews and testimonials must reflect genuine experiences and may not be fabricated or manipulated to create a misleading impression.

45. PAID ADVERTISING AND SEARCH MARKETING

Unless DevSphere gives prior written authorization, Affiliates may not bid on, purchase, or target paid-search keywords that consist of or confusingly resemble:

DevSphere;

DevSphere Voice;

DevSphere Technologies;

official DevSphere product names;

common misspellings of DevSphere trademarks; or

other brand terms identified by DevSphere.

You may not create paid advertisements that falsely appear to be official DevSphere advertisements.

You may not use misleading display URLs or advertisements designed to cause users to believe that an Affiliate site is owned or operated by DevSphere.

46. DOMAIN NAMES AND SOCIAL IDENTITIES

Without written authorization, you may not register or use a domain name, subdomain, social-media username, account name, business name, application name, or other identifier that contains or confusingly resembles a DevSphere trademark in a manner likely to imply official ownership, authorization, or operation by DevSphere.

47. DEVSPHERE INTELLECTUAL PROPERTY

DevSphere retains all rights in its:

names;

trademarks;

logos;

brand assets;

designs;

software;

documentation;

website content;

marketing assets; and

other intellectual property.

While your Affiliate account remains authorized, DevSphere grants you a limited, revocable, non-exclusive, non-transferable license to use Affiliate marketing materials expressly supplied or approved for Program promotion.

You may not:

claim ownership;

sell DevSphere intellectual property;

sublicense it;

materially distort it;

use it deceptively; or

continue using it after your authorization ends.

Any goodwill from authorized use of DevSphere trademarks belongs to DevSphere.

48. COUPONS, PRICING, AND PROMOTIONS

Affiliates may advertise only pricing, offers, coupons, and promotions currently authorized by DevSphere.

You may not:

invent coupons;

advertise unauthorized discounts;

misrepresent pricing; or

promote expired offers as current.

Official DevSphere server-authoritative checkout pricing controls over Affiliate marketing materials.

49. NO COLLECTION OF DEVSPHERE CUSTOMER PAYMENTS

Unless DevSphere expressly authorizes otherwise in writing, Affiliates may not collect:

subscriptions;

setup fees;

deposits;

implementation payments; or

other customer funds

on behalf of DevSphere.

Customers should complete purchases through official DevSphere channels.

50. CUSTOMER DATA AND PRIVACY

You must handle personal information lawfully.

You may not:

scrape;

purchase unlawfully;

resell;

misuse;

improperly disclose; or

improperly collect

personal information in connection with the Program.

Where practical, prospective customers should be directed to official DevSphere forms, demo-booking pages, and checkout flows.

You must not request, obtain, or store DevSphere customer passwords, card credentials, private platform credentials, API secrets, or similar sensitive information.

DevSphere processes Program information in accordance with its Privacy Policy and applicable law.

51. CONFIDENTIAL INFORMATION

You may not disclose or misuse information that DevSphere identifies as confidential or that a reasonable person would understand to be confidential.

Confidential information may include:

non-public roadmaps;

security details;

credentials;

internal metrics;

customer information;

unpublished products;

commercial strategies;

internal pricing;

technical architecture; and

other non-public business information.

This restriction does not apply to information that:

became public without your breach;

was lawfully known without a confidentiality restriction;

was lawfully received from another source; or

must be disclosed by law.

Where legally permitted, you should provide reasonable notice before a compelled disclosure.

52. AFFILIATE DASHBOARD METRICS

The Affiliate dashboard may display non-financial and financial Program metrics.

Examples may include:

link visitors;

click activity;

demo requests;

checkouts started;

new customers;

pending commissions;

validated commissions; or

other Program activity.

Metrics may be subject to:

deduplication;

fraud screening;

validation;

attribution rules;

refunds;

payment status; and

technical processing.

Dashboard activity does not necessarily equal payable commission.

Validated DevSphere server records control in the event of a reasonable discrepancy.

53. FRAUD AND PROGRAM ABUSE

DevSphere may investigate suspected Affiliate fraud or abuse.

Examples include:

fabricated customers;

self-referral schemes;

unauthorized automation;

artificial clicks;

coordinated attribution manipulation;

payment fraud;

chargeback abuse;

false identities;

misleading advertising;

unauthorized Affiliate networks; and

other conduct intended to obtain Program benefits improperly.

DevSphere may hold disputed commissions or payouts during a reasonable good-faith investigation.

Fraudulent or abusive conduct may result in suspension, termination, loss of affected unpaid commissions, and other available remedies, subject to applicable law.

54. SUSPENSION

DevSphere may suspend an Affiliate account for reasons including:

Program violations;

suspected fraud;

security concerns;

compliance issues;

required Terms reacceptance;

misleading marketing;

payment concerns; or

other legitimate Program risks.

While suspended:

new Affiliate links may not create valid new attribution;

Affiliate tools may be restricted;

dashboard information may be limited; and

payments may be held where appropriate.

Historical evidence remains preserved where permitted by law.

DevSphere may reactivate a suspended account where appropriate.

55. REACTIVATION

A suspended Affiliate may be reactivated by DevSphere.

Reactivation does not retroactively convert invalid referral activity recorded during the suspension period into qualifying commission unless DevSphere expressly determines otherwise.

Historical suspension and reactivation events may be retained.

56. REJECTION

A Pending Affiliate application may be rejected.

Under the current Program policy, rejection is final unless DevSphere expressly permits reapplication.

A Rejected Affiliate cannot create valid new Affiliate referral attribution.

57. TERMINATION

Either party may end the Affiliate relationship, subject to obligations already accrued.

DevSphere may terminate participation immediately for reasons including:

fraud;

material breach;

unlawful conduct;

repeated policy violations;

deceptive marketing;

misuse of intellectual property;

security abuse;

unauthorized Affiliate networks; or

other serious Program misconduct.

After termination, you must stop representing yourself as a DevSphere Affiliate and discontinue unauthorized use of DevSphere Affiliate materials.

58. EFFECT OF TERMINATION ON REFERRALS AND COMMISSIONS

Referral activity occurring after termination is not eligible.

Termination does not automatically invalidate a commission validly earned before termination unless the commission is otherwise subject to:

fraud;

refund;

chargeback;

payment reversal;

self-referral;

Program violation;

customer ineligibility; or

another valid disqualification.

DevSphere may withhold amounts subject to a legitimate unresolved fraud, payment, compliance, or attribution investigation.

59. HISTORICAL RECORDS AND RETENTION

Termination, rejection, suspension, or account closure does not automatically erase Program records.

DevSphere may retain records reasonably necessary for:

contract enforcement;

attribution;

fraud prevention;

tax;

account security;

audit;

legal compliance;

payment reconciliation;

Terms acceptance; and

dispute resolution,

subject to applicable privacy and data-protection law.

Requests concerning personal information will be handled in accordance with DevSphere's Privacy Policy and applicable legal requirements.

60. PROGRAM CHANGES

DevSphere may modify:

Program features;

referral mechanics;

marketing assets;

operational procedures;

Affiliate tiers;

commercial settings;

supported payment methods;

fraud controls; and

other Program functionality.

Commercial changes will generally apply prospectively from their stated effective date.

Nothing in this section permits DevSphere to retroactively reduce a commission that had already become earned and payable under the applicable schedule, except where a valid reversal, correction, fraud determination, or other applicable provision permits it.

61. COMMISSION SCHEDULE CHANGES

The Commission Schedule may be updated independently from these Affiliate Terms.

Each new Schedule should identify an effective date.

A new Schedule applies prospectively according to its terms.

A change in a future commission rate will not, solely because of that rate change, reduce a commission that already became earned under a prior applicable Commission Schedule.

Historical Commission Schedules may be retained.

62. CHANGES TO THESE AFFILIATE TERMS

DevSphere may publish a new version of these Terms.

Where a new Terms version requires Affiliate acceptance, DevSphere may restrict referral tools until the Affiliate accepts the updated version.

Previous acceptance evidence may remain preserved.

Your continued Program participation may be conditioned on acceptance of the then-current required Terms.

63. PROGRAM AVAILABILITY

DevSphere does not guarantee uninterrupted availability of:

the Affiliate Program;

Affiliate links;

tracking;

dashboards;

email services;

payment services; or

other Program features.

Maintenance, third-party outages, security incidents, legal requirements, payment-provider interruptions, and technical changes may affect availability.

DevSphere will use reasonable efforts to maintain accurate Program records but does not guarantee error-free tracking.

64. NO GUARANTEE OF EARNINGS

DevSphere does not guarantee:

traffic;

visitors;

leads;

demo requests;

customers;

conversions;

revenue;

commissions; or

profit.

Past performance does not guarantee future results.

You are responsible for your own marketing costs, business expenses, strategy, and decisions.

65. INDEPENDENT CONTRACTOR

The Affiliate is an independent contractor.

Nothing in this Agreement creates:

employment;

partnership;

franchise;

agency;

fiduciary relationship; or

joint venture.

Affiliates are not entitled to employee compensation, employment benefits, insurance, paid leave, retirement benefits, or other employee rights solely because they participate in the Program.

66. COMPLIANCE WITH LAW

You must comply with laws applicable to your Affiliate activity, including where applicable:

advertising laws;

endorsement rules;

consumer-protection requirements;

privacy laws;

commercial-communications laws;

anti-spam laws;

intellectual-property laws;

tax laws;

sanctions requirements;

export-control requirements; and

other applicable regulations.

If applicable law prevents you from lawfully conducting an Affiliate activity, you must stop the affected activity.

67. SANCTIONS AND PAYMENT COMPLIANCE

DevSphere may restrict participation or payment where required by:

sanctions laws;

financial regulations;

payment-provider requirements;

anti-fraud controls;

identity-verification requirements; or

other applicable legal obligations.

DevSphere does not guarantee that every payout method is available in every country.

68. RECORDS AND INVESTIGATION

DevSphere may maintain reasonable Program records necessary for legitimate business and legal purposes.

Where reasonably necessary to investigate suspected Program abuse, DevSphere may request supporting information regarding your Affiliate activities.

You agree to cooperate reasonably with legitimate investigations concerning potential violations of these Terms.

69. ELECTRONIC COMMUNICATIONS

You agree that DevSphere may send Affiliate Program communications electronically, including through:

email;

the Affiliate dashboard;

administrative notices; or

the DevSphere website.

Electronic acceptance of these Terms is intended to evidence your agreement to the applicable Terms version.

You are responsible for maintaining access to the email address associated with your Affiliate account.

70. DISCLAIMER OF WARRANTIES

To the maximum extent permitted by applicable law, the Affiliate Program and related tools are provided on an "as is" and "as available" basis.

DevSphere does not warrant that the Program will:

operate uninterrupted;

be error-free;

remain permanently available; or

produce any particular commercial result.

Nothing in these Terms excludes warranties or statutory rights that cannot lawfully be excluded.

71. LIMITATION OF LIABILITY

To the maximum extent permitted by applicable law, DevSphere will not be liable for indirect, incidental, special, exemplary, punitive, or consequential damages arising from the Affiliate Program, including lost profit, lost opportunity, lost goodwill, or lost data.

To the maximum extent permitted by law, DevSphere's aggregate liability arising specifically from the Affiliate Program will not exceed the greater of:

(a) USD $100; or

(b) the commissions actually paid or payable to the Affiliate during the six months immediately preceding the event giving rise to the claim.

This limitation does not apply where liability cannot lawfully be excluded or limited.

72. INDEMNIFICATION

To the extent permitted by applicable law, you agree to defend, indemnify, and hold harmless DevSphere Technologies PVT LTD and its applicable affiliates, directors, officers, employees, representatives, and service providers from third-party claims, damages, penalties, liabilities, losses, and reasonable costs arising from:

your unlawful Affiliate marketing;

your breach of these Terms;

your infringement of third-party rights;

spam or unlawful communications;

misleading claims;

misuse of personal information;

Affiliate fraud; or

other wrongful Affiliate conduct.

DevSphere will provide reasonable notice of a covered claim where practicable.

73. FORCE MAJEURE

Neither party will be responsible for delay or failure caused by circumstances beyond reasonable control, including:

natural disasters;

war;

civil unrest;

government action;

widespread telecommunications failures;

cloud-provider failures;

payment-network outages; or

comparable extraordinary events,

except for obligations that cannot lawfully be excused.

74. ASSIGNMENT

You may not transfer or assign:

your Affiliate account;

referral code;

Program rights; or

obligations under these Terms

without DevSphere's prior written consent.

DevSphere may assign this Agreement in connection with a merger, acquisition, financing, corporate restructuring, sale of assets, or transfer of the DevSphere Voice business, subject to applicable law.

75. NO WAIVER

Failure to enforce a provision of these Terms does not waive the right to enforce that provision or any other provision later.

76. SEVERABILITY

If a provision of these Terms is determined to be invalid or unenforceable, the remaining provisions remain effective to the maximum extent permitted by law.

The affected provision will be interpreted or limited as necessary to preserve its lawful purpose where possible.

77. ENTIRE AGREEMENT

These Affiliate Terms, the applicable Commission Schedule, the DevSphere Voice Privacy Policy, and other Program rules expressly incorporated by reference constitute the agreement governing Affiliate participation.

They supersede prior representations concerning the same subject matter except for obligations expressly stated to survive.

78. GOVERNING LAW

These Terms are governed by the laws of the State of Wyoming, United States, together with applicable United States federal law, without regard to conflict-of-laws principles, except where mandatory applicable law requires otherwise.

79. JURISDICTION

Subject to mandatory rights that cannot lawfully be waived, disputes arising from these Terms will be subject to the jurisdiction of the appropriate state courts located in or serving Sheridan County, Wyoming and, where federal jurisdiction exists, the appropriate federal courts serving Wyoming.

Each party consents to such jurisdiction to the extent permitted by law.

80. INTERNATIONAL AFFILIATES

The Affiliate Program may be available outside the United States.

International Affiliates are responsible for complying with laws applicable to their own location, audience, marketing activity, taxes, data protection, and payment receipt.

Nothing in these Terms overrides rights that applicable mandatory law does not permit the parties to waive.

81. LANGUAGE

The controlling version of these Terms is the English-language version unless DevSphere expressly designates another version as controlling.

Translations may be provided for convenience.

82. CONTACT

Questions concerning the Affiliate Program or these Terms may be directed to:

DevSphere Technologies PVT LTD

DevSphere Voice Affiliate Program

30 N Gould St, Ste R

Sheridan, WY 82801

United States

Email: [email protected]

Website: https://devspherevoice.com

83. ACCEPTANCE

By selecting the Affiliate Terms acceptance checkbox, completing Affiliate enrollment, accepting a required updated Terms version, or otherwise electronically confirming acceptance, you acknowledge that:

you have read these Terms;

you understand these Terms;

you agree to be bound by these Terms;

the information you provided is accurate to the best of your knowledge;

you will comply with the applicable Affiliate Program rules; and

if acting for an organization, you have authority to bind that organization.

Your acceptance is associated with the specific published Terms version presented to you at the time of acceptance.